Jump to content
The simFlight Network Forums

Andydigital

Members
  • Posts

    1,227
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by Andydigital

  1. That is the users registration email address not the store.
  2. R4.csv (one of the files created by makerwys.exe) is used by many applications including RAAS which is used by the 777 as you found out already, that file is it not exclusive to Radar Contact. Put the files back that you moved and the error will go away.
  3. You can get your key by logging into your account at Simmarket.com and looking at your purchase history.
  4. Isn't file corruption a potential issue when forcibly killing programs?
  5. No it's not possible to close anything after FSX has closed because FSUIPC has to close before FSX and P3D exit, FSUIPC is actually run inside of FSX so its impossible for it to do anything once it has closed itself.
  6. You can't avoid it, you are supposed to start ASN before FSX or P3D and close it after the simulators are exited. You get that warning because closing ASN before FS can cause problems with hangs, although to be honest that never seems to be an issue on my system.
  7. Like I said I've never used either of the other products so I have no idea, I'm sure someone else will answer if they know.
  8. EFB uses its own networking solution, no idea about the others as I never used them. EFB is really easy to use across a network though, there are detailed instructions in the manual.
  9. You need to assign with the special assignment app that comes with the A2A aircraft, the input configurator. FSUIPC will only work if you do it via an aircraft specific profile and offsets, I'll show you how if you wish, but it is easier to use the A2A application.
  10. This should help I think. http://forum.simflight.com/topic/73846-one-saitek-throttle-quadrant-lever-not-recognized-properly/
  11. None whatsoever ;) The FSPS support forum, where you should be ;) is at the link below. http://forum.simflight.com/forum/128-fsps-support-forum/
  12. You are talking about FSPS Fiber Accelerator not FSUIPC, hence you are in the wrong forum section.
  13. The FSUIPC license is registered in your name for you to use on as many PC's as you personally own, you can even use it on all of them at the same time too, it makes a refreshing change doesn't it.
  14. Deleted. See here; http://www.a2asimulations.com/forum/viewtopic.php?t=35833#p270188
  15. Search Flight1's website for "Soundstream". Be aware P3D does not need this as its a built in feature.
  16. You may not be using Linda but it's LUA's are obviously still installed as that is where that error is coming from, it's nothing to do with FSUIPC or VRInsight as I said above.
  17. This will be a LINDA popup printed by their LUA's and nothing to do with FSUIPC or VRInsight. By the way I answered you already over on the VRi forum and the fix is the same as Pete posted above in post 4 i.e. remove the VRinsight section from the FSUIPC.ini, you should also disable the MCP Combo in Linda too.
  18. Even though the brakes message is not showing on the screen it is still possible for the brakes to bind ever so slightly if you haven't created a big enough null zone for your pedals. I'd try making the null zone bigger and assign the brakes through FSUIPC not in FSX, remember to recalibrate after Reversing the axis if needed.
  19. Just remove the whole line that says Patchsimfriction.
  20. Yes, but also read further through that thread and take notice of posts 8 and 9 seeing as you have been using a patched sim1.dll
  21. A quick search of the forum got me this; http://forum.simflight.com/topic/75702-dynamic-friction-with-fsuipc-4923/?hl=dynamicfriction
  22. Restore the original sim1.dll file and use the dynamicfrictions.lua instead it much better and more sophisticated than then version you are trying to use now.
×
×
  • 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.