John Dowson

Hi all, a quick update and new version to try: FSUIPC5.txt This version contains a workaround, hopefully, and not and actual fix. Please report back if this works for you and doesn't have any other issues. There is a memory corruption somewhere and its proving difficult to track down. Whether this AI Slew/CTD problem occurs or not depends upon the memory arrangement of each build. Of course, this implies that just because this problem doesn't occur, it doesn't mean that there still isn't a memory corruption issue, just that its moved to some other place, which is worrying....! We will be continuing to investigate this issue to determine the source of the corruption. Its still not clear if this is caused by FSUIPC or P3D itself. Cheers, John

The newlines go in the format string, so something like string.format("%-3s\n%-6s\n%-5s ", str_var1, str_var2, str_var3)

Hi Tasso, not sure what you mean by this. This knob must be that operated by the following controls: TRUE AIRSPEED CAL DEC 65886 TRUE AIRSPEED CAL INC 65885 TRUE AIRSPEED CAL SET 66043 There is currently no offset available for reading the calibration value. There is a SIMVAR available: AIRSPEED TRUE CALIBRATE Angle of “True” calibration scale on airspeed indicator Degrees Y but this is not currently published to the FSUIPC offsets. I could add for FSUIPC5 (P3D), but FSUIPC4 is closed for future development - sorry. John

notepad++

Hi Peter, Presume you mean WideClient, which is part of WideFS. It may be that the network (or other services) may not be available yet when auto starting. Do you have anything in your event log? Could you also try adding Log=Debugall to the [user] section of your WideClient.ini (or add the [user] section if not already there). Then post the log when you get the crash. The log file may be quite large but zips up nicely. John

Ah yes, I remember now - thanks Roman. There's a similar post but for spot view, so this thread may be of interest:

If you are assigning as 'Send direct to FSUIPC Calibration', as you say, then you should see the following throttle controls: Throttle, Throttle/SlewAlt, Throttle1, Throttle2, Throttle3, Throttle4. The 'Axis Throttle Set' controls are only available when you send direct to FS. As Reinhard says, some add-ons do not play well with FSUIPC calibration and for these you should use 'Send to FS as normal axis'. John

No, I don't think you can assign to change to a specific view. Generally you assign a button to the 'VIEW_MODE' control, which will cycle through the 7 view modes (Cockpit, Outside, Tower, Aircraft, Runway, Air Traffic and Sensor) and then another to the 'NEXT_SUB_VIEW', which cycles through the sub-views of the selected view mode. As the controls provided only allow you to cycle through the different modes, I don't think its possible to toggle to a specific view.

No problem - glad its all now working for you. John

Sounds like you have a corrupt weather file somewhere. Usually its the wxstationlist.bin file, in the same directory as your fsx.cfg file. Try deleting/renaming that first - a new one should be created when you restart the sim.

Do you have any other events just before the crash event? Can you try disabling weather by adding NoWeatherAtAll=Yes to the [General] section of you ini. If that doesn't work then we'll add some logging flags. I'm away from my PC for a while, but Pete will be back next week if you don'y hear from me before then.

Hi Raj, you don't assign to a 'joystick trigger', you assign to controls. Your 'joystick trigger' will also be sending a control - just assign your mouse button to the same control that your trigger is sending (on press and release, if applicable). If you don't know what control its sending, you can activate event and button logging (from the fsuipc logging tab) to see whats being sent.

Hi, maybe try without having the a320 as your default aircraft in your default flight - your log shows this is still there, although I'm not sure that this matters but worth a try. Many people seem to have problems with add-on aircraft unless the sim is initialised with a default aircraft first. Defender updates shouldn't effect things, but you never know with windows, and the timing is suspicious. Maybe check your defender logs after the update to see if they show anything. Did you not manage to re-register (or retrieve your old key file)?

Also, presumably this was previously working. What did you change?

Log and ini files?

As the documentation says, you can read both 0574 (for altitude in metres) and 0570 (for fractional part) and combine them, or just read 6020 which is the altitude as a a 64bit double floating point.

Many add-on aircraft, PMDG especially, ignore or even re-purpose many of the P3D controls and also use their own. For PMDG aircraft, please see this FAQ article:

Hi, for the crash problem, please try with LINDA disabled (rename your ipcReady.lua to ipcReady.notUsed - you can change it back later). Also try with loading a default aircraft first, then switching to the A320. When re-installing there is no need to register, you can skip the registration and your previous key file will be used. However, your details are still valid. All 3 field (name, email, key) must be exactly right - best to cut and paste from your registration email. Please don't post the dll - this is not needed. Generally you should post the log and ini files if you have any issues (and install log if you have installation problems) and we can advise from there.

Also, why do you have controls being sent when your axis go into and out of 0 (right hand side of Axis Assignment)? 1=0X,B,0,0,65697,0 -{ TO SIM: THROTTLE_SETEntering=THROTTLE_SET }- 3=0Y,B,0,0,65767,0 -{ TO SIM: PROP_PITCH_SETEntering=PROP_PITCH_SET }- 5=0Z,B,0,0,66292,0 -{ TO SIM: AXIS_MIXTURE_SETEntering=AXIS_MIXTURE_SET }- 7=1X,B,0,0,65695,0 -{ TO SIM: AILERON_SETEntering=AILERON_SET }- 9=1Y,B,0,0,65694,0 -{ TO SIM: ELEVATOR_SETEntering=ELEVATOR_SET }- 11=2X,B,0,0,66387,0 -{ TO SIM: AXIS_LEFT_BRAKE_SETEntering=AXIS_LEFT_BRAKE_SET }- 13=2Y,B,0,0,66388,0 -{ TO SIM: AXIS_RIGHT_BRAKE_SETEntering=AXIS_RIGHT_BRAKE_SET }- 15=2R,B,0,0,65696,0 -{ TO SIM: RUDDER_SETEntering=RUDDER_SET }- I'm not sure what purpose these serve, if any. John

Using an axis for gear-up/gear-down is also the example in the FSUIPC user manual, page 37. John

Just checked and it seems that you can calibrate the other axis (aileron, elevator and rudder) without using the corresponding axis set command, but not with throttle. Not sure why this is, I'll look into it. John

You need to use 'Axis Throttle Set' and not 'Throttle Set' if you want to calibrate as an axis. Or set to 'send Direct to FSUIPC Calibration' and use the Throttle or Throttle/SlewAlt control, but you must calibrate if you send it this way. Also applies to your Aileron, Elevator and Rudder. John

The version on SimMarket is 5.151, and the ones posted since on other posts have been later versions - 5.151a, & 5.151b. Could @Drumcodeand @UniformAlpha2014 therefore please try 5.15.. 5.15 is attached - rename to FSUIPC5.dll once downloaded. FSUIPC5.txt

Does that mean 5.15 doesn't work for you?

Do you mean 5.15? @UniformAlpha2014 reports 5.11 being ok, but I assumed that was a typo. I can post 5.15 if you really need it (i.e. reducing AI traffic is not an option), but this is not supported, so please don't post any issues if you use it. Let me know. I'm pretty certain that the problem is due to heap corruption somewhere, but its a bugger to track down. The release (commit) where the problem first arises is not related to where the problem was introduced. Any heap analysis tool I've tried crashes in P3D before it even touches the FSUIPC code, which is also worrying (and am working on to raise with LM). Thanks for all the info so far, but no point in posting more really - just adding noise to the topic. Cheers, John