Jump to content
The simFlight Network Forums


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About gfd

  • Rank
    Advanced Member

Profile Information

  • Gender
    Not Telling
  • Location
    Alberta, Canada

Recent Profile Visitors

2,019 profile views
  1. You're the best Simon. All the best in return.
  2. Thanks for the background. I'll post to them over at their place and see what they have to say. I couldn't figure out how I might have invoked some elevated debug activity in FSUIPC. I use ASN and therefore do not make extensive use of your miscellaneous options. The exceptions being VAS tracking via the log page and the facility to start the session with accurate time. Controller assignments and WideFS buttons are something else altogether. I mention this as you expressed concern about P3D v3 playing nice with FSUIPC. I don't know what significance this will have, but: -as stated elsewher
  3. Thanks Simon, for getting us back on track. I experience single stutters lasting about 1 second on an infrquent basis. I am using UT2 now and perhaps that is the reason. I also have MyTraffic 6. UT2 appears to be less of a drag on the system and the models are superior. Too bad it is no longer supported. I won't go into the litany. You mentioned you were able to use STB in P3D 3, using the hotfix. Where do I get that? Or is it rendered obsolete by your other advances? Does STB support UT2? I had to create a fake FSX environment to get it installed. Will that impact the functionality of STB?
  4. Thanks for that. Just to clarify, let's say I have two identical controllers. 1=A and 2=B. Each has a distinct GUID: 1=controller 1.GUID={123} 2=controller 2.GUID={234} A=controller A.GUID={123} B=controller B.GUID={234} Say the controllers drop out and get reversed. I correct that by changing the letters on both pairs of lines? Thanks again.
  5. I am using the latest version of FSUIPC along with LINDA in P3D v3 inside of Windows 10 64 bit. I have started getting an error in the FSUIPC log as follows: *** LUA Error: cannot open S:\P3D\Modules\ipcDebug.lua: No such file or directory There are several instances of this error in the log. This file does not exist on my computer. Please see the log below. I should point out that I looked at this thread: http://forum.simflight.com/topic/80259-i-need-help-for-lua/ Have I inadvertently put FSUIPC into debug mode? Is this something I need to be concerned about? If not, plea
  6. I am bumping my own topic as I need some help. As indicated above, the Saitek throttles drop out after restarting Windows. The only way to get them back is to reinstall the driver. This reorders the controllers in the OS. I had thought that FSUIPC reassigned the controller order to compensate. I may have been mistaken. I reinstalled the driver after a reboot and two of the throttle quadrants were reversed. No amount of tinkering with FSUIPC4.ini corrected the situation. I looked in the manual, but didn't find a solution. I'm sure it's there, but I'm probably too thick to get it. I had Auto
  7. I can confirm that P3D seems to respect the deleted controller assignments when there is a disconnect/reconnect.
  8. Yeah, that's how I do it. However, until the latest version, I found that when I reinstalled my controllers, due to the useless Saitek drivers; I had to mess around getting FSUIPC controllers back in order. This is the first time I reinstalled drivers and didn't have to do some engineering in order to keep the controllers in line. Perhaps I was doing something wrong in the past, but the compliment still stands.
  9. Just wanted to say thanks for making good on the plan to have FSUIPC track controller changes. As some of you may know, Saitek controllers tend to misbehave on Windows 10; particularly if the are more than 1 of the same controller. In my case, I have 3 throttle quadrants. On startup, I occasionally lose 1 or more controllers. That requires running the driver installer to get the controllers back. I decided to uninstall all of the throttles and manually point them to the inf file for the driver. I don't know if that will work. However, upon reinstalling the drivers, the throttle IDs in Wind
  10. I cannot disagree re the preferred location for xml file use (ProgramData). I am not competent to do so. However, all of my addons have used the xml files in AppData. But perhaps this is not the problem that Simon needs to tackle. I have deactivated the SuperTrafficBoard server entry in exe.xml and ran it manually before, during and after P3D. The result is the same: initiizes and shuts down after bout 5 seconds. P3D is setup on separate drive. STB server is setup on same drive as P3D in separate folder. Both are set to run as administrator. I have not tried putting an entry into the xml file
  11. There are exe.xml/dll.xml files in both %PROGRAMDATA% and %APPDATA%. The files in ProgramData are stripped and probably exist in order to replace a deleted file in AppData. So...both functional xml files are in Roaming\Lockheed Martin\Prepar3D v3\. I setup a dummy framework for both FSX and P3D v2 in order to install/configure legacy addons. This includes links to folders and registry entries. STB server still crashes/closes after P3D startup. What is your program looking for, that it can't find?
  12. As far as registry keys go, I have registry keys for Prepar3D v2 in both HKCU\SOFTWARE\Lockheed Martin and HKLM\SOFTWARE\Wow6432Mode\Lockheed Martin. I also have symbolic links titled Prepar3D v2 pointing to Prepar3D v3 in ProgramData, AppData\Roaming, AppData\Local and MyDocuments. I have been able to install software which doesn't support P3D v3. According to the error messages that Clayton and I get, STB reports P3D version Does STB look in the metadata of Prepar3D.exe? Possibly not, as the STB server didn't crash until Prepar3D started. There was no complaint about the platfor
  • 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.