Jump to content
The simFlight Network Forums

Recommended Posts

Posted

In trouble shooting a new Jetmax 737NG build, I keep seeing changing JetMax throttle, and PFC yoke & rudder USB assignments in P3D-V3 with FSUIPC 4.948.  This in turn results in a mostly unusable sim since some of the controls don't respond to inputs.  See examples here:

 

First P3D startup (only operational control was the yoke)
 
[JoyNames]
AutoAssignLetters=No
0=PFC Rudder Pedals
0.GUID={184D3590-72AD-11E5-8001-444553540000}
1=PFC Cirrus Yoke
1.GUID={6527A820-72AB-11E5-8001-444553540000}
2=JetMAX 737 Throttle
2.GUID={432B3EA0-8181-11E5-8001-444553540000}
 
2nd Startup of P3D:  (did not reboot PC - note change in USB joystick assignments - this assignment works correctly except still no rudder control)
 
[JoyNames]
AutoAssignLetters=No
0=JetMAX 737 Throttle
0.GUID={432B3EA0-8181-11E5-8001-444553540000}
1=PFC Cirrus Yoke
1.GUID={6527A820-72AB-11E5-8001-444553540000}
2=PFC Rudder Pedals
2.GUID={184D3590-72AD-11E5-8001-444553540000}
 
Do I need to utilize the JoyNames utility?  I thought I read that with 4.948, that was no longer necessary.
 
Thanks,
Gordon
Posted

 

In trouble shooting a new Jetmax 737NG build, I keep seeing changing JetMax throttle, and PFC yoke & rudder USB assignments in P3D-V3 with FSUIPC 4.948.  This in turn results in a mostly unusable sim since some of the controls don't respond to inputs.  See examples here:

 

First P3D startup (only operational control was the yoke)
 
[JoyNames]
AutoAssignLetters=No
0=PFC Rudder Pedals
0.GUID={184D3590-72AD-11E5-8001-444553540000}
1=PFC Cirrus Yoke
1.GUID={6527A820-72AB-11E5-8001-444553540000}
2=JetMAX 737 Throttle
2.GUID={432B3EA0-8181-11E5-8001-444553540000}
 
2nd Startup of P3D:  (did not reboot PC - note change in USB joystick assignments - this assignment works correctly except still no rudder control)
 
[JoyNames]
AutoAssignLetters=No
0=JetMAX 737 Throttle
0.GUID={432B3EA0-8181-11E5-8001-444553540000}
1=PFC Cirrus Yoke
1.GUID={6527A820-72AB-11E5-8001-444553540000}
2=PFC Rudder Pedals
2.GUID={184D3590-72AD-11E5-8001-444553540000}

 

That's very strange indeed. I have no explanation at present. I need more information.

 

Can you please add the following lines to the [General] section of the INI file:

 

Debug=Please

LogExtras=x200000

 

then run it twice again, as you have above, sdaving the FSUIPC4 LOG file for each. I need to see those logs to work out what is going on.

 

Do I need to utilize the JoyNames utility?  I thought I read that with 4.948, that was no longer necessary.

 

 

Where did you read that? Using Joy Letters would certainly allow FSUIPC to maintain your assignments no matter what joystick ID numbers were assigned.  But then you might not have noticed the numbers changing. I need to find out why that is happening in any case.

 

Pete

Posted

The PC seems to have stabilized for now.  Thank you for your response and I will reach out to you again it this problem reoccurs again.  

 

Thanks,

 

Gordon

Posted

The PC seems to have stabilized for now.  Thank you for your response and I will reach out to you again it this problem reoccurs again.  

 

Ok. I'm still a bit concerned that it might have been related to the new code I added to scan joysticks and assign ID numbers to those which don't have them -- as seems to be the case with the default installs of some drivers for Win8 and Win10. So if it does happen again, please do show me the logs with those added lines in the INI file.

 

Incidentally, I'm away from this afternoon till December 7th in any case.

 

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.