Jump to content
The simFlight Network Forums


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About rocketman3

  • Rank
  1. Pete, I've been using with the calibration approach you recommended (creating a null zone for the brakes) and it seems to be more stable. I've had the odd crash or two but that may be from something else. I'm running most of my add-ons now as well. I'll run with this configuration for a while and see how it goes. Regards, Glenn
  2. Pete, I have played around with some other configurations, but the only time I see the crash is with the brakes configured through FSUIPC as before. I will try the calibration suggestions you made and the new version and let you know if I see it again. Thanks! Glenn
  3. Pete, For what it's worth, I did run memory diagnostics and everything passed. I'm not having any stability problems with any other software. I use this machine primarily for video editing and other multimedia work. These programs may not use pipes, but they are very memory intensive. Regards, Glenn
  4. Pete, I went back to the configuration that caused the crash and ran till FSX failed again to confirm. Here's the FSUIPC calibration and axis configuration (I had also deleted the brake axis assignments in FSX): [JoystickCalibration] ExcludeThrottleSet=Yes ExcludeMixtureSet=Yes ExcludePropPitchSet=Yes SepRevsJetsOnly=No ApplyHeloTrim=Yes 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=-16384,-3382,0,16383 Elevator=-16384,18,18,16383 Rudder=-15473,512,1024,16128 Throttle=-16384,16383 SlopeAileron=1 SlopeElevator=1 SlopeRudder=1 LeftBrake=-16384,15744/16 RightBrake=-16384,15488/16 [Axes] 4=1Y,256,D,8,0,0,0 5=1Z,256,D,3,0,0,0 0=0X,256,D,1,0,0,0 1=0Y,256,D,2,0,0,0 2=0S,256,D,4,0,0,0 3=1X,256,D,7,0,0,0 Seems strange to me as well. I wonder if there is something causing a value out of range or otherwise bad data to be sent to FSUIPC from the CHPro brakes? If so, could FSUIPC be sending these bad values to SimConnect as command parameters? Perhaps FSX can't handle that? (I'm speculating, of course). Could this be what the log entries " Exception 2 "SIZE_MISMATCH"" and "EXCEPTION=2, SendID=11209, Index=0 <<<<< Unrecognized Data Received" are referring to? So far I have tried "Axis assign in FSUIPC, Direct to FSUIPC calibration" and "Axis assign in FS, no calibration in FSUIPC". The former triggers the crash, the later seems to be stable. I'll play around with some of the other combinations you listed and see what results I get. Regards, Glenn
  5. Pete, After a lot of testing different configurations (I can give you the list if you're interested), the bottom line is that if I run FSUIPC and configure the brake axis in it (Axis Assignments - Rescan, move brake pedal, Type of action required - Send direct to FSUIPC Calibration - LeftBrake or RightBrake, repeat for other side, calibrate via Joystick Calibration tab) the problem reproduces. I have CHPro USB pedals and I'm not using their Manager. To workaround it, I deleted the brake assignments in FSUIPC and added the brake axis in FSX. I'm happy with this configuration (FSUIPC for all other axis except brakes). I have run for many hours this way without a crash, even with other add-ons installed. Again, I'm not drawing any conclusions as to where the root cause is. I'm an Enterprise Architect with a major software company and I know how easy it is for some to jump to conclusions. The problem could be in the driver stack, Directx, some other part of Windows, FSX, FSUIPC or somewhere else. The only thing I'm saying is that this workaround seems to be effective in my case. Thanks for your support. I am very impressed with your personal attention to problem reports. Regards, Glenn
  6. Pete, I'm using the production release of SP1 http://technet.microsoft.com/en-us/windowsvista/bb738089.aspx (never did use the Beta). No add-ons right now. I'll do as you suggest. Just finished a 2+ hour flight with no problems. I'll try turning on FSUIPC next and see what happens. Thanks, Glenn
  7. Pete, I have 4GB RAM and I'm running Vista Home Premium SP1. Task Manager reports Physical Memory as 3325MB (this is normal for 32 bit OS). I've disabled the add-ons using FS Startup Editor (handy!) and have been running about an hour now with no problems. Task Manager reports FSX is using 1,038,028K RAM and it's steady. Regards, Glenn
  8. Pete, Thanks again for responding so quickly and completely. I really appreciate it. Sorry if I didn't describe ALL of the steps I have taken. I have spent quite a bit of time on this and tried to give you the important points. I see now that I did not. When the failures started to occur, I was working with my full install, which included add-ons. I tried to eliminate them one by one to see if I could narrow down the list, but in the end I couldn't. So I uninstalled FSX, cleaned the registry, renamed the FSX folder to Microsoft Flight Simulator X OLD, then reinstalled only FSX and Acceleration to the default Microsoft Flight Simulator X folder. After testing for a while with the clean install, I had no issues and started to reinstall a few add-ons to see if I could trigger the fault. I did install FSForce (a force feedback enhancement) and TrackIR. In testing I had no problems with either of these. However, you have a point that I should remove those until we get to a root cause. I believe the Aircreation 582 is a standard FSX aircraft (http://www.fsinsider.com/product/features/Pages/aircraft.aspx). I didn't add on or modify anything like this. I switched to the Caravan simply to get a plane with good duration and an autopilot for testing purposes. This plane has not been modified either. I will try deleting FSX.CFG and see if that makes a difference. I will also check out the memory and see where that leads. Thanks much, Glenn
  9. Pete, Thanks for the quick reply. I tried everything I could first so as not to waste your time. I will do as you suggest. Thanks again for the assist. Regards, Glenn
  10. Pete, I'm having some trouble with FSX/FSUIPC and I wonder if you can help. I recently purchased a license for FSUIPC and began using it. I really like the functionality, especially for calibrating my joystick and pedals. However, I'm having consistent crashes to desktop. I have spent a lot of time troubleshooting and testing by flying long flights on autopilot, and here's what I found: - Removed FSX, cleaned registry, reinstalled FSX: No crashes (ran for several days) - Installed FSUIPC: Crashes (typically within an hour, sometimes much sooner. I don't assume that this means FSUIPC is the root cause) - Disable virus scan: Still crashes - Updated graphic drivers: Still crashes - Disabled TrackIR: Still crashes - Installed CH Control Manager: Still crashes (removed it after testing) - Remove FSUIPC.dll from Modules: No crashes overnight (Again, I don't assume that this means FSUIPC is the root cause) - Updated FSUIPC to version 4.264: Still crashes - Reset defaults in FSUIPC, removed joystick calibration: Still crashes I have tried different aircraft, different locations, different/default graphic settings, etc. with no success. I enabled all FSUIPC logs and for each crash, I opened the log and checked for errors. I'm consistently finding the following message within the last few lines of the log: Exception 2 "SIZE_MISMATCH", Ref 22497, Index param 0 on unknown request! (The value following "Ref" changes each time.) Also, I see the following errors/exceptions in the beginning of each log: 32988 Exception 3 "UNRECOGNIZED_ID", Ref 2346, Index param -1 on unknown request! 65977 Error 126 (The specified module could not be found. ) "C:\Program Files\Microsoft Games\Microsoft Flight Simulator X\Modules\PFCFSX.DLL" 65977 Error 126 (The specified module could not be found. ) "C:\Program Files\Microsoft Games\Microsoft Flight Simulator X\Modules\EPICINFO5.DLL" I don't use either PFC or Epic. The Windows Event Viewer shows faults in either MSVCR80.dll or API.dll: Faulting application fsx.exe, version 10.0.61637.0, time stamp 0x46fadb14, faulting module MSVCR80.dll, version 8.0.50727.1434, time stamp 0x4757746d, exception code 0xc000000d, fault offset 0x00008aa0, process id 0x884, application start time 0x01c898ceb7180227. Faulting application fsx.exe, version 10.0.61637.0, time stamp 0x46fadb14, faulting module API.DLL, version 10.0.61637.0, time stamp 0x46fadb58, exception code 0xc0000005, fault offset 0x000176f6, process id 0x5d0, application start time 0x01c898d037613c77. I have searched the documentation, the forums and the Internet and cannot find a reference to a similar case. My system is a Dell XPS-420, Intel Q6850 quadcore @ 3.00GHz, 4GB RAM, Vista Home Premium SP1. User Account Control is Off, and the user account I'm running FSX with has full control of the FSX folder and below, including the Modules folder. I use a Logitech Wingman Force joystick and CH Pro pedals. I have FSX SP2 with Acceleration. Any insights you might have would be greatly appreciated! Regards, Glenn
  • 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.