Jump to content
The simFlight Network Forums

Tigerhawk

Members
  • Posts

    15
  • Joined

  • Last visited

Posts posted by Tigerhawk

  1. 41 minutes ago, John Dowson said:

    This log shows that FSUIPC7 couldn't connect until more than 3.5 minutes after the sim was detected...very strange. Do you have a lot in your community folder? I will adjust to allow more time to be specified before the attempt to connect is made.

     

     

    I don't have a massive amount ( I don't think!) - 26 folders:-

    community folder.jpg

  2. 5 hours ago, Pete Dowson said:

    But if you don't mind waiting a few more days, I am working on a version of MakeRwys which uses local paths, changing the "current" directory to the main part of the path first. As I said, it's a bit complicated and quite error prone, so after I've tested it here as much as I can I'll send you a version to test.

    Pete

     

    Thanks Pete.
    Under the circumstances that seems like the best thing to do! 
    I’ll leave it in your capable hands!

  3. On 4/17/2021 at 12:01 AM, Terry Phelps said:

    Have been using makerunways for years with P3D and recently with MSFS. Had a system crash so reloaded msfs and makerunways. When I click the make runways exec. it only creats a file called runways but it is empty. I had it working before reload. My msfs is and was on my d drive under the default WpSystem folder. Any assistance would be appreciated. i use the program with msfs and Pilot2 atc. As stated worked fine for a while.

    Hi Terry,

    Did you ever get this sorted as I am having a similar problem?

  4. 23 hours ago, John Dowson said:

    To create links, the easiest method is to install the Link Shell extension, which will enable you to create links using windows Explorer. See https://schinagl.priv.at/nt/hardlinkshellext/linkshellextension.html

     

    Thanks for your input John,

    Unfortunately I find that even more obscure than Pete's suggestion.

    I sort of get what a symbolic link is - I presume I need to create a link (e.g - "D/New Link" linked to "C:\Users\David Hawxwell\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe") in order for the file name length to be much shorter?

    But what I don't understand is what type of link I need, nor how MakeRwys would then use the "D/New Link" rather than the original as I assume MakeRwys gets the location of MSFS from the Windows registry.

    Sorry to being a little confused, like Pete I just cannot understand what has caused this issue?

  5. 22 hours ago, Pete Dowson said:

     

    A symbolic link to "C:\Users\David Hawxwell\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe" might work.

     

     

    Hi Pete,

    I have updated Windows to 19043.1237 also.

    I've tried using both the gpedit and registry methods of enabling long path names, but still with exactly the same outcome.

    I've had a look at the symbolic link instructions.  I don't know if I'm being dense, but I'm afraid I haven't a clue how to do this to enable MakeRwys to use the link, or even how to even create the link or which type!

    Any advice?

  6. Thanks for your efforts Pete. 
    I did use the gpedit  method first, though when that didn’t work I also checked the registry method and there was a “1” entry against the long file names entry. 
    I’ll have a look at resetting the gpedit back to off and set it using the registry method tomorrow afternoon. 
    I’ll also have a look at the symbolic link method as well and report back. 

  7. Hi Pete,

    No, sorry, exactly the same result after making that change. The last file entered in the runways.txt was the same as previously so I haven’t attached it this time  

    I am on Windows 10 Pro - build 19043.1202 in case that makes a difference?

    I last run MakeRwys successfully in July (after the last MSFS World Update) so I presume it may be Windows updates that have caused this as there have been several since July?

     

  8. Thank you Pete,

    I believe all that has changed is the recent MSFS SU5 and WU6, that was why I was running it as the airports needed updating for PF3.

    I have attached the file.

    Yes, I was running it as Admin, and the User Account box is the "Do you want to allow this app from an unknown........ etc etc

    The following was in the Windows Event Viewer:-

    - <System>
      <Provider Name="Application Error" />
      <EventID Qualifiers="0">1000</EventID>
      <Version>0</Version>
      <Level>2</Level>
      <Task>100</Task>
      <Opcode>0</Opcode>
      <Keywords>0x80000000000000</Keywords>
      <TimeCreated SystemTime="2021-09-13T13:51:47.3186544Z" />
      <EventRecordID>25497</EventRecordID>
      <Correlation />
      <Execution ProcessID="0" ThreadID="0" />
      <Channel>Application</Channel>
      <Computer>255329-1-1</Computer>
      <Security />
      </System>
    - <EventData>
      <Data>MakeRwys.exe</Data>
      <Data>5.1.2.7</Data>
      <Data>60bf66cb</Data>
      <Data>ucrtbase.dll</Data>
      <Data>10.0.19041.789</Data>
      <Data>2bd748bf</Data>
      <Data>c0000409</Data>
      <Data>0000000000071208</Data>
      <Data>3e5c</Data>
      <Data>01d7a8a67e291090</Data>
      <Data>C:\FS_Addons\MakeRwys\MakeRwys.exe</Data>
      <Data>C:\Windows\System32\ucrtbase.dll</Data>
      <Data>54429960-59e5-4bd3-9b4f-70c74e232e9e</Data>
      <Data />
      <Data />
      </EventData>
      </Event>


    The ucrtbase.dll file has a date modified of 25/02/21 so has not changed recently.

    Hope this helps.

    Runways.zip

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.