[Programmed Buttons becoming reset after days of use]

1 hour ago, Pete Dowson said:

If the buttons are programmed generically -- i.e NOT whilst in a profile, or with the profile check mark off -- then the apply all the time unless overridden in a profile. But if you programmed then whilst in a profile and with the profile check mark on, then they ONLY apply to that profile.

That's the whole point in having profiles, so you can have different settings for flying different aircraft.

I've never heard of profile selection by airport -- I don't know how you'd do that. You normally use the Sim's scenarios for that. I think you maybe mixing up FSUIPC's profiles and the saved flights or scenarios you have? the latter are to do with the Sim, nothing to do with FSUIPC. FSUIPC's profiles are changed automatically depending on the aircraft you load.

Maybe you'd better show my your FSUIPC INI file (the one with the settings in) and tell me which button assignments keep "disappearning".

Pete

 

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.

[Programmed Buttons becoming reset after days of use]

14 minutes ago, Pete Dowson said:

I suspect you are just using Profiles with different settings and have some otherwise similar aircraft registered in different profiles and you are thinking they should be the same. It really sounds like you need to tidy it all up if so.

Pete

 

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.

[Programmed Buttons becoming reset after days of use]

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.

[FSUIPC Error #12]

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.

[FSUIPC Error #12]

14 minutes ago, Pete Dowson said:

If this the command line then it is no wonder it couldn't run. That says "run G:\ProSim737" (which is presumably a folder) with the parameter ProSim737.exe.

Assuming the path is correct you need just G:\ProSim737\ProSim737.exe. You don't even need any " as this contains no spaces.

Pete

 

Yes Pete, correct; I entered by mistake an quotation mark in the line - G:\ProSim737ProSim737.exe"

 

[FSUIPC Error #12]

2 minutes ago, Pete Dowson said:

If this the command line then it is no wonder it couldn't run. That says "run G:\ProSim737" (which is presumably a folder) with the parameter ProSim737.exe.

Assuming the path is correct you need just G:\ProSim737\ProSim737.exe. You don't even need any " as this contains no spaces.

Pete

 

Oh dear, silly me. I didn't notice that.

Again, thanks and I'll report further.

[FSUIPC Error #12]

Quote

You should be able to do that from the task bar - did you try?

No I didn't, and will do so  next.

Quote

It would help if you also showed me your FSUIPC6.ini file

I will send this on my next reply.

Quote

So, if FSUIPC didn't start prosim, something else did. If FSUIPC didn't start prosim, it won't be able to stop/kill it when terminating. Could that message therefore be from ProSim that has lost its FSUIPC connection as FSUIPC has terminated?

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.

[FSUIPC Error #12]

On 5/24/2021 at 6:39 AM, John Dowson said:

You need to determine which one, if any, is showing that message. Could it be something else? You could also show me your FSUIPC log file (and ini maybe) - that should show what was started and shut down.

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

[FSUIPC Error #12]

2 minutes ago, John Dowson said:

What program is sending that message? Are you using FSUIPC to shutdown that program as well?

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.

[FSUIPC Error #12]

Hi, I am getting this error message (see attached) after shutting down P3Dv5.1 using FSUIPC to start/close three programs.

Thanks,

Michael.

[Using the runway exclusion in makerunways for a specific airport]

On 6/10/2020 at 7:46 AM, Pete Dowson said:

If they no longer exist, but are present in the default airport data, then they need excluding in an add-on scenery file. Then MakeRunways will no longer list them.

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.

[Using the runway exclusion in makerunways for a specific airport]

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.

[FSUIPC error on sim shutdown]

Why do I get this error message every time I shutdown P3Dv4.3. Only recently started happening.

Thanks,

[GSX lua with with WideClient?]

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.

[RUN1 command section [PROGRAM] in FSUIPC.INI with FSX]

On 8/16/2018 at 4:49 AM, spokes2112 said:

If FSUIPC 5 contains the same run functions as FSUIPC 4 then take a look at the
\modules\FSUIPC Documents\FSUIPC Documents\FSUIPC# for Advanced Users.pdf
look for the "Programs: facilities to load and run additional programs" section.

If it all carried over from FSUIPC 4 then something like the following "may" work - (as an example)
RunIf1=READY,DELAY,C:\Windows\System32\notepad.exe

The above will give a 10 second delay "after" the sim is up and running.
Again this is under the assumption that the facilities are still available in FSUIPC 5

No hurting in giving it a try.. Pete will be back soon and can give further advise.

 

Thanks. tried it and it works.

[GSX lua with with WideClient?]

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.

[RUN1 command section [PROGRAM] in FSUIPC.INI with FSX]

Thanks Pete

[RUN1 command section [PROGRAM] in FSUIPC.INI with FSX]

I tried the DELAY and it works great.

Can I increase the 10 in DELAY=10, upwards?

Thanks.

[RUN1 command section [PROGRAM] in FSUIPC.INI with FSX]

Is their a way to add a delay to a program starting in FSUIPC5 [Programs]?

[RUN1 command section [PROGRAM] in FSUIPC.INI with FSX]

Is their a way to add a delay to a program starting in FSUIPC5 [Programs]?

[Called ProATCx Menu cycles OFF with FSUIPC 123e on P3Dv4.2]

I've gone back to P3Dv4.1 until there is a fix.

Regards,

Mike.

[Called ProATCx Menu cycles OFF with FSUIPC 123e on P3Dv4.2]

OK Pete thanks. So far I don't have the problem with GSX.

[Called ProATCx Menu cycles OFF with FSUIPC 123e on P3Dv4.2]

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

[Prepar3D v4.2 SimConnect and FSUIPC 5.123c]

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

[Further FSUIPC4 and P3D throttle and stick problems]

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