Jump to content
The simFlight Network Forums

Recommended Posts

Posted

Hi Pete,

I've just upgraded to FSUIPC 4.6.1.5 from 4.6.0.2 and it seems there is a bug in the VRInsight code somewhere. When the VRInsight entries in the FSUIPC.ini are enabled and it comes time to exit FSX it also forces the PC to shutdown too. The dialogue box for Windows 7 comes up which has the drop down options to select shutdown, sleep, restart etc. If you click on the cancel button to stop the shutdown procedure it makes no difference and still shuts down the PC anyway. It's not a clean shut down either because many apps are asking me if I really want to stop them or not, things like my Anti-virus package are asking me if they really want me to close them or not.

If I disable everything in the INI related to VRI then FSX closes as normal, or at least it did the second and third time I tested it to confirm my findings, in the first test FSX appeared closed except it still resided in the task manager.

Posted

I've just upgraded to FSUIPC 4.6.1.5 from 4.6.0.2 and it seems there is a bug in the VRInsight code somewhere. When the VRInsight entries in the FSUIPC.ini are enabled and it comes time to exit FSX it also forces the PC to shutdown too....

Hmm. Strange. I don't know any way, programmatically, I can make that happen. There is some shutdown code in WideClient (for use on multi-PC systems when when you close FS you want the Clients to close too), but there's nothing similar in FSUIPC at all.

Didn't you try ANY version between 4.602 and 4.615? That's a huge number of changes! :-(

I'm out tonight, but I'll try setting my system up with some VRi devices tomorrow and see if I can reproduce the problem. Anything special I should know? Will just one connected MCP-Combi do? Do you have a Lua program running for it? Maybe a sight of the VRi parts of your FSUIPC4.INI file would help me reproduce it?

Regards

Pete

Posted

Unfortunately not Pete, I've hardly been near my FS PC due to other commitments and I'd not been too well over the last few weeks either, plus everything in FSUIPC had been working fine for me too so I didn't feel the need to update. It was only because I saw a fix for the M-panel that I bothered updating today.

No rush Pete I've dropped back to 4602 for now as it worked fine for me anyway. Here is some my FSUIPC4.ini

[General]
UpdatedByVersion=4615
History=CDGKY6778FAZU9GVULF06
MouseWheelTrim=No
MouseWheelTrimSpeed=1
FixControlAccel=Yes
FixMachSpeedBug=Yes
VisibilityOptions=No
OneCloudLayer=No
CloudTurbulence=No
CloudIcing=No
GenerateCirrus=Yes
SuppressCloudTurbulence=No
MaxIce=-4
MinIce=-4
UpperWindGusts=No
SuppressWindTurbulence=No
SuppressWindVariance=Yes
WindTurbulence=No
TurbulenceRate=0.5,2.5
TurbulenceDivisor=40,40,80,80
SuppressAllGusts=No
MaxSurfaceWind=0
WindLimitLevel=200
WindDiscardLevel=400
WindAjustAltitude=No
WindAjustAltitudeBy=2000
SmoothBySimTime=Yes
WindSmoothing=Yes
WindSmoothness=-2
WindSmoothAirborneOnly=No
PressureSmoothness=20
TemperatureSmoothness=100
DisconnTrimForAP=No
ZeroElevForAPAlt=No
ThrottleSyncAll=No
WhiteMessages=No
ShowPMcontrols=No
SpoilerIncrement=512
MagicBattery=Yes
RudderSpikeRemoval=No
ElevatorSpikeRemoval=No
AileronSpikeRemoval=No
ReversedElevatorTrim=No
ClockSync=No
ClockSyncMins=5
ClearWeatherDynamics=No
OwnWeatherChanges=No
TimeForSelect=30
LoadFlightMenu=No
LoadPlanMenu=No
PauseAfterCrash=No
SaveDataWithFlights=No
ZapSound=firework
ShortAircraftNameOk=Substring
UseProfiles=Yes
TCASid=Flight
TCASrange=60
AxisCalibration=No
DirectAxesToCalibs=No
ShowMultilineWindow=Yes
SuppressSingleline=No
SuppressMultilineFS=No
AxisIntercepts=No
WeatherReadFactor=1
WeatherRewriteSeconds=1
CustomWeatherModify=No
SimConnectStallTime=1
Console=No
SetSimSpeedX1=223,8
SetStdBaroKey=222,8
BrakeReleaseThreshold=50
DontResetAxes=No
JoystickTimeout=20
Debug=Please
PollGFTQ6=Yes
BlankDisplays=No
ConsoleWindow=513,64,1876,893
GetNearestAirports=No

[VRInsight]
1=COM3,COM21
2=COM4,COM23
3=COM5,COM25

[VRInsight.MPanl]
Lua=VRI_SetBaro
DriverWrites=Filter
WrFilter.1=BAR?
DriverReads=Filter
RdFilter.1=BAR?+

[Programs] 
Run1=READY,CLOSE,C:\Program Files (x86)\SerialFP2\SerialFP2.exe
Run2=READY,CLOSE,C:\Program Files (x86)\SerialFP2\SerialFP2.exe
Run3=READY,CLOSE,C:\Program Files (x86)\SerialFP2\SerialFP2.exe

[ClientNames]
1=ANDY-NETBOOK //Not being used during tests Pete

[Monitor]

[LuaFiles]
1=display vals
2=liar
3=ComLoop
4=MenuDemo
5=TripleUse
6=VRIinput
7=VRI_SetMach
8=VRI_SetBaro
9=F1_Mustang
10=log lvars

[MacroFiles]
1=md11
2=FSFK
3=J41
4=135LR
5=Mustang

[AutoSave]
AutoSaveEnabled=Yes
Interval=300
Files=10
SaveOnGround=No
Next=10
1=Mon 102038
2=Mon 102538
3=Mon 133408
4=Mon 133907
5=Mon 134407
6=Mon 134906
7=Mon 141709
8=Mon 142208
9=Wed 164932
10=Mon 101539
AlsoManage1=PMDG\MD11\PanelState\*.FLT.0.rte
AlsoManage2=PMDG\MD11\PanelState\*.FLT.0.slv.rte
AlsoManage3=PMDG\MD11\PanelState\*.FLT.1.rte
AlsoManage4=PMDG\MD11\PanelState\*.FLT.sav
AlsoManage5=PMDG\MD11\PanelState\*.FLT.2.rte
AlsoManage6=PMDG\MD11\PanelState\*.FLT.2.slv.rte
AlsoManage7=PMDG\MD11\PanelState\*.FLT.3.rte

[GPSout]
GPSoutEnabled=No
Port=COM3
Speed=4800
Interval=2000
PosTo6Decimal=No
Sentences=

[GPSout2]
GPSoutEnabled=No
Port=
Speed=4800
Interval=2000
PosTo6Decimal=No
Sentences=

[WideServer]
WideFSenabled=No
AdvertiseService=1
Port=8002
Port2=9002

[JoyNames]
AutoAssignLetters=No
I=InterLink
R=Saitek Pro Flight Rudder Pedals
X=Saitek X52 Pro Flight Controller


0=InterLink
0.GUID={2931FFF0-31F7-11DF-8001-444553540000}
2=Saitek Pro Flight Rudder Pedals
2.GUID={2931FFF0-31F7-11DF-8007-444553540000}
1=Controller (XBOX 360 For Windows)
1.GUID={756452B0-35C6-11DF-8001-444553540000}
3=Saitek X52 Pro Flight Controller
3.GUID={2931FFF0-31F7-11DF-8006-444553540000}

I'll try it with just the MCP to see if I can recreate it.

Yes the MCP on its own with the other devices disconnected and their entries removed from the FSUIPC4.ini reproduces the same error. I've posted the ini again below to show what's been disabled with comments.

[General]
UpdatedByVersion=4615
History=445QPXYWE6MBJY5KJA4PZ
MouseWheelTrim=No
MouseWheelTrimSpeed=1
FixControlAccel=Yes
FixMachSpeedBug=Yes
VisibilityOptions=No
OneCloudLayer=No
CloudTurbulence=No
CloudIcing=No
GenerateCirrus=Yes
SuppressCloudTurbulence=No
MaxIce=-4
MinIce=-4
UpperWindGusts=No
SuppressWindTurbulence=No
SuppressWindVariance=Yes
WindTurbulence=No
TurbulenceRate=0.5,2.5
TurbulenceDivisor=40,40,80,80
SuppressAllGusts=No
MaxSurfaceWind=0
WindLimitLevel=200
WindDiscardLevel=400
WindAjustAltitude=No
WindAjustAltitudeBy=2000
SmoothBySimTime=Yes
WindSmoothing=Yes
WindSmoothness=-2
WindSmoothAirborneOnly=No
PressureSmoothness=20
TemperatureSmoothness=100
DisconnTrimForAP=No
ZeroElevForAPAlt=No
ThrottleSyncAll=No
WhiteMessages=No
ShowPMcontrols=No
SpoilerIncrement=512
MagicBattery=Yes
RudderSpikeRemoval=No
ElevatorSpikeRemoval=No
AileronSpikeRemoval=No
ReversedElevatorTrim=No
ClockSync=No
ClockSyncMins=5
ClearWeatherDynamics=No
OwnWeatherChanges=No
TimeForSelect=30
LoadFlightMenu=No
LoadPlanMenu=No
PauseAfterCrash=No
SaveDataWithFlights=No
ZapSound=firework
ShortAircraftNameOk=Substring
UseProfiles=Yes
TCASid=Flight
TCASrange=60
AxisCalibration=No
DirectAxesToCalibs=No
ShowMultilineWindow=Yes
SuppressSingleline=No
SuppressMultilineFS=No
AxisIntercepts=No
WeatherReadFactor=1
WeatherRewriteSeconds=1
CustomWeatherModify=No
SimConnectStallTime=1
Console=No
SetSimSpeedX1=223,8
SetStdBaroKey=222,8
BrakeReleaseThreshold=50
DontResetAxes=No
JoystickTimeout=20
Debug=Please
PollGFTQ6=Yes
BlankDisplays=No
ConsoleWindow=513,64,1876,893
GetNearestAirports=No

[VRInsight]
1=COM3,COM21
//2=COM4,COM23
//3=COM5,COM25

[VRInsight.MPanl]
Lua=VRI_SetBaro
DriverWrites=Filter
WrFilter.1=BAR?
DriverReads=Filter
RdFilter.1=BAR?+

[Programs] 
Run1=READY,CLOSE,C:\Program Files (x86)\SerialFP2\SerialFP2.exe
//Run2=READY,CLOSE,C:\Program Files (x86)\SerialFP2\SerialFP2.exe
//Run3=READY,CLOSE,C:\Program Files (x86)\SerialFP2\SerialFP2.exe

[ClientNames]
1=ANDY-NETBOOK

[Monitor]

[LuaFiles]
1=display vals
2=liar
3=ComLoop
4=MenuDemo
5=TripleUse
6=VRIinput
7=VRI_SetMach
8=VRI_SetBaro
9=F1_Mustang
10=log lvars

[MacroFiles]
1=md11
2=FSFK
3=J41
4=135LR
5=Mustang

[AutoSave]
AutoSaveEnabled=Yes
Interval=300
Files=10
SaveOnGround=No
Next=10
1=Mon 102038
2=Mon 102538
3=Mon 133408
4=Mon 133907
5=Mon 134407
6=Mon 134906
7=Mon 141709
8=Mon 142208
9=Wed 164932
10=Mon 101539
AlsoManage1=PMDG\MD11\PanelState\*.FLT.0.rte
AlsoManage2=PMDG\MD11\PanelState\*.FLT.0.slv.rte
AlsoManage3=PMDG\MD11\PanelState\*.FLT.1.rte
AlsoManage4=PMDG\MD11\PanelState\*.FLT.sav
AlsoManage5=PMDG\MD11\PanelState\*.FLT.2.rte
AlsoManage6=PMDG\MD11\PanelState\*.FLT.2.slv.rte
AlsoManage7=PMDG\MD11\PanelState\*.FLT.3.rte

[GPSout]
GPSoutEnabled=No
Port=COM3
Speed=4800
Interval=2000
PosTo6Decimal=No
Sentences=

[GPSout2]
GPSoutEnabled=No
Port=
Speed=4800
Interval=2000
PosTo6Decimal=No
Sentences=

[WideServer]
WideFSenabled=No
AdvertiseService=1
Port=8002
Port2=9002

[JoyNames]
AutoAssignLetters=No
I=InterLink
R=Saitek Pro Flight Rudder Pedals
X=Saitek X52 Pro Flight Controller


0=InterLink
0.GUID={2931FFF0-31F7-11DF-8001-444553540000}
2=Saitek Pro Flight Rudder Pedals
2.GUID={2931FFF0-31F7-11DF-8007-444553540000}
1=Controller (XBOX 360 For Windows)
1.GUID={756452B0-35C6-11DF-8001-444553540000}
3=Saitek X52 Pro Flight Controller
3.GUID={2931FFF0-31F7-11DF-8006-444553540000}

I also use FPS-limiter but doubt that makes any difference.

Posted
When the VRInsight entries in the FSUIPC.ini are enabled and it comes time to exit FSX it also forces the PC to shutdown too. The dialogue box for Windows 7 comes up which has the drop down options to select shutdown, sleep, restart etc. If you click on the cancel button to stop the shutdown procedure it makes no difference and still shuts down the PC anyway.

Okay, I can reproduce the Win7 dialogue box coming up asking if I want to shut down the system or not, but when I press Cancel, it simply finishes closing FSX and that's it. Not so drastic, but still wrong.

I've no idea how I can get Windows to do that! Weird. Investigating now ...

Pete

Posted
I don't know why but sometimes I can't get it to cancel, I'm probably not as quick off the mark as you :D I'm glad you can repro it though.

I've found it and fixed itget 4.616 when it's up, soon ...

It turned out not to be anything directly to do with the VRi facilities, but the CLOSE option on the Run parameter for the SerialFP2 program. Any "run" parameter for any program with a "CLOSE" option would have generated the same error. Due to a stupid typo it was sending a WM_CLOSE message to the Desktop instead of to the program it should have been closing!

I never realised something as easy as sending WM_CLOSE to the Windows desktop could result in it actually trying to do so! In WideClient in order to close down client PCs I have to go to quite extraordinary lengths, comparatively speaking!

The "KILL" option for the Run parameters was okay, oddly.

Regards

Pete

Posted

Good news Pete I'm glad it was an easy fix, I'll keep my eye out for the update and try to keep abreast of your updates too so as to find any bugs as soon as possible in future.

Posted
Good news Pete I'm glad it was an easy fix, I'll keep my eye out for the update and try to keep abreast of your updates too so as to find any bugs a soon as possible in future.

Thanks. 4.616 is up now.

Best Regards

Pete

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
×
×
  • 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.