FSUIPC stops working

[guenseli]

Hello Pete,

this is a very strange bug, I fiddled now a few weeks with it around, now I have to ask you.

I installed WIN8 64 enterprise version (RTM official version).

Means also that I installed FSX (Acc) freshly ... with FSUIPC 4.853

Normaly I copy over the complete modules folder to have my setup instantly as I assigned everything through FSUIPC.

What happens now is, that sometimes, when I enter the FSUIPC menue,FSUIPC stopps working.

Currently this evening, it is for 100% that it is not working.

This doesn't matter which aircraft it is.

Before entering FSUIPC menue everything works, but if I call up FSUIPC menue, I can't see my axis or buttons in the FSUIPC interface.

If I leave then the FSUIPC interface, everything has stopped working - moving a joystick does not have any result.

Buttons do also not react (in the FSUIPC menue), but they do it through LINDA (where I have all my buttons assigned with)

(as you surely know, LINDA needs FSUIPC to work, that's why I wonder)

What I have tried to solve it:

- complete new FSUIPC.ini with all assignments new.

- "reload all assignments" of course

- disabled USB poweroff in the OS

- disabled any other OS power save thingy

- changed my joysticks location to several USB ports (I have a Warthog, two Saitek throttles, a Bodnar BUX device and a X52 Pro)

- all drivers updated

- checked windows devices and joysticks show up and work as they should while they do not in FSUIPC any more

- EZDOC hat switch is working also after FSUIPC has stopped

For your info: as I said above it wasn't working for 100% this evening: this was resolved by restarting the PC.

After that it was working. Don't know if that info is important.

I insert hereinafter my first part of the FSUIPC.ini, maybe you see sth.

(note, that I moved to P3D now: what I've described above happened with normal FSX, but is the same issue in P3D)

I hope you do not say "doesn't interest me; WIN8 isn't officially released"

Everything (except the new QW Bae146) is working under WIN8 without any problems.

Many, many thanks,

Günter

[General]
UpdatedByVersion=4853
History=EGYXFLP7LXO5XKTTH3XIW
InitDelayDevicesToo=No
MouseWheelMove=No
MouseWheelTrim=No
MouseWheelTrimSpeed=1
JoystickTimeout=20
PollGFTQ6=Yes
BlankDisplays=No
FixControlAccel=No
FixMachSpeedBug=No
DeleteVehiclesForAES=Yes
AutoScanDevices=Yes
VisibilityOptions=No
OneCloudLayer=No
CloudTurbulence=No
CloudIcing=No
GenerateCirrus=No
SuppressCloudTurbulence=No
MaxIce=-4
MinIce=-4
UpperWindGusts=No
SuppressWindTurbulence=No
SuppressWindVariance=No
WindTurbulence=No
TurbulenceRate=1.0,5.0
TurbulenceDivisor=20,20,40,40
SuppressAllGusts=No
MaxSurfaceWind=0
WindLimitLevel=200
WindDiscardLevel=400
WindAjustAltitude=No
WindAjustAltitudeBy=2000
SmoothBySimTime=No
WindSmoothing=No
WindSmoothness=2
WindSmoothAirborneOnly=Yes
PressureSmoothness=0
TemperatureSmoothness=0
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
OwnWeatherChanges=No
TimeForSelect=4
LoadFlightMenu=No
LoadPlanMenu=No
PauseAfterCrash=No
BrakeReleaseThreshold=0
SaveDataWithFlights=No
ZapSound=firework
ShortAircraftNameOk=Yes
UseProfiles=Yes
EnableMouseLook=No
AxesWrongRange=No
TCASid=Flight
TCASrange=40
AxisCalibration=No
DirectAxesToCalibs=No
ShowMultilineWindow=Yes
SuppressSingleline=No
SuppressMultilineFS=No
AxisIntercepts=No
DontResetAxes=No
InitDelay=0
GetNearestAirports=No
OOMcheck=Yes
WeatherReadFactor=2
WeatherRewriteSeconds=1
CustomWeatherModify=No
SimConnectStallTime=1
InitialStallTime=10
NormalStallTime=1
LuaRerunDelay=66
Console=No
LogEvents=Yes
FSVersionUsed="Lockheed Martin® Prepar3D®",1.4.4747.0
SimConnectUsed=1.4.0.0

[VRInsight]
1=com3
[Programs]
RunIf1=F:\Program Files (x86)\Lockheed Martin\Prepar3D\Modules\linda.exe

[JoyNames]
AutoAssignLetters=Yes
A=Saitek Pro Flight Throttle Quadrant
A.GUID={77A144F0-FA79-11E1-8002-444553540000}
B=BU0836X Interface
B.GUID={77A144F0-FA79-11E1-8003-444553540000}
C=Saitek Pro Flight Rudder Pedals
C.GUID={77A16C00-FA79-11E1-8005-444553540000}
D=Joystick - HOTAS Warthog
D.GUID={77A16C00-FA79-11E1-8006-444553540000}
E=Saitek Pro Flight Throttle Quadrant
E.GUID={77A16C00-FA79-11E1-8007-444553540000}
F=Throttle - HOTAS Warthog
F.GUID={77A19310-FA79-11E1-8008-444553540000}
G=Saitek X52 Pro Flight Control System
G.GUID={77A1BA20-FA79-11E1-800D-444553540000}
0=Saitek Pro Flight Throttle Quadrant
0.GUID={77A144F0-FA79-11E1-8002-444553540000}
1=BU0836X Interface
1.GUID={77A144F0-FA79-11E1-8003-444553540000}
2=Saitek Pro Flight Rudder Pedals
2.GUID={77A16C00-FA79-11E1-8005-444553540000}
3=Joystick - HOTAS Warthog
3.GUID={77A16C00-FA79-11E1-8006-444553540000}
4=Saitek Pro Flight Throttle Quadrant
4.GUID={77A16C00-FA79-11E1-8007-444553540000}
5=Throttle - HOTAS Warthog
5.GUID={77A19310-FA79-11E1-8008-444553540000}
6=Saitek X52 Pro Flight Control System
6.GUID={77A1BA20-FA79-11E1-800D-444553540000}


[Buttons]
ButtonRepeat=20,10
1=CP(+A,2)A,5,CL2:R,0

[MacroFiles]

[LuaFiles]
1=ipcReady
2=linda
3=log lvars
4=A2A_Cowl
5=A2A_Flaps
6=A2A_Turbo

[AutoSave]
Next=1
Interval=60
Files=10
SaveOnGround=No
AutoSaveEnabled=No
[GPSout]
GPSoutEnabled=No
[GPSout2]
GPSoutEnabled=No
[WideServer]
WideFSenabled=Yes
[Sounds]
Path=F:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Sound\
Device1=Primärer Soundtreiber
Device2=Lautsprecher (High Definition Audio-Gerät)
Device3=Kopfhörer (High Definition Audio-Gerät)
Device4=Digitalaudio (S/PDIF) (High Definition Audio-Gerät)
Device5=Digitalaudio (S/PDIF) (High Definition Audio-Gerät)
[Keys]
2=97,8,1126,0
4=98,8,65907,0
5=99,8,65908,0
7=100,8,65909,0
9=101,8,65910,0
11=102,8,65911,0
13=103,8,65912,0
15=104,8,65913,0
17=105,8,65914,0
19=111,8,66506,225
21=96,8,1126,0

[Axes]
0=AX,256,D,13,0,0,0
1=AY,256,D,14,0,0,0
2=AZ,256,D,23,0,0,0
3=CX,256,D,7,0,0,0
4=CY,256,D,8,0,0,0
5=CR,256,D,47,0,0,0
6=DX,256,D,45,0,0,0
7=DY,256,D,46,0,0,0
8=EX,256,D,17,0,0,0
9=EY,256,D,18,0,0,0
10=EZ,256,D,22,0,0,0
11=FZ,256,D,10,0,0,0
12=FR,256,D,9,0,0,37
13=FS,256,D,21,0,0,0

[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
Aileron=-16380,-512,512,16380
Elevator=-16380,-512,512,16380
Rudder=-16380,-2000,2000,16380
LeftBrake=-16380,16380/16
RightBrake=-16380,16380/16
Throttle1=-16380,-512,512,16380/32
Throttle2=-16380,-512,512,16380/32
ElevatorTrim=-16380,-512,512,16380
SlopeElevatorTrim=5
[/CODE]

[Pete Dowson]

I installed WIN8 64 enterprise version (RTM official version).

Ugh! Why on Earth abandon Windows 7, the best operating system Microsoft ever produced, for something so inferior? At least wait for Windows 9. Win8 looks like another Vista fiasco to me.

Before entering FSUIPC menue everything works, but if I call up FSUIPC menue, I can't see my axis or buttons in the FSUIPC interface.

If I leave then the FSUIPC interface, everything has stopped working - moving a joystick does not have any result.

Buttons do also not react (in the FSUIPC menue), but they do it through LINDA (where I have all my buttons assigned with)

(as you surely know, LINDA needs FSUIPC to work, that's why I wonder)

Is Win8 compatible with Win7 and before? Is there a Win7 compatibility mode you can set for FSX?

I insert hereinafter my first part of the FSUIPC.ini, maybe you see sth.

I'm sure nothing you can do in an INI file will make a difference between Win7 and Win8. The differences must be in Windows.

I hope you do not say "doesn't interest me; WIN8 isn't officially released"

Everything (except the new QW Bae146) is working under WIN8 without any problems.

But evidently it is different. FSUIPC works okay in WinXP, Vista and Win7. So what's been messed up in Win8? And how can I possibly tell?

I don't understand why you supply an INI file yet no Log at all. You say FSUIPC is 100% not working even with a default INI file? Or do you really mean that FSUIPC is working completely normally EXCEPT for assignments? If you assign in FSX and merely calibrate in FSUIPC, does that work?

I'm afraid there's no way I'm going to be able to do anything with Win 8 for a while. I'll need to build a new PC -- I can't afford to compromise any of those I currently use for development. You'll need to do some process of elimination. Start simple. Try all avenues. Collect data. Use logging.

Pete

[guenseli]

Morning Pete,

Interesting to see so many people ranting about WIN8; I'm sure most haven't had a slight glance into it beside some screenshots of the metro menu ;-)

All I can say is, that there is absolutely no difference in appearance between WIN7 and WIN8, except the startmenue is looking different - and you can use it on your tablet in a few month. The difference however is a much faster OS with some features I like very much now.

What I wonder about is, that it (FSUIPC) works mostly but than from a day to another when I enter the menue, FSUIPC stops working.

A restart of FSX solves this then. (exception yesterday evening).

I haven't attached a LOG file, because, there you could not see anything. There is simply no loggin any more.

But of course, I can attach one next time it happens.

You say FSUIPC is 100% not working even with a default INI file? Or do you really mean that FSUIPC is working completely normally EXCEPT for assignments?

What I see, when I open the FSUIPC menue is, that there's then no reaction to joystick movement or button presses.

When I close then the menue, I have no joystick movement in FS, too. Restarting FS solves this normaly.

Same could happen with a default ini file, yes.

As I said, this does not happen every time. There are days it is working normal as it should.

I was just posting here in case, you have an initial idea about- maybe I have messed something up in my ini ...

But I do not want you to dig deeper into that as I also have to say that I experiment now currently a bit with the OS and FSX and P3D.

Maybe I had made some strange setting somewhere.

In one month, when WIN8 is released to the public I have to reinstall in any case and I would then avoid to try out all the settings.

I'm very confident WIN8 would be a success :razz:

EDIT

Is Win8 compatible with Win7 and before?

Yes, of course and I can of course set compatibility mode to test it, but no difference.

Till now I haven't had one program that had any problems with win8. Even my old scanner who has just XP drivers is working.

[Pete Dowson]

Interesting to see so many people ranting about WIN8; I'm sure most haven't had a slight glance into it beside some screenshots of the metro menu ;-)

I put the Preview edition on an otherwise seldom-used lap top to check it out. It took quite a bit of fiddling aound to get it as usable as Win7 (my opinion of course). Certainly FSUIPC worked okay on it, but everything was so slow as to be unusable. It's only a 2 GHz processor, but i expected more. The main problem was lack of drivers, eg, for video, then.

All I can say is, that there is absolutely no difference in appearance between WIN7 and WIN8, except the startmenue is looking different

Have they actually put the start button back? I had to download a program to fiddle that back in on the Preview.

What I wonder about is, that it (FSUIPC) works mostly but than from a day to another when I enter the menue, FSUIPC stops working.

A restart of FSX solves this then. (exception yesterday evening).

But FSUIPC isn't changing -- so what in your system is changing? Why is Win8 different on one day to another? And why should restarting a program make it run differently? There's nothing a program retains when it closes other than in its files, and FSUIPC's files are ONLY the INI and referenced macro and Lua files.

I haven't attached a LOG file, because, there you could not see anything. There is simply no loggin any more.

What do you mean "no logging any more". You mean no closure, no end? So FSUIPC really does get unloaded or hung? The Logging is produced in the main thread, the same as the main thread of FSX, so if that thread hangs, so does FSX.

I was just posting here in case, you have an initial idea about- maybe I have messed something up in my ini ...

But there is nothing you can do in the INI which will make it change from day to day or the start of FSX to the next restart. And nothing in a default INI either.

For more information on what is going on with buttons and axes, add more logging options. Button logging, especially, but also add this to the [General] section of the INI:

Debug=Please

LogExtras=x200000

That'll make it log some of the details of the device scan it does when you go into the assignment options.

But I do not want you to dig deeper into that as I also have to say that I experiment now currently a bit with the OS and FSX and P3D.

Maybe I had made some strange setting somewhere.

In one month, when WIN8 is released to the public I have to reinstall in any case and I would then avoid to try out all the settings.

I have downloaded the release version (I assume it is release) 64-bit, but not "Enterprise", and will make a DVD of the ISO. I have five keys for it so I will try it on that Lap Top I mentioned.

Till now I haven't had one program that had any problems with win8. Even my old scanner who has just XP drivers is working.

Must be a huge change from the shabby preview editions, then.

What is different in the "Enterprise" edition? I don't think I'm entitled to that as part of my MSDN/MVP membership. I'd assumed in any case most FS users would be using the standard edition.

Regards

Pete

[guenseli]

Hello Pete,

I got mine from here, I think I had subscribed for MSDN a while ago

http://msdn.microsoft.com/en-us/evalcenter/jj554510.aspx

I tried the public versions a few month ago, too, and yes, there is a big difference.

Currently, the enterprise RTM it is not perfect as IE10 or the on-board-mail program have some bugs, but all in all it is rockstable and faster as WIN7; at least for me.

In FSX I can't see any difference in frames or smoothing, but I haven't expceted this.

MS has done a huge stept forward the last month/year in my opinion.

I own a Windows Phone, just wanted to try out for cheap money and I'm very surprised and even IPhone users do admit a better usability!

In combination with a MS Live ID and WIN8, it's a perfect workspace

(no, I'm not a MS employee :mrgreen: )

The difference between enterprise and the WIN8 Pro version which will be relased end of october for public is not soooo big for a normal user I think.

Enterprise is able to have the complee OS on an USB stick and has some developer features.

But be aware, that this version ends after 90 days without any possibility to change to the nomal version. You have to reinstall in every case!

Regarding the FSUIPC proble, I have inserted the logging lines into the ini and hope to catch the error this evening!

Maybe we see then sth in the log.

Greetings,

Günter

[Pete Dowson]

I got mine from here, I think I had subscribed for MSDN a while ago

http://msdn.microsof...r/jj554510.aspx

Ah, tthats a public evaluation version.

The difference between enterprise and the WIN8 Pro version which will be relased end of october for public is not soooo big for a normal user I think.

Enterprise is able to have the complee OS on an USB stick and has some developer features.

But be aware, that this version ends after 90 days without any possibility to change to the nomal version. You have to reinstall in every case!

i think the version I downloaded is the one which will be publically released, and as an MVP I get some free keys which are permanent, not temporary. As it says, on that Evaluation weeb page:

Is the evaluation edition really for you?

This is intended for developers building Windows 8 apps and IT professionals interested in trying Windows 8 Enterprise on behalf of their organization. If you qualify under one of the following programs listed below, you may already have access to the final bits and do not need to download this 90-day evaluation.

• MSDN Subscription
  
• Microsoft Partner Network
  
• TechNet Professional Subscription
  
• Microsoft Volume Licensing/Software Assurance
  

Pete

[guenseli]

Yes, thats another one.

For my version there are no keys to insert - therefore just 90 days.

I treid to get my hands also on this free keys, but haven't worked :)

[guenseli]

ok, and I have here alog now:

removed wrong log
[/CODE]
P3D started the flight, B58 was loaded, axis working.
Entered FSUIPC menu --> I can't see my axis movement
Exit FSUIPC menue, no axis movement, but buttons work via LINDA
Then I exited FS

[guenseli]

ok, seems that haven't worked with this debug.

Here is a log again:

********* FSUIPC4, Version 4.853 by Pete Dowson *********
Running inside Prepar3D on Windows 7
... Prepar3D has been renamed as "fsx"
Module base=62F10000
User Name="Günter Steiner"
User Addr="yyyy"
FSUIPC4 Key is provided
WIDEFS7 not user registered, or expired
	   78 System time = 13/09/2012 19:48:50
	   78 FLT path = "C:\Users\Günter\Documents\Prepar3D Files\"
	   93 Trying F:\Program Files (x86)\Lockheed Martin\Prepar3D\Modules\SimConnectP3D.dll
	   93 Found it: trying to connect
	   93 FS path = "F:\Program Files (x86)\Lockheed Martin\Prepar3D\"
	  327 #### Initialising Dlrectinput Axis Scanning ...
	  327    Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_06A3&PID_0C2D\Calibration\0"
	  327    Found correct joystick Id 0
	  327    ... and a "GUID" value
	  327    ... okay, Acquired device!
	  327    Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_1DD2&PID_1001\Calibration\0"
	  327    Found correct joystick Id 1
	  327    ... and a "GUID" value
	  327    ... okay, Acquired device!
	  327    Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_06A3&PID_0763\Calibration\0"
	  327    Found correct joystick Id 2
	  327    ... and a "GUID" value
	  327    ... okay, Acquired device!
	  327    Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_044F&PID_0402\Calibration\0"
	  327    Found correct joystick Id 3
	  327    ... and a "GUID" value
	  327    ... okay, Acquired device!
	  327    Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_06A3&PID_0C2D\Calibration\0"
	  327    "Joystick Id" value = 0, not wanted this time
	  327    Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_06A3&PID_0C2D\Calibration\1"
	  327    Found correct joystick Id 4
	  327    ... and a "GUID" value
	  327    ... okay, Acquired device!
	  327    Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_044F&PID_0404\Calibration\0"
	  327    Found correct joystick Id 5
	  327    ... and a "GUID" value
	  327    ... okay, Acquired device!
	  327    Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_06A3&PID_0762\Calibration\0"
	  327    Found correct joystick Id 6
	  327    ... and a "GUID" value
	  327    ... okay, Acquired device!
	  327    joyGetDevCaps for device 7 returned error 165 [000000A5]
	  327    joyGetDevCaps for device 8 returned error 165 [000000A5]
	  327    joyGetDevCaps for device 9 returned error 165 [000000A5]
	  327    joyGetDevCaps for device 10 returned error 165 [000000A5]
	  327    joyGetDevCaps for device 11 returned error 165 [000000A5]
	  327    joyGetDevCaps for device 12 returned error 165 [000000A5]
	  327    joyGetDevCaps for device 13 returned error 165 [000000A5]
	  327    joyGetDevCaps for device 14 returned error 165 [000000A5]
	  327    joyGetDevCaps for device 15 returned error 165 [000000A5]
	  327 #### Completed Dlrectinput Axis Scanning
	  327 LogOptions=20000000 02000011
	  327 Wind smoothing fix is fully installed
	  327 G3D.DLL fix attempt installed ok
	  327 SimConnect_Open succeeded: waiting to check version okay
	  327 Trying to use SimConnect Prepar3D
	  359 VRI port 1 "com3" opened
	  795 Ready Flags: Ready-To-Fly=N, In Menu=N, In Dlg=N
	  795 Running in "Lockheed Martin® Prepar3D®", Version: 1.4.4747.0 (SimConnect: 1.4.0.0)
	  795 Initialising SimConnect data requests now
	  795 FSUIPC Menu entry added
	  811 Ready Flags: Ready-To-Fly=N, In Menu=Y, In Dlg=Y
	  811 C:\Users\Günter\Documents\Prepar3D Files\EDDT_Standard.FLT
	  811 F:\Program Files (x86)\Lockheed Martin\Prepar3D\SimObjects\Airplanes\Beech_Baron_58\Beech_Baron_58.AIR
	 2028 VRI MCP2B ("MCP2 Boeing") detected on port com3
    68110 Ready Flags: Ready-To-Fly=N, In Menu=N, In Dlg=N
    68812 System time = 13/09/2012 19:49:59, Simulator time = 19:48:53 (17:48Z)
    68812 Aircraft="Beech Baron 58 Paint1"
    69155 Starting everything now ...
    69171 LUA.0: beginning "F:\Program Files (x86)\Lockheed Martin\Prepar3D\Modules\ipcReady.lua"
    69171 LUA.0: ended "F:\Program Files (x86)\Lockheed Martin\Prepar3D\Modules\ipcReady.lua"
    69171 *** EVENT: Cntrl= 66851 (0x00010523), Param= 0 (0x00000000) VIEW_CAMERA_SELECT_1
    69171 *** EVENT: Cntrl= 65701 (0x000100a5), Param= 26 (0x0000001a) VIEW_ZOOM_SET
    69171 Ready Flags: Ready-To-Fly=Y, In Menu=N, In Dlg=N
    69186 LUA.1:

    69186 LUA.1: [INIT]LINDA:: Loading...
    69373 LUA.1: LINDA:: Aircraft: Beech Baron 58 Paint1
    69389 LUA.1: LINDA:: Aircraft module detected: FSX Default
    69420 LUA.0: LINDA:: AivlaSoft library loaded...
    69420 LUA.0: LINDA:: FSX standard library loaded...
    69436 LUA.0: LINDA:: IAO library loaded...
    69436 LUA.0: LINDA:: RealityXP library loaded...
    69451 LUA.0: LINDA:: A2A MAP library loaded...
    70309 Advanced Weather Interface Enabled
    74537 LUA.0: LINDA:: Loading a fallback joysticks config...
    74537 LUA.0: LINDA:: Loading FSX Default joysticks config...
    74553 LUA.0: LINDA:: Module: FSX Default Started...
    74553 LUA.0: LINDA:: Ready to go, Captain!
    74553 LUA.0: LINDA::
    84755 LUA.0: LINDA:: [S] FSUIPC logging bit set: 10
    95332 Sim stopped: average frame rate for last 27 secs = 25.1 fps
   110152 #### Initialising Dlrectinput Axis Scanning ...
   110152    Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_06A3&PID_0C2D\Calibration\0"
   110152    Found correct joystick Id 0
   110152    ... and a "GUID" value
   110152    DirectInput8Create failed, return = 80040154
   110152    Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_1DD2&PID_1001\Calibration\0"
   110152    Found correct joystick Id 1
   110152    ... and a "GUID" value
   110152    DirectInput8Create failed, return = 80040154
   110152    Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_06A3&PID_0763\Calibration\0"
   110152    Found correct joystick Id 2
   110152    ... and a "GUID" value
   110152    DirectInput8Create failed, return = 80040154
   110152    Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_044F&PID_0402\Calibration\0"
   110152    Found correct joystick Id 3
   110152    ... and a "GUID" value
   110152    DirectInput8Create failed, return = 80040154
   110152    Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_06A3&PID_0C2D\Calibration\0"
   110152    "Joystick Id" value = 0, not wanted this time
   110152    Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_06A3&PID_0C2D\Calibration\1"
   110152    Found correct joystick Id 4
   110152    ... and a "GUID" value
   110152    DirectInput8Create failed, return = 80040154
   110152    Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_044F&PID_0404\Calibration\0"
   110152    Found correct joystick Id 5
   110152    ... and a "GUID" value
   110152    DirectInput8Create failed, return = 80040154
   110152    Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_06A3&PID_0762\Calibration\0"
   110152    Found correct joystick Id 6
   110152    ... and a "GUID" value
   110152    DirectInput8Create failed, return = 80040154
   110152    joyGetDevCaps for device 7 returned error 165 [000000A5]
   110152    joyGetDevCaps for device 8 returned error 165 [000000A5]
   110152    joyGetDevCaps for device 9 returned error 165 [000000A5]
   110152    joyGetDevCaps for device 10 returned error 165 [000000A5]
   110152    joyGetDevCaps for device 11 returned error 165 [000000A5]
   110152    joyGetDevCaps for device 12 returned error 165 [000000A5]
   110152    joyGetDevCaps for device 13 returned error 165 [000000A5]
   110152    joyGetDevCaps for device 14 returned error 165 [000000A5]
   110152    joyGetDevCaps for device 15 returned error 165 [000000A5]
   110152 #### Completed Dlrectinput Axis Scanning
   123553 *** EVENT: Cntrl= 65732 (0x000100c4), Param= 0 (0x00000000) EXIT
   132367 System time = 13/09/2012 19:51:03, Simulator time = 19:49:41 (17:49Z)
   132367 *** FSUIPC log file being closed
Average frame rate for running time of 47 secs = 25.1 fps
G3D fix: Passes 23809, Null pointers 0, Bad pointers 0, Separate instances 0
Memory managed: 37 Allocs, 37 Freed
********* FSUIPC Log file closed ***********
[/CODE]
I have had now a look into the normal FS controls and there my joysticks are disappeared!
They do work in FS, also when I enter the FS controls menue and go back to FS.
But entering FSUIPC then makes them stop working.
So, the fault is maybe not FSUIPC (I never thoght this), the question is, why they do disappear in the FS controls menu?
And why do they work one time and then the next start not?
And I have made absolute no changes between: Starting FS, doesn't work, closing FS, do nothing, starting again: works!
hmmmm...

[guenseli]

DirectInput8Create failed, return = 80040154
[/CODE]
no, with this log, I found this post from you:
http://forum.simflight.com/topic/70834-io-cards/#entry438543
will try to update directX now, but I think this will be up to date ...

[Pete Dowson]

ok, and I have here alog now:

Yes, but with this one you didn't add that logging line I gave you, as I can see here:

	  405 LogOptions=20000000 00000001
[/CODE]

I see you added it for the next log ...
[CODE]
	  327 LogOptions=20000000 02000011

and when you forced a device rescan, these errors are certainly the cause of the problems:

110152 DirectInput8Create failed, return = 80040154

That error seems to be "class not registered", which would be related to the GUIDs and therefore the Registry. did you install Win8 clean, or as an upgrade from Win7? Maybe the registry is screwed up somewhat? The GUID for DX8 is

0xBF798030,0x483A,0x4DA2,0xAA,0x99,0x5D,0x64,0xED,0x36,0x97,0x00

but that appears to be a pre-defined fixed one. The GUIDs for the devices, which will also appear in the call which is failing, are those listed in your INI file.

Do a search on the error number on the Internet. There are lots of suggestions for fixes, but few directly related to DirectX at all -- this was the only one I found which even mentioned it:

http://www.free-codecs.com/guides/How_to_fix_Class_not_registered_or_80040154_error.htm

I have had now a look into the normal FS controls and there my joysticks are disappeared!

FSX uses the same DirectX calls as FSUIPC4, so they should fail there too, to be consistent.

They do work in FS, also when I enter the FS controls menue and go back to FS.

But entering FSUIPC then makes them stop working.

FS doesn't re-scan devices for changes, whilst FSUIPC, by default, does. I do this because it enables you to change devices, add or remove them, without restarting FS. FS doesn't allow this at all.

You can stop FSUIPC doing the auto-scanning on entry to the Options by changing

AutoScanDevices=Yes

to "No" in the INI. Then it will only re-scan if you click any of the "reload" buttons in the options.

So, the fault is maybe not FSUIPC (I never thoght this), the question is, why they do disappear in the FS controls menu?

Same reason. Evidently Win8's version of DirectX does not like programs trying to close and re-open devices! crazy. You need to submit a bug report.

And why do they work one time and then the next start not?

And I have made absolute no changes between: Starting FS, doesn't work, closing FS, do nothing, starting again: works!

Maybe it's even buggier than I just suggested? Or maybe it's because FS is opening the devices as well as FSUIPC? Have you disabled controllers completely in FS? I don't know if that stops it identifying them.

Regards

Pete

[guenseli]

Hello Pete,

did you install Win8 clean, or as an upgrade from Win7? Maybe the registry is screwed up somewhat

I installed it clean. But as I siaid I have experimented a bit and there was also a hybernation issue (which I had also in WIN7) where I have played much with (without solving it). Therefore I made some registry changings. Maybe this screwed it up.

Have you disabled controllers completely in FS?

First not as I do it for many years now by editing the stanrdard.xml and remove all entries for the joysticks (fastest way to unassign them all)

But yes I have tried this also by unchecking them in the FS menue.

What I finally wonder about:

If the error happens, means the controllers have stopped working in FS and do not show up in FS and FSUIPC menues.

Even when I do not stop FS, but just change to the device and printers window to look at the controllers properties they do show up and work there!?

I will follow the link above and search around a bit, but I think, the cleanest solution would be a complete reinstall of the OS.

I thought that would be necessary in only 66 days ...

[Pete Dowson]

First not as I do it for many years now by editing the stanrdard.xml and remove all entries for the joysticks (fastest way to unassign them all)

But yes I have tried this also by unchecking them in the FS menue.

FSX has a checkbox to turn all controllers off. Use that. It sets the "joysticks=0" entry in the FSX.CFG.

Even when I do not stop FS, but just change to the device and printers window to look at the controllers properties they do show up and work there!?

The Windows device controllers is a way in to the drivers, and a separate process. I don't understand why you'd think a process problem in FSX would apply system-wide?

Pete

[Pete Dowson]

Well, I'm stuck! I made a DVD with the ISO of the 64-bit Win8 I downloaded, but my lap top, with the Win8 32-bit preview on it, won't run the SetUp for a 64-bit version, and the damned disk doesn't boot!

I was going to set it all up and test joystick connections here for you, with the "final" release, but i can't get past this stupid situation. How can they provide a non-bootable ISO build? WinZip opens the ISO file and it shows boot stuff on it, but evidently no cylinder 0 sector 0 bootstrap file (or wherever it goes these days)? Crazy.

Looks like I need first to boot and install Win7-64 so I can run the Win8 64-bit setup! :sad:

[LATER]

Okay, I've done that ... but none of the proper drivers for my Lap Top's hardware will install under Windows 8! The video card is the main problem -- it is a full HD display (1920 x 1080) but the generic Win8 driver it installed only allows 1600x1200x16 max. The card is a GeForce Go 7400 but the nVidia drivers get as far only as saying Windows 8 isn't supported!

I'll try installing FSX to see if it'll be happy with the crappy default Win8 driver, but I have doubts. Win8 doesn't even recognise that it's a WideScreen display, so round things are elliptical!

Pete

[Pete Dowson]

Okay. FSX and Acceleration and FSUIPC all installed.

Performance, with everything at minimum, and running at a very low resolution, is abysmal -- 5 fps most of the time, down to 1-2 at night. Useless. How much of that is due to the bad video drivers and how much to Win8's apparent inappropriateness on this PC I've no idea. But when I've done proving to myself that there's nothing needing changing in FSUIPC, I'll probably reformat and go back to Win7 64 so that i can install some drivers.

Anyway, I let FSX install all it wanted, including (it said) DirectX 9.0C in the RTM FSX, and an update from the Acceleration disk. I've not gone and hunted for a later DirectX update yet -- I would have assumed that later components were not replaced by FSX installers in any case.

Took a while to work out how to close down or restart the PC. I don't understand why this is hidden away in "Settings". What has powering down to do with Settings? It's the last place I'd look (and in fact did look there almost last!).

I've connected a couple of joystick type devices and so far have had none of the problems you've reported. I'm just re-booting and trying again, then I'll look for a DX update.

Pete

[guenseli]

Thanks Pete for your searching here.

Unfortunately I have not much time this and the next days.

But I have decided already to reinstall the complete thing, anything else would not be a good solution.

Just have to find time for it; but I'll report back!

Why you have so much problems with WIN8 I do not know.

The hidden shut down is rubbish, yes.

But your low frame rates I can't confirm. FS is not running better or smoother, but in no case it's running one frame bader.

The rest of the system is running a bit better.

My conclusion for WIN8 (maybe someone reads this):

If you are happy with WIN7, stay there. The difference, especially for FSX is not that much.

If you have a bit fun of trying out new things, then try it.

There are still a few things I do not like on WIN8 (shut down, no start menue button, no desktop gagets [yes, I have used them; yes, I found Rainmeter now]). But there are also many features I like so much now that I wouldn't go back (FileHistory, Metro screen for fast information, explorer additions, fast boot and shutdown)

Hope, I get my issue solved after a reinstall (but will take a few weeks)

And I hope Pete is making his peace finally with win8 :mrgreen:

[Pete Dowson]

But your low frame rates I can't confirm. FS is not running better or smoother, but in no case it's running one frame bader.

The rest of the system is running a bit better.

Well, I'll assume it's the lack of a proper video driver. Certainly, with all sliders to the left I get 2-5 fps at best with default scenery and aircraft. I know it's only a 2 Ghz processor, but on Vista (the previous operating system on this lap top, the one it came with), I was getting 15 fps with sliders reasonably high and using the full 1920 x 1080 resolution!

And I hope Pete is making his peace finally with win8 :mrgreen:

Not till drivers have caught up, at least. The nVidia Win7 drivers refuse to install -- they may well work if they would install, but the installer simply says "not supported" and terminates.

But at least I'm sure that there is no inherent problem in the joysticks interface. I think something has become screwed up on your setup. I hope you get it resolved when installing the release version.

Regards

Pete