Jump to content
The simFlight Network Forums
Flieger59

GSX does not work when the FSUIPC is installed

Recommended Posts

Hello,

I can not run GSX if the FSUIPC is installed.
In the menu item Add Ons - GSX - I can not call "Show GSX Menu by passing..Shift + Ctrl + F12.
If the FSUIPC is not installed, everything is fine.
Tried FSUIPC version 5.124 as well as 5.122.
P3D v4.2 client version 4.2.21.24048
GSX Version 2.3.0.1

Can you help me?

Share this post


Link to post
Share on other sites
22 minutes ago, Flieger59 said:

I can not run GSX if the FSUIPC is installed.
In the menu item Add Ons - GSX - I can not call "Show GSX Menu by passing..Shift + Ctrl + F12.
If the FSUIPC is not installed, everything is fine.

Have you tried any other key combinations? That isn't the default setting, is it? I thought it was a straight F11 or F12? I don't recall, because here I have it assigned to a button (via FSUIPC of course).

FSUIPC and GSX have absolutely nothing in common and they work quite happily together here. It sounds like you have Ctrl+SHft+F12 assigned in FSUIPC, or being used by a Lua plug-in as otherwise FSUIPC doesn't touch the keyboard.

Please show me your FSUIPC5.INI file.

You can also check these things by enabling Button and Key logging in FSUIPC's Logging tab, then checking the log after you've pressed those keys.

Pete
 

Share this post


Link to post
Share on other sites

My FSUIPC.INI

[General]
UpdatedByVersion=5124
History=QAY4D6WST4653P8IYE7SF
InitDelayDevicesToo=No
PMDG737offsets=Auto
PMDG747offsets=Auto
PMDG777offsets=Auto
Annotate=Yes
NewInterceptTextMenu=No
UseSystemTime=No
UseMidMouseBtn=Yes
MouseWheelMove=No
MouseWheelTrim=No
MouseWheelTrimSpeed=1
JoystickTimeout=20
FixControlAccel=No
FixMachSpeedBug=No
AutoScanDevices=Yes
DisconnTrimForAP=No
ZeroElevForAPAlt=No
ThrottleSyncAll=No
WhiteMessages=No
ShowPMcontrols=No
SpoilerIncrement=512
MagicBattery=No
RudderSpikeRemoval=No
ElevatorSpikeRemoval=No
AileronSpikeRemoval=No
ReversedElevatorTrim=No
ClockSync=No
ClockSyncMins=5
ClearWeatherDynamics=No
TimeForSelect=4
LoadFlightMenu=No
LoadPlanMenu=No
PauseAfterCrash=No
BrakeReleaseThreshold=75
SaveDataWithFlights=No
ZapSound=firework
ShortAircraftNameOk=Substring
UseProfiles=Yes
EnableMouseLook=No
DelayedMouseLookZoom=No
WideLuaGlobals=Yes
AxesWrongRange=No
TCASid=Flight
TCASrange=40,3
AxisCalibration=No
DirectAxesToCalibs=No
ShowMultilineWindow=Yes
SuppressSingleline=No
SuppressMultilineFS=No
AxisIntercepts=No
DontResetAxes=No
ThreadAffinityMask=x0
LuaAffinityMask=x0
InitDelay=0
GetNearestAirports=Yes
LogOptionProtect=Yes
TimeForLuaClosing=2
WeatherReadFactor=2
WeatherRewriteSeconds=1
CustomWeatherModify=No
SimConnectStallTime=1
InitialStallTime=10
NormalStallTime=1
LuaRerunDelay=66
Console=No
SetStdBaroKey=66,8
ProvideAIdata=Yes
ProvideAIairports=Yes
RestoreSimcWindows=No
ControlsListBuild=24048
ThrottleSyncToggle=88,8
FSVersionUsed="Lockheed Martin® Prepar3D® v4",4.2.21.24048
SimConnectUsed=4.2.0.0

[Traffic Limiter]
AirportPreference=50
PlannedAirportsPreference=50
GroundPreference=50
NearerPreference=50
TargetFrameRate=0
TrafficLimit=0

[JoyNames]
AutoAssignLetters=No
0=T.Flight Hotas X
0.GUID={EC7675E0-7C4A-11E7-800A-444553540000}

[Axes]
PollInterval=10
RangeRepeatRate=10

[Buttons]
PollInterval=25
ButtonRepeat=20,10

[AutoSave]
Next=1
Interval=60
Files=10
SaveOnGround=No
AutoSaveEnabled=No

[GPSout]
GPSoutEnabled=No

[GPSout2]
GPSoutEnabled=No

[WideServer]
WideFSenabled=Yes

[Sounds]
Path=F:\Lockheed Martin\Prepar3D v4\Sound\
Device1=Primärer Soundtreiber
Device2=Lautsprecher (2- C-Media USB Headphone Set  )
Device3=Realtek Digital Output(Optical) (Realtek High Definition Audio)
Device4=Lautsprecher (SPEEDLINK THEBE Default Device)
Device5=Realtek Digital Output (Realtek High Definition Audio)

[Window.Message Window]
NewDocked=23, 65, 1874, 17

[Window.SimConnectWindow]
NewDocked=-115, 5, 2149, 1075
Undocked=0, 0, 391, 222

[JoystickCalibration]
AllowSuppressForPFCquad=Yes
ExcludeThrottleSet=Yes
ExcludeMixtureSet=Yes
ExcludePropPitchSet=Yes
SepRevsJetsOnly=No
ApplyHeloTrim=No
UseAxisControlsForNRZ=No
FlapsSetControl=0
FlapDetents=No
ReverserControl=66292
Reverser1Control=66422
Reverser2Control=66425
Reverser3Control=66428
Reverser4Control=66431
MaxThrottleForReverser=256
AileronTrimControl=66731
RudderTrimControl=66732
CowlFlaps1Control=66162
CowlFlaps2Control=66163
CowlFlaps3Control=66164
CowlFlaps4Control=66165
SteeringTillerControl=0
MaxSteerSpeed=60
Throttle=-16380,16380
SlopeThrottle=15

 

Share this post


Link to post
Share on other sites
41 minutes ago, Flieger59 said:

Hello Pete, sorry I do not know exactly what is meant, so a picture of my FSUIPC menu

What don't you understand?  Why send me a picture of the "menu" my program creates? I did actually write the program and designed the menu (actually "Options") window, so I do know quite well what it looks like!

Do you mean you don't see the little tab marked "Logging"?  I can see it even in the miniature picture you sent! Have another look please!

The INI file you sent shows you aren't actually using FSUIPC user features for much, just a throttle calibration with a remarkably extreme slope (sensitivity) change.  Certainly no key assignments.

We need to see the logging of the key press to see what is going on.

By the way, there are some known reported problems related to add-on menus in P3D4.2 which are being resolved by L-M at this moment.  Your problem might be a symptom of one of them. But let me see what happens with the logging first.

Pete

 

 

 

 

Share this post


Link to post
Share on other sites
 
 
Following their instructions and running the INI. File (content)

[General]
UpdatedByVersion=5124
History=JE3YJA0XN8IO9VEO4KDYI

InitDelayDevicesToo=No
PMDG737offsets=Auto
PMDG747offsets=Auto
PMDG777offsets=Auto
Annotate=Yes
NewInterceptTextMenu=No
UseSystemTime=No
UseMidMouseBtn=Yes
MouseWheelMove=No
MouseWheelTrim=No
MouseWheelTrimSpeed=1
JoystickTimeout=20
FixControlAccel=No
FixMachSpeedBug=No
AutoScanDevices=Yes
DisconnTrimForAP=No
ZeroElevForAPAlt=No
ThrottleSyncAll=No
WhiteMessages=No
ShowPMcontrols=No
SpoilerIncrement=512
MagicBattery=No
RudderSpikeRemoval=No
ElevatorSpikeRemoval=No
AileronSpikeRemoval=No
ReversedElevatorTrim=No
ClockSync=No
ClockSyncMins=5
ClearWeatherDynamics=No
TimeForSelect=4
LoadFlightMenu=No
LoadPlanMenu=No
PauseAfterCrash=No
BrakeReleaseThreshold=75
SaveDataWithFlights=No
ZapSound=firework
ShortAircraftNameOk=Substring
UseProfiles=Yes
EnableMouseLook=No
DelayedMouseLookZoom=No
WideLuaGlobals=Yes
AxesWrongRange=No
TCASid=Flight
TCASrange=40,3
AxisCalibration=No
DirectAxesToCalibs=No
ShowMultilineWindow=Yes
SuppressSingleline=No
SuppressMultilineFS=No
AxisIntercepts=No
DontResetAxes=No
ThreadAffinityMask=x0
LuaAffinityMask=x0
InitDelay=0
GetNearestAirports=Yes
LogOptionProtect=Yes
TimeForLuaClosing=2
WeatherReadFactor=2
WeatherRewriteSeconds=1
CustomWeatherModify=No
SimConnectStallTime=1
InitialStallTime=10
NormalStallTime=1
LuaRerunDelay=66
Console=No
SetStdBaroKey=66,8
ProvideAIdata=Yes
ProvideAIairports=Yes
RestoreSimcWindows=No
ControlsListBuild=24048
ThrottleSyncToggle=88,8
FSVersionUsed="Lockheed Martin® Prepar3D® v4",4.2.21.24048
SimConnectUsed=4.2.0.0

[Traffic Limiter]
AirportPreference=50
PlannedAirportsPreference=50
GroundPreference=50
NearerPreference=50
TargetFrameRate=0
TrafficLimit=0

[JoyNames]
AutoAssignLetters=No
0=T.Flight Hotas X
0.GUID={EC7675E0-7C4A-11E7-800A-444553540000}

[Axes]
PollInterval=10
RangeRepeatRate=10

[Buttons]
PollInterval=25
ButtonRepeat=20,10

[AutoSave]
Next=1
Interval=60
Files=10
SaveOnGround=No
AutoSaveEnabled=No

[GPSout]
GPSoutEnabled=No

[GPSout2]
GPSoutEnabled=No

[WideServer]
WideFSenabled=Yes

[Sounds]
Path=F:\Lockheed Martin\Prepar3D v4\Sound\
Device1=Primärer Soundtreiber
Device2=Lautsprecher (2- C-Media USB Headphone Set  )
Device3=Realtek Digital Output(Optical) (Realtek High Definition Audio)
Device4=Lautsprecher (SPEEDLINK THEBE Default Device)
Device5=Realtek Digital Output (Realtek High Definition Audio)

[Window.Message Window]
NewDocked=23, 65, 1874, 17

[Window.SimConnectWindow]
NewDocked=-115, 5, 2149, 1075
Undocked=0, 0, 391, 222

[JoystickCalibration]
AllowSuppressForPFCquad=Yes
ExcludeThrottleSet=Yes
ExcludeMixtureSet=Yes
ExcludePropPitchSet=Yes
SepRevsJetsOnly=No
ApplyHeloTrim=No
UseAxisControlsForNRZ=No
FlapsSetControl=0
FlapDetents=No
ReverserControl=66292
Reverser1Control=66422
Reverser2Control=66425
Reverser3Control=66428
Reverser4Control=66431
MaxThrottleForReverser=256
AileronTrimControl=66731
RudderTrimControl=66732
CowlFlaps1Control=66162
CowlFlaps2Control=66163
CowlFlaps3Control=66164
CowlFlaps4Control=66165
SteeringTillerControl=0
MaxSteerSpeed=60
Throttle=-16380,16380
SlopeThrottle=15

[Monitor]
Display=1

 


 
Edited by Flieger59

Share this post


Link to post
Share on other sites
1 hour ago, Flieger59 said:

Following their instructions and running the INI. File (content)

Sorry, what was this about? What is the point of this message? It makes no sense at all. Who are "they" and how do you "run" an INI file? It is just a place where your settings are saved, not a program to run.

Have you changed the INI settings since you posted the file before, 2 hours before this strange post, repeating what looks to be exactly the same?

Pete

 

Share this post


Link to post
Share on other sites
41 minutes ago, Flieger59 said:

My last chance, since not well explained http://www.bilder-upload.eu/show.php?file=6c471d-1523188872.gif

That is a picture of the Log file in a Console window.

Earlier you couldn't even find the Logging tab. Now it seems you have found it and have been selecting things rather wildly!

Why? What are you trying to show? Why are you choosing a console log? And why are you pressing the "New Log" button?

The picture shows nothing useful.

I'll lay it out step-by-step. Do this:

1. Start P3D.
2. When P3D is ready, find the FSUIPC entry in the AddOns menu item
3. Select it so that the FSUIPC Otions window appears.
4. Click on the tab which says "Logging"
5. Make sure NOTHING is checked. Uncheck anything which is. Do NOT press any selections or buttons yet.
6. Now select the "Button and key operations" option, 3rd one down on the left, so that it is checked.
7. Click OK, bottom right
8. Press the key combination to invoke GSX. Note what happens.
9. Go back to FSUIPC Logging and UNCHECK the "Button and key operations" option you checked above.
10. Find the FSUIPC5.LOG file in the P3D Modules folder, and show me that. Paste the contents of the file in a message here -- please do NOT show me a photograph or screengrab!

I hope setting it out like this will help you understand what to do!

Pete

 

Share this post


Link to post
Share on other sites
Thank you for the effort and understanding !!
Hopefully correct....

********* FSUIPC5, Version 5.124 (27th February 2018) by Pete Dowson *********
Running inside Prepar3D v4
Module base=7FFF3EAE0000
Windows 10 Pro 64 Bit reported as Build 16299, Release ID: 1709 (OS 10.0)
Prepar3D.exe version = 4.2.21.24048
Reading options from "F:\Lockheed Martin\Prepar3D v4\Modules\FSUIPC5.ini"
Checking the Registrations now ...
User Name=""
User Addr=""
FSUIPC5 Key is provided
WIDEFS7 not user registered, or expired
        0 System time = 08/04/2018 15:01:08
        0 FLT path = "C:\Users\HJLampe\Documents\Prepar3D v4 Files\"
        0 ------ Module Version Check ------
        0        acontain.dll: 4.2.21.24048
        0             api.dll: 4.2.21.24048
       15        controls.dll: 4.2.21.24048
       15      fs-traffic.dll: 4.2.21.24048
       15             G3D.dll: 4.2.21.24048
       15        language.dll: 4.2.21.24048
       15            sim1.dll: 4.2.21.24048
       15        visualfx.dll: 4.2.21.24048
       15         weather.dll: 4.2.21.24048
       15          window.dll: 4.2.21.24048
       15 ----------------------------------
       15 Using PDK events
       15 Using DialogMode
       15 FS path = "F:\Lockheed Martin\Prepar3D v4\"
      125 ---------------------- Joystick Device Scan -----------------------
      125 Product= T.Flight Hotas X
      125    Manufacturer= Thrustmaster
      125    Vendor=044F, Product=B108 (Version 1.0)
      125    GUIDs returned for product: VID_044F&PID_B108:
      125       GUID= {EC7675E0-7C4A-11E7-800A-444553540000}
      125       Details: Btns=12, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R255,U255,V0,X1023,Y1023,Z255
      125 -------------------------------------------------------------------
      140 Device acquired for use:
      140    Joystick ID = 0 (Registry okay)
      140    0=T.Flight Hotas X
      140    0.GUID={EC7675E0-7C4A-11E7-800A-444553540000}
      140 -------------------------------------------------------------------
      156 LogOptions=40000000 00000001
      156 -------------------------------------------------------------------
      156 SimConnect_Open succeeded: waiting to check version okay
      156 Opened separate AI Traffic client okay
   166078 Running in "Lockheed Martin® Prepar3D® v4", Version: 4.2.21.24048 (SimConnect: 4.2.0.0)
   166078 Initialising SimConnect data requests now
   166078 FSUIPC Menu entry added
   166078 ... Using Prepar3D with Academic License
   166125 C:\Users\HJLampe\AppData\Local\Lockheed Martin\Prepar3D v4\Prepar3D_Default.fxml
   166125 F:\Lockheed Martin\Prepar3D v4\SimObjects\Airplanes\IRIS Raptor Driver\Raptor.air
   203890 Loading Complete ...
   204593 Aircraft loaded: running normally now ...
   204625 User Aircraft ID 2 supplied, now being used
   204984 System time = 08/04/2018 15:04:33, Simulator time = 14:00:01 (19:00Z)
   204984 Aircraft="F-22 Raptor - 525th Fighter Squadron"
   205984 -------------------- Starting everything now ----------------------
   206000 ASN active function link set
   206000 Ready for ActiveSky WX radar with additional data
   207265 Advanced Weather Interface Enabled
   228000 **** Restarting traffic scanning due to non-reception ****
   234640 KEYDOWN: VK=16, Waiting=0, Repeat=N, Shifts=1
   234640 .. Key not programmed -- passed on to FS
   235015 KEYDOWN: VK=17, Waiting=0, Repeat=N, Shifts=3
   235015 .. Key not programmed -- passed on to FS
   235531 KEYDOWN: VK=123, Waiting=0, Repeat=N, Shifts=3
   235531 .. Key not programmed -- passed on to FS
   236015 KEYUP: VK=123, Waiting=0
   236218 KEYUP: VK=17, Waiting=0
   236234 KEYUP: VK=16, Waiting=0
   242968 KEYDOWN: VK=16, Waiting=0, Repeat=N, Shifts=1
   242968 .. Key not programmed -- passed on to FS
   243328 KEYDOWN: VK=17, Waiting=0, Repeat=N, Shifts=3
   243328 .. Key not programmed -- passed on to FS
   243843 KEYDOWN: VK=17, Waiting=0, Repeat=Y, Shifts=3
   243843 .. Key not programmed -- passed on to FS
   243859 KEYDOWN: VK=17, Waiting=0, Repeat=Y, Shifts=3
   243859 .. Key not programmed -- passed on to FS
   243890 KEYDOWN: VK=17, Waiting=0, Repeat=Y, Shifts=3
   243890 .. Key not programmed -- passed on to FS
   243922 KEYDOWN: VK=17, Waiting=0, Repeat=Y, Shifts=3
   243922 .. Key not programmed -- passed on to FS
   243968 KEYDOWN: VK=17, Waiting=0, Repeat=Y, Shifts=3
   243968 .. Key not programmed -- passed on to FS
   244000 KEYDOWN: VK=17, Waiting=0, Repeat=Y, Shifts=3
   244000 .. Key not programmed -- passed on to FS
   244031 KEYDOWN: VK=17, Waiting=0, Repeat=Y, Shifts=3
   244031 .. Key not programmed -- passed on to FS
   244062 KEYDOWN: VK=17, Waiting=0, Repeat=Y, Shifts=3
   244062 .. Key not programmed -- passed on to FS
   244062 KEYDOWN: VK=123, Waiting=0, Repeat=N, Shifts=3
   244062 .. Key not programmed -- passed on to FS
   244297 KEYUP: VK=123, Waiting=0
   244437 KEYUP: VK=17, Waiting=0
   244468 KEYUP: VK=16, Waiting=0
   319031 ### MENU: Error: failed to receive DLGMODE notification! Going ahead anyway ...
   328437 **** No SimConnect events or states being received! Re-connecting now ... ****
   328797 SimConnect_Open succeeded: waiting to check version okay
   328797 Opened separate AI Traffic client okay

 


 

Share this post


Link to post
Share on other sites
43 minutes ago, Flieger59 said:

Hopefully correct....

Thank you!

So, first thing I notice is this:

44 minutes ago, Flieger59 said:

Checking the Registrations now ...
User Name=""
User Addr=""
FSUIPC5 Key is provided
WIDEFS7 not user registered, or expired

So, it seems that FSUIPC is actually running unregistered? Or have you deleted the User Name and Address in this posting?

It says "FSUIPC5 Key is provided" may mean the key you entered is NOT valid for FSUIPC5. maybe an FSUIPC4 one?

If FSUIPC is not registered it is really not doing anything UNLESS told to by some FSUIPC-using applications.

This sequence:

49 minutes ago, Flieger59 said:

   234640 KEYDOWN: VK=16, Waiting=0, Repeat=N, Shifts=1
   234640 .. Key not programmed -- passed on to FS
   235015 KEYDOWN: VK=17, Waiting=0, Repeat=N, Shifts=3
   235015 .. Key not programmed -- passed on to FS
   235531 KEYDOWN: VK=123, Waiting=0, Repeat=N, Shifts=3
   235531 .. Key not programmed -- passed on to FS
   236015 KEYUP: VK=123, Waiting=0
   236218 KEYUP: VK=17, Waiting=0
   236234 KEYUP: VK=16, Waiting=0

shows you pressing Ctrl + Shft + F12 then releasing them. As logged, they were not used by FSUIPC at all.  What then happens is up to other programs.

So, I'm sorry, but it isn't FSUIPC which is upsetting your GSX invoking. I can only suggest checking other add-ons you are running. In the past there has been the occasional odd issue with other add-ons and FSUIPC involving the order in which they are loaded.

Also, it would be worth you trying a different key comibination for GSX. I seem to recall it is assignable. Or maybe it defaults to the setting I have, which does work -- Ctrl+F12 rather than Shift+Ctrl+F12. Try it. (I think that is the default, by the way)

Pete

 

Share this post


Link to post
Share on other sites

Hello Pete,

I have almost the same issue:

I'm using FSUIPC5.131a

P3Dv4.2

when I load an addon scenery, no addons inside the add-ons menu works (GSX, Addon Manager, SODE, ChasePlane, ActiveSky, Ultimate Traffic, ....).

If I load the default scenery of P3D, everything works fine. But if I change the location, the issue comes back.

How did I know this is from FSUIPC ? 

I remove the entry from dll.xml then everything works fine with default scenery and addon s sceneries.

 

I tried to uninstall FSUIPC and reinstall. nothning changed

 

FSUIPC5.log:

********* FSUIPC5, Version 5.131 (17th May 2018) by Pete Dowson *********
Running inside Prepar3D v4
Module base=7FFBF7D80000
Windows 10 Pro 64 Bit reported as Build 17134, Release ID: 1803 (OS 10.0)
Prepar3D.exe version = 4.2.21.24048
Reading options from "D:\P3Dv4\Modules\FSUIPC5.ini"
Checking the Registrations now ...
User Name="Johann CHARLERY"
User Addr="           @djomaster.fr"
FSUIPC5 Key is provided
WIDEFS7 not user registered, or expired
        0 System time = 28/05/2018 18:57:02
        0 FLT path = "C:\Users\djomaster\Documents\Prepar3D v4 Files\"
        0 Using PDK events
        0 Using DialogMode
       15 FS path = "D:\P3Dv4\"
      203 ---------------------- Joystick Device Scan -----------------------
      203 Product= Saitek Pro Flight Yoke
      203    Manufacturer= Saitek
      203    Vendor=06A3, Product=0BAC (Version 3.4)
      218    GUIDs returned for product: VID_06A3&PID_0BAC:
      218       GUID= {8D4E6820-F220-11E6-8006-444553540000}
      218       Details: Btns=23, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U255,V255,X1023,Y1023,Z255
      218 Product= Saitek Pro Flight Rudder Pedals
      218    Manufacturer= Saitek
      218    Vendor=06A3, Product=0763 (Version 1.1)
      218    GUIDs returned for product: VID_06A3&PID_0763:
      218       GUID= {8D4D0890-F220-11E6-8002-444553540000}
      218       Details: Btns=0, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R511,U0,V0,X127,Y127,Z0
      218 -------------------------------------------------------------------
      234 Device acquired for use:
      234    Joystick ID = 0 (Registry okay)
      234    0=Saitek Pro Flight Yoke
      234    0.GUID={8D4E6820-F220-11E6-8006-444553540000}
      234 Device acquired for use:
      234    Joystick ID = 1 (Registry okay)
      234    1=Saitek Pro Flight Rudder Pedals
      234    1.GUID={8D4D0890-F220-11E6-8002-444553540000}
      234 -------------------------------------------------------------------
      265 LogOptions=00000000 00000001
      281 -------------------------------------------------------------------
      281 SimConnect_Open succeeded: waiting to check version okay
      281 Opened separate AI Traffic client okay
    18672 Running in "Lockheed Martin® Prepar3D® v4", Version: 4.2.21.24048 (SimConnect: 4.2.0.0)
    18672 Initialising SimConnect data requests now
    18672 FSUIPC Menu entry added
    18672 ... Using Prepar3D with Professional Plus License
    18859 C:\Users\djomaster\AppData\Local\Lockheed Martin\Prepar3D v4\Prepar3D_Default.fxml
    18859 D:\P3Dv4\SimObjects\Airplanes\IRIS Raptor Driver\Raptor.air

 

I tried a lot of other operations but same result (delete dll.xlm, prepar3d.cfg, uninstall Addons scenery and aircrafts, reinstall P3Dv4.2 client, uninstall GSX, uninstall & reinstall simconnect and as_connect, ....)

I don't know if it started with an W10 update

if you could help me and figure out this issue please.

 

regards,

Edited by djomaster@djomaster.fr

Share this post


Link to post
Share on other sites
10 hours ago, djomaster@djomaster.fr said:

when I load an addon scenery, no addons inside the add-ons menu works (GSX, Addon Manager, SODE, ChasePlane, ActiveSky, Ultimate Traffic, ....).

If I load the default scenery of P3D, everything works fine. But if I change the location, the issue comes back.

This is obviously a bug in P3D. Can you please report it to them.

10 hours ago, djomaster@djomaster.fr said:

How did I know this is from FSUIPC ? 

I remove the entry from dll.xml then everything works fine with default scenery and addon s sceneries.

Well, that's really not proof. You need to remove ALL add-ons then add them one at a time. It could be anything which uses SimConnect.

10 hours ago, djomaster@djomaster.fr said:

if you could help me and figure out this issue please.

I run GSX, UTLive, ASP4, ASCA, Rex SkyForce, and several others which appear in AddOns, and almost all the scenery i ever use is add-on scenery, and there's no such problems here. It really does sound like a P3D problem. After all, FSUIPC has no involvement whatsoever with scenery. I literally does not know what scenery you use nor does it case.

You might need to uninstall P3D completely and install it from scratch.

Pete

 

 

Share this post


Link to post
Share on other sites
16 hours ago, Pete Dowson said:

Well, that's really not proof. You need to remove ALL add-ons then add them one at a time. It could be anything which uses SimConnect.

Maybe you're right, but I don't understand why if I disable FSUIPC, everything works fine.

last week everything worked well. I went to Boston 5 days then suddently I got this issue

Saddly I think I have to install from scratch 😐🙁 too many addons to reinstall.

 

thanks for you support

Share this post


Link to post
Share on other sites
9 hours ago, djomaster@djomaster.fr said:

Saddly I think I have to install from scratch 😐🙁 too many addons to reinstall.

Just uninstall P3D4 as you would have to before installing an update from L-M in any case. When 4.3 comes out you'll want to do this in any case or you won't be taking advantage of all the fixes and improvements. It is by no means a static setup.

And you should not have to reinstall many, if any, addons. Save copies of the DLL.XML and EXE.XML from the user AppData\Roaming folder and restore them afterwards. Most up to date P3D4 addons aren't even bothered and don't load that way in any case. P3D4 will simply prompt you on first starting after reload asking if you want to enable each of those add-ons. Orbx aren't the same --- for their sceneries just run FTX Central and that sorts it out.

Nevertheless, I would strongly suggest that you re-download the Virtuali AddOn Manager (or the GSX Setup file as that includes AddOn Manager). I've experienced strange problems in the past and many of them came down to BGLMANX or COUATL being out of date. So much so that this is the first thing I tend to check on experiencing any odd problems.

Pete

 

Share this post


Link to post
Share on other sites
On 5/30/2018 at 8:11 AM, Pete Dowson said:

Just uninstall P3D4 as you would have to before installing an update from L-M in any case. When 4.3 comes out you'll want to do this in any case or you won't be taking advantage of all the fixes and improvements. It is by no means a static setup.

And you should not have to reinstall many, if any, addons. Save copies of the DLL.XML and EXE.XML from the user AppData\Roaming folder and restore them afterwards. Most up to date P3D4 addons aren't even bothered and don't load that way in any case. P3D4 will simply prompt you on first starting after reload asking if you want to enable each of those add-ons. Orbx aren't the same --- for their sceneries just run FTX Central and that sorts it out.

Nevertheless, I would strongly suggest that you re-download the Virtuali AddOn Manager (or the GSX Setup file as that includes AddOn Manager). I've experienced strange problems in the past and many of them came down to BGLMANX or COUATL being out of date. So much so that this is the first thing I tend to check on experiencing any odd problems.

Pete

 

Hello Pete,

I took long to preceed.

I reinstall completely my windows then P3D, QW 787, GSX, 787 immersion, FlyTampa St. Maarten, AS P3Dv4, Rex Sky Force 3D, chase plane. everything works fine.
then I installed FSUIPC 5.131a and ..... the issue came back 😞 😞 😞 

 

I don't know what to do. If I disable FSUIPC from dll.xml, all works fine

Regards,
Djo

Share this post


Link to post
Share on other sites
6 hours ago, djomaster@djomaster.fr said:

I don't know what to do. If I disable FSUIPC from dll.xml, all works fine

Assuming you downloaded a new copy of GSX then, sorry, I don't know what is wrong there. I use GSX all the time. Never any problems . There's absolutely no connection between the two programs.

Have you asked FSDT / Virtuali for help? If it is their program not running then really only they can work out why, maybe with some logging information. That's what I'd do if FSUIPC wasn't running -- add more logging to find out exactly why.

Pete

 

Share this post


Link to post
Share on other sites
5 hours ago, Pete Dowson said:

Assuming you downloaded a new copy of GSX then, sorry, I don't know what is wrong there. I use GSX all the time. Never any problems . There's absolutely no connection between the two programs.

Have you asked FSDT / Virtuali for help? If it is their program not running then really only they can work out why, maybe with some logging information. That's what I'd do if FSUIPC wasn't running -- add more logging to find out exactly why.

Pete

 

Hello Pete,

I though to ask them, but it's not only GSX not works. This issue applied to all addon-ons listed in the Add-ons menu. (AS, Addon Manager, SODE, UT, Chase Plane) and the QW 787 doesn't load correctly (some buttons non functional, no parking brake, ....). Only FSUIPC could open.
But if FSUIPC disabled, all addons in the menu works and the QW 787 fully functional

 

Djo

Share this post


Link to post
Share on other sites
4 hours ago, djomaster@djomaster.fr said:

I though to ask them, but it's not only GSX not works. This issue applied to all addon-ons listed in the Add-ons menu. (AS, Addon Manager, SODE, UT, Chase Plane) and the QW 787 doesn't load correctly (some buttons non functional, no parking brake, ....). Only FSUIPC could open.

Well Addon Manager is included in the GSX package. I use all of those except Chse Plane, will never ay trouble.

I think one of the things you have installed is messing up the normal SimConnect interface, but only when FSUIPC is there for some reason. 

By all means show me a FULL FSUIPC5.LOG file (last time you on;y showed the start of a session). I'll checvk that everything there looks okay. Run some things and close the session before getting the log.

A while back you said:

"last week everything worked well. I went to Boston 5 days then suddently I got this issue"

But FSUIPC doesn't know or care where you go away to, and it doesn't change just sitting there. It's certainly somethhing on your system.

Pete

 

Share this post


Link to post
Share on other sites
5 hours ago, Pete Dowson said:

Well Addon Manager is included in the GSX package. I use all of those except Chse Plane, will never ay trouble.

I think one of the things you have installed is messing up the normal SimConnect interface, but only when FSUIPC is there for some reason. 

By all means show me a FULL FSUIPC5.LOG file (last time you on;y showed the start of a session). I'll checvk that everything there looks okay. Run some things and close the session before getting the log.

A while back you said:

"last week everything worked well. I went to Boston 5 days then suddently I got this issue"

But FSUIPC doesn't know or care where you go away to, and it doesn't change just sitting there. It's certainly somethhing on your system.

Pete

 

lol I know Pete,
Maybe an update of Windows

FSUIPC5.log:

********* FSUIPC5, Version 5.131a (19th May 2018) by Pete Dowson *********
Running inside Prepar3D v4
Module base=7FFCD6320000
Windows 10 Pro 64 Bit reported as Build 17134, Release ID: 1803 (OS 10.0)
Prepar3D.exe version = 4.2.21.24048
Reading options from "D:\P3Dv4\Modules\FSUIPC5.ini"
Checking the Registrations now ...
User Name="Johann CHARLERY"
User Addr="djomaster@djomaster.fr"
FSUIPC5 Key is provided
WIDEFS7 not user registered, or expired
        0 System time = 13/06/2018 22:02:26
        0 FLT path = "C:\Users\djomaster\Documents\Prepar3D v4 Files\"
       16 Using PDK events
       16 Using DialogMode
       47 FS path = "D:\P3Dv4\"
      172 ---------------------- Joystick Device Scan -----------------------
      172 Product= Saitek Pro Flight Yoke
      172    Manufacturer= Saitek
      172    Vendor=06A3, Product=0BAC (Version 3.4)
      188    GUIDs returned for product: VID_06A3&PID_0BAC:
      188       GUID= {8D4E6820-F220-11E6-8006-444553540000}
      188       Details: Btns=23, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U255,V255,X1023,Y1023,Z255
      188 Product= Saitek Pro Flight Rudder Pedals
      188    Manufacturer= Saitek
      188    Vendor=06A3, Product=0763 (Version 1.1)
      188    GUIDs returned for product: VID_06A3&PID_0763:
      188       GUID= {8D4D0890-F220-11E6-8002-444553540000}
      188       Details: Btns=0, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R511,U0,V0,X127,Y127,Z0
      188 -------------------------------------------------------------------
      203 Device acquired for use:
      203    Joystick ID = 0 (Registry okay)
      203    0=Saitek Pro Flight Yoke
      203    0.GUID={8D4E6820-F220-11E6-8006-444553540000}
      203 Device acquired for use:
      203    Joystick ID = 1 (Registry okay)
      203    1=Saitek Pro Flight Rudder Pedals
      203    1.GUID={8D4D0890-F220-11E6-8002-444553540000}
      203 -------------------------------------------------------------------
      219 LogOptions=00000000 00000001
      234 -------------------------------------------------------------------
      234 SimConnect_Open succeeded: waiting to check version okay
      234 Opened separate AI Traffic client okay
     8500 Running in "Lockheed Martin® Prepar3D® v4", Version: 4.2.21.24048 (SimConnect: 4.2.0.0)
     8500 Initialising SimConnect data requests now
     8500 FSUIPC Menu entry added
     8500 ... Using Prepar3D with Professional Plus License
     8547 C:\Users\djomaster\AppData\Local\Lockheed Martin\Prepar3D v4\Prepar3D_Default.fxml
     8547 D:\P3Dv4\SimObjects\Airplanes\IRIS Raptor Driver\Raptor.air
    40109 D:\P3Dv4\SimObjects\Airplanes\QualityWings 787-9\Boeing 787-9 GE.air
    68172 Loading Complete ...
    69047 User Aircraft ID 4 supplied, now being used
    69047 Aircraft loaded: running normally now ...
    69141 System time = 13/06/2018 22:03:35, Simulator time = 17:02:35 (21:02Z)
    69156 Aircraft="QualityWings 787-9 Air France SATCOM"
    70141 -------------------- Starting everything now ----------------------
    70172 ASN active function link set
    70172 Ready for ActiveSky WX radar with additional data
   746156 ### MENU: Error: failed to receive DLGMODE notification! Going ahead anyway ...
  1225641 Sim stopped: average frame rate for last 1156 secs = 29.9 fps
  1225641    Max AI traffic was 1 aircraft (Deleted 0)
  1227016 === Closing session: waiting for DLLStop to be called ...
  1244313 === DLLStop called ...
  1244313 === Closing external processes we started ...
  1245313 === About to kill any Lua plug-ins still running ...
  1245469 === Closing global Lua thread
  1246484 === About to kill my timers ...
  1246672 === Restoring window procs ...
  1246672 === Unloading libraries ...
  1246672 === stopping other threads ...
  1246672 === ... Button scanning ...
  1246781 === ... Axis scanning ...
  1246875 === Releasing joystick devices ...
  1246875 === Freeing macro memory
  1246875 === Removing any offset overrides
  1246875 === Clearing any displays left
  1246875 === NOTE: not calling SimConnect_Close ...
  1246875 === AI slots deleted!
  1246875 === Freeing button memory ...
  1246875 === Closing my Windows ...
  1246875 === Freeing FS libraries ...
  1247875 === Closing devices ...
  1247875 === Closing the Log ... Bye Bye! ...
  1247875 System time = 13/06/2018 22:23:14, Simulator time = 17:14:49 (21:14Z)
  1247875 *** FSUIPC log file being closed
Minimum frame rate was 22.3 fps, Maximum was 44.9 fps
Average frame rate for running time of 1156 secs = 29.9 fps
Maximum AI traffic for session was 1 aircraft
Memory managed: 4 Allocs, 3 Freed
********* FSUIPC Log file closed ***********
 

 

 

Djo

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×

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.