Jump to content
The simFlight Network Forums

Portanav

Members
  • Posts

    46
  • Joined

  • Last visited

Everything posted by Portanav

  1. Yes Pete your are correct I mean scenarios and not profiles, I did mix them up. I actually don't use profiles in FSUIPC. At least not as far as I am aware. I will send you the FSUIPC if you still want to have a look at it when nest I power up the sim. Thanks, Michael.
  2. Hi Pete, I fly only one aircraft Prosim737 (Flight Model). I'll program my eg: joystick (steering tiller) fly then when I come back in a day or two the joystick buttons that I programmed are gone (reset). I do have profiles for different airports which I use to load gate pos'n and radios tuned; do you mean that if I programmed a button/switch for a particular airport (profile) and then load another airport by profile that the buttons I just programmed for the other profile would not be there? Regards, Michael.
  3. Hi; On more than one occasion I have experienced FSUIPC reset randomly buttons that were previously programmed. Any idea what might be causing this to happen? Thanks.
  4. Pete, I was copying the the programs path from shortcuts, and some of them included quotes in the line which I did not take notice of. I made the correct entries this time, and all is working well once again. Thanks for the enlightenment and guidance. Michael.
  5. Yes Pete, correct; I entered by mistake an quotation mark in the line - G:\ProSim737ProSim737.exe"
  6. Oh dear, silly me. I didn't notice that. Again, thanks and I'll report further.
  7. No I didn't, and will do so next. I will send this on my next reply. FSUIPC didn't/couldn't start Prosim so I did that myself, so maybe that was the cause of the error#12. I check again. I will look further into this. Thanks.
  8. Hi John, I removed all the programs except for Prosim737 and I am still getting the error after shutdown of P3D. I have attached the log file for your perusal. Thanks. FSUIPC6.log
  9. Hello John, I am using Prosim737 and use FSUIPC to start Opencockpits SIOC, Prosim737 MCP and Prosim737. Not sure which one (or if all) is the culprit. I suspected it might have been that. Thanks very much for the reply. Michael.
  10. Hi, I am getting this error message (see attached) after shutting down P3Dv5.1 using FSUIPC to start/close three programs. Thanks, Michael.
  11. How is this exclusion done, as this is where I believe the problem lies; in the default scenery. How does one create and exclusion in an add-on? Thanks Pete.
  12. Hi Pete, is their a way to use the runway exclusion in makerunways.exe to exclude a runway at a specific airport? I am asking this since RAAS calls out runways no longer in use or existing at some airport scenery. Many thanks.
  13. Why do I get this error message every time I shutdown P3Dv4.3. Only recently started happening. Thanks,
  14. Here's the link Pete, I guess I misunderstood the post - https://prosim-ar.com/forum/viewtopic.php?f=95&t=15017#p106191 Thanks, Michael.
  15. Hi Pete, I saw on the Prosim forum that there is a GSX lua that works with WideClient. Can you tell me where I can get more information on this, or briefly what it does? Thanks, Michael.
  16. I tried the DELAY and it works great. Can I increase the 10 in DELAY=10, upwards? Thanks.
  17. Is their a way to add a delay to a program starting in FSUIPC5 [Programs]?
  18. Is their a way to add a delay to a program starting in FSUIPC5 [Programs]?
  19. Hi, with P3D in "full screen", whenever I call up the ProATCx Menu it flashes on screen and disappears. If I switch to a windowed P3D the menu stays ON when called. This did not happen with FSUIPC v1.22. Log attached. Regards, FSUIPC5.log
  20. I upgraded FSUIPC 122a on P3Dv4.2 to 123c and P3D is constantly reloading (updating) some content, too fast for me to read (flash). I went back to v122a and P3dv4.2 works fine. FSUIPC log attached. Regards, FSUIPC5.log
  21. Hi Pete; I seemed to have solved the problem. I decided to strip down the rudder pedals on the co-pilot's side, which was giving the problem. I found one of the wire connectors slack on the brake pot. Securing it properly to the pot has fixed the problem, or so it appears. So all flight control usb devices are functioning correctly now. If you still want the data requested I have attached for your perusal. Thanks very much, Michael. Current User.reg.txt FSUIPC4.ini FSUIPC4.log HidScanner.log Local Mach.reg.txt
×
×
  • 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.