Jump to content
The simFlight Network Forums

FSUIPC5 causes a CTD - ucrtbase.dll


Recommended Posts

All of a sudden FSUIPC5 causes a CTD  of P3d V4 - ucrtbase.dll violation. It did work before.

It seems to be a part of vs 2015 runtime

Windows 10 64-bit, both FSUIPC 5.10 & 5.101, Prepar3D v4 Academic 4.0.23.21468

Addons: Chaseplane. AS2016/ASCA, GSX, Aerosoft Twin Otter, ORBX Global Base - LC Europe - Libs

Installed runtimes:

Link

Any suggestions ?

 

Many happy landings

Andi

Link to comment
Share on other sites

2 hours ago, ITholic said:

Any suggestions ?

Seems to affect a few users and has already been reported. Is it occurring during a session, or when P3D4 is still on the Splash Sctreen?

I need to see the FSUIPC5.INI and the FSUIPC5.LOG, both from the Modules folder, please.

Pete

 

Link to comment
Share on other sites

Hi Pete

It crashes on the splash screen - but only if the joystick is not connected ... 

 

Without Joystick:

********* FSUIPC5, Version 5.101 (4th June 2017) by Pete Dowson *********
Windows 10 Home 64 Bit reported as Build 14393, Release ID: 1607 (OS 10.0)
FSUIPC5.dll version = 5.1.0.1
Reading options from "D:\Prepar3D v4\Modules\FSUIPC5.ini"
Running inside Prepar3D v4 on Windows 10
Module base=7FFE3E460000
User Name="Andreas Giel"
User Addr="andreas.giel@web.de"
FSUIPC5 Key is provided
WIDEFS7 not user registered, or expired
      110 System time = 06/06/2017 20:46:30
      110 FLT path = "C:\Users\Andi\Documents\Prepar3D v4 Files\"
      110 ------ Module Version Check ------
      110        acontain.dll: 4.0.23.21468
      110             api.dll: 4.0.23.21468
      110        controls.dll: 4.0.23.21468
      110      fs-traffic.dll: 4.0.23.21468
      110             G3D.dll: 4.0.23.21468
      110        language.dll: 4.0.23.21468
      110            sim1.dll: 4.0.23.21468
      110        visualfx.dll: 4.0.23.21468
      110         weather.dll: 4.0.23.21468
      110          window.dll: 4.0.23.21468
      110 ----------------------------------
      110 FS path = "D:\Prepar3D v4\"
      266 ---------------------- Joystick Device Scan -----------------------
      266 Product= <not readable at this time: maybe device disconnected?>
      266    Vendor=0CF2, Product=9010 (Version 1.1)
      266 -------------------------------------------------------------------

With joystick connected:

********* FSUIPC5, Version 5.101 (4th June 2017) by Pete Dowson *********
Windows 10 Home 64 Bit reported as Build 14393, Release ID: 1607 (OS 10.0)
FSUIPC5.dll version = 5.1.0.1
Reading options from "D:\Prepar3D v4\Modules\FSUIPC5.ini"
Running inside Prepar3D v4 on Windows 10
Module base=7FFE3B7F0000
User Name="Andreas Giel"
User Addr="andreas.giel@web.de"
FSUIPC5 Key is provided
WIDEFS7 not user registered, or expired
        0 System time = 06/06/2017 20:43:53
        0 FLT path = "C:\Users\Andi\Documents\Prepar3D v4 Files\"
        0 ------ Module Version Check ------
        0        acontain.dll: 4.0.23.21468
        0             api.dll: 4.0.23.21468
        0        controls.dll: 4.0.23.21468
        0      fs-traffic.dll: 4.0.23.21468
        0             G3D.dll: 4.0.23.21468
      156        language.dll: 4.0.23.21468
      156            sim1.dll: 4.0.23.21468
      156        visualfx.dll: 4.0.23.21468
      156         weather.dll: 4.0.23.21468
      156          window.dll: 4.0.23.21468
      156 ----------------------------------
      156 FS path = "D:\Prepar3D v4\"
      296 ---------------------- Joystick Device Scan -----------------------
      296 Product= Mad Catz F.L.Y.5 Stick
      296    Manufacturer= Mad Catz
      296    Vendor=0738, Product=1302 (Version 1.51)
      328    GUIDs returned for product: VID_0738&PID_1302:
      328       GUID= {07C4D920-913A-11E5-8006-444553540000}
      328       Details: Btns=14, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R255,U255,V0,X1023,Y1023,Z255
      328 Product= <not readable at this time: maybe device disconnected?>
      328    Vendor=0CF2, Product=9010 (Version 1.1)
      328 -------------------------------------------------------------------
      328 Device acquired for use:
      328    Joystick ID = 1 (Registry okay)
      328    1=Mad Catz F.L.Y.5 Stick
      328    1.GUID={07C4D920-913A-11E5-8006-444553540000}
      328 Device acquired for use:
      328    Joystick ID = 1 (Registry okay)
      328    1=
      328    1.GUID={07C4D920-913A-11E5-8006-444553540000}
      328 -------------------------------------------------------------------
      359 LogOptions=00000000 00000001
      359 -------------------------------------------------------------------
      359 SimConnect_Open succeeded: waiting to check version okay
      359 Opened separate AI Traffic client okay
     8875 Running in "Lockheed Martin® Prepar3D® v4", Version: 4.0.23.21468 (SimConnect: 4.0.0.0)
     8875 Initialising SimConnect data requests now
     8875 FSUIPC Menu entry added
     8875 ... Using Prepar3D with Academic License
     8890 C:\Users\Andi\AppData\Local\Lockheed Martin\Prepar3D v4\Prepar3D_Default.fxml
     8890 D:\Prepar3D v4\SimObjects\Airplanes\IRIS Raptor Driver\Raptor.air
    69343 User Aircraft ID 2 supplied, now being used
    69359 Aircraft loaded: running normally now ...
    70312 System time = 06/06/2017 20:45:04, Simulator time = 14:00:03 (19:00Z)
    70312 Aircraft="F-22 Raptor - 525th Fighter Squadron"
    77312 Starting everything now ...
    77343 ASN active function link set
    77343 Ready for ASN WX radar
    83187 Advanced Weather Interface Enabled
    89671 === Closing session: waiting for DLLStop to be called ...
 

Many happy landings

 

Andi

Link to comment
Share on other sites

51 minutes ago, ITholic said:

It crashes on the splash screen - but only if the joystick is not connected ...

Yes, thank you. this is actually the same problem as already covered at length in another thread (with a misleading title, unfortunately, "FSUIPC REG not working". But ytou're the first to confrm what some of the other logs had indicated -- that it's related to the joystick scan and what happens when there aren't any.

Therefore, i would be grateful if you could do another pair of tests, the same as those you have posted, but first add the following two lines to the [General] section of the FSUIPC5.INI file:

Debug=Please
LogExtras=x200000

This will log the scanning in more detail. Please sohw me the resulting logs.

Odd that I have three PCs here running P3D4 yet cannot reproduce this.

Thank you,
Pete

 

Link to comment
Share on other sites

You're welcome Pete!

Here you are:

 

********* FSUIPC5, Version 5.101 (4th June 2017) by Pete Dowson *********
Windows 10 Home 64 Bit reported as Build 14393, Release ID: 1607 (OS 10.0)
FSUIPC5.dll version = 5.1.0.1
Reading options from "D:\Prepar3D v4\Modules\FSUIPC5.ini"
Running inside Prepar3D v4 on Windows 10
Module base=7FFED9F60000
User Name="Andreas Giel"
User Addr="andreas.giel@web.de"
FSUIPC5 Key is provided
WIDEFS7 not user registered, or expired
      125 System time = 06/06/2017 23:22:45
      125 FLT path = "C:\Users\Andi\Documents\Prepar3D v4 Files\"
      125 ------ Module Version Check ------
      125        acontain.dll: 4.0.23.21468
      125             api.dll: 4.0.23.21468
      125        controls.dll: 4.0.23.21468
      125      fs-traffic.dll: 4.0.23.21468
      125             G3D.dll: 4.0.23.21468
      125        language.dll: 4.0.23.21468
      125            sim1.dll: 4.0.23.21468
      125        visualfx.dll: 4.0.23.21468
      125         weather.dll: 4.0.23.21468
      125          window.dll: 4.0.23.21468
      125 ----------------------------------
      125 FS path = "D:\Prepar3D v4\"
      282 #### Initialising Dlrectinput Axis Scanning ...
      282    (Entry from GetRegisteredOptions)
      282 ---------------------- Joystick Device Scan -----------------------
      282 Checking: \\?\hid#ene0110#6&39a4dcf9&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
      282    Usage=12, UsagePage=1, =Flight Mode Switch
      282 Error 1 [00000001] returned on HidD_GetProductString:  (\\?\hid#ene0110#6&39a4dcf9&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030})
      282 Product= <not readable at this time: maybe device disconnected?>
      282    Vendor=0CF2, Product=9010 (Version 1.1)
      282 -------------------------------------------------------------------
      282 ****** Registry scanning: VID=0CF2, PID=9010 ******
      282 Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_0CF2&PID_9010\Calibration\0"
      282    ... and a "GUID" value
      282    GUID= {07C10890-913A-11E5-8003-444553540000}
      282        NB: not valid for this device according to GetConfig!

Link to comment
Share on other sites

My FSUIPC5.ini:

[General]
UpdatedByVersion=5101
History=M9XYYZWPN4W159JO5B4PG
InitDelayDevicesToo=No
Annotate=Yes
NewInterceptTextMenu=No
UseSystemTime=No
UseMidMouseBtn=Yes
MouseWheelMove=No
MouseWheelTrim=No
MouseWheelTrimSpeed=1
JoystickTimeout=20
FixControlAccel=No
FixMachSpeedBug=No
AutoScanDevices=Yes
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
TimeForSelect=4
LoadFlightMenu=No
LoadPlanMenu=No
PauseAfterCrash=No
BrakeReleaseThreshold=75
SaveDataWithFlights=No
ZapSound=firework
ShortAircraftNameOk=Substring
UseProfiles=Yes
EnableMouseLook=No
DelayedMouseLookZoom=No
WideLuaGlobals=Yes
AxesWrongRange=No
TCASid=Flight
TCASrange=40,3
AxisCalibration=No
DirectAxesToCalibs=No
ShowMultilineWindow=Yes
SuppressSingleline=No
SuppressMultilineFS=No
AxisIntercepts=No
DontResetAxes=No
ThreadAffinityMask=x0
LuaAffinityMask=x0
InitDelay=0
GetNearestAirports=Yes
LogOptionProtect=Yes
TimeForLuaClosing=2
WeatherReadFactor=2
WeatherRewriteSeconds=1
CustomWeatherModify=No
SimConnectStallTime=1
InitialStallTime=10
NormalStallTime=1
LuaRerunDelay=66
Console=No
Debug=Please
LogExtras=x200000

[Traffic Limiter]
AirportPreference=50
PlannedAirportsPreference=50
GroundPreference=50
NearerPreference=50
TargetFrameRate=0
TrafficLimit=0

[JoyNames]
AutoAssignLetters=No
1=
1.GUID={07C4D920-913A-11E5-8006-444553540000}

[Axes]
PollInterval=10
RangeRepeatRate=10
0=1X,256,D,1,0,0,0    -{ DIRECT: Aileron }-
1=1Y,256,D,2,0,0,0    -{ DIRECT: Elevator }-
2=1Z,256,D,9,0,0,0    -{ DIRECT: Throttle1 }-
3=1R,256,D,3,0,0,0    -{ DIRECT: Rudder }-
4=1S,256,D,10,0,0,0    -{ DIRECT: Throttle2 }-

[Buttons]
PollInterval=25
ButtonRepeat=20,10
1=R1,9,C65602,0     -{THROTTLE_DECR}-
2=P1,10,C65853,0     -{SPOILERS_ARM_TOGGLE}-
3=P1,13,C65570,0     -{GEAR_TOGGLE}-
4=P1,8,C65758,0     -{FLAPS_INCR}-
5=P1,7,C65759,0     -{FLAPS_DECR}-
6=R1,2,C65615,0     -{ELEV_TRIM_UP}-
7=R1,4,C65607,0     -{ELEV_TRIM_DN}-
8=R1,0,C65588,0     -{BRAKES}-

[AutoSave]
Next=1
Interval=60
Files=10
SaveOnGround=No
AutoSaveEnabled=No

[GPSout]
GPSoutEnabled=No

[GPSout2]
GPSoutEnabled=No

[WideServer]
WideFSenabled=Yes

[Sounds]
Path=D:\Prepar3D v4\Sound\
Device1=Primärer Soundtreiber
Device2=Lautsprecher (Realtek High Definition Audio)
Device3=Realtek Digital Output (Realtek High Definition Audio)
Device4=Lautsprecher (XSplit  Stream  Audio  Renderer)

[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=-16384,0,32,16383
Elevator=-16384,-257,-161,16383
Rudder=-16384,-130,128,16383
Throttle1=-16384,-512,512,16383/32
Throttle2=-16384,-512,512,16383/32
 

Link to comment
Share on other sites

Thanks.

Your registry / DirectInput result are the same as at least one other with this problem: a "Flight Mode Switch":

      282 ---------------------- Joystick Device Scan -----------------------
      282 Checking: \\?\hid#ene0110#6&39a4dcf9&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
      282    Usage=12, UsagePage=1, =Flight Mode Switch
      282 Error 1 [00000001] returned on HidD_GetProductString:  (\\?\hid#ene0110#6&39a4dcf9&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030})
      282 Product= <not readable at this time: maybe device disconnected?>
      282    Vendor=0CF2, Product=9010 (Version 1.1)
      282 -------------------------------------------------------------------
      282 ****** Registry scanning: VID=0CF2, PID=9010 ******
      282 Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_0CF2&PID_9010\Calibration\0"
      282    ... and a "GUID" value
      282    GUID= {07C10890-913A-11E5-8003-444553540000}
      282        NB: not valid for this device according to GetConfig!

He says he doesn't have one either!

Another very odd thing is that it gets into the INI:

[JoyNames]
AutoAssignLetters=No
1=
1.GUID={07C4D920-913A-11E5-8006-444553540000}

albeit with no name (which was unreadable), yet the log doesn't get that far -- might that section have been created by an earlier session. I see from the Calibrations that you must have had a device operating at some stage.

Anyway, now please try 

FSUIPC5101d_TEST.zip

still with these lines added to the[General] section of the FSUIPC5.INI file:

Debug=Please
LogExtras=x200000

and please show me the Log file after, no matter what the result.

Pete

 

 

Link to comment
Share on other sites

No CTD on loading Prepar3D v4 without the joystick now using 5101d :

********* FSUIPC5, Version 5.101d (7th June 2017) by Pete Dowson *********
Running inside Prepar3D v4
Module base=7FFEF7410000
Windows 10 Home 64 Bit reported as Build 14393, Release ID: 1607 (OS 10.0)
Prepar3D.exe version = 4.0.23.21468
Checking the Registrations now ...
User Name="Andreas Giel"
User Addr="andreas.giel@web.de"
FSUIPC5 Key is provided
WIDEFS7 not user registered, or expired
       63 System time = 07/06/2017 06:48:44
       63 FLT path = "C:\Users\Andi\Documents\Prepar3D v4 Files\"
       63 ------ Module Version Check ------
       63        acontain.dll: 4.0.23.21468
       63             api.dll: 4.0.23.21468
       63        controls.dll: 4.0.23.21468
       63      fs-traffic.dll: 4.0.23.21468
       63             G3D.dll: 4.0.23.21468
       78        language.dll: 4.0.23.21468
       78            sim1.dll: 4.0.23.21468
       78        visualfx.dll: 4.0.23.21468
       78         weather.dll: 4.0.23.21468
       78          window.dll: 4.0.23.21468
       78 ----------------------------------
       94 FS path = "D:\Prepar3D v4\"
      235 #### Initialising Dlrectinput Axis Scanning ...
      235    (Entry from GetRegisteredOptions)
      235 ---------------------- Joystick Device Scan -----------------------
      235 Checking: \\?\hid#ene0110#6&39a4dcf9&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
      235    Usage=12, UsagePage=1, =Flight Mode Switch
      235 -------------------------------------------------------------------
      235 -------------------------------------------------------------------
      235 UserDevices: 1.GUID={07C4D920-913A-11E5-8006-444553540000}
      235 ---------- Making INI JoyNames Section ----------
      235     wJoyIDsUsed=0000
      235 -------------------------------------------------
      235   Checking and assigning Joy Letters as needed
      250 #### Completed Dlrectinput Axis Scanning
      266 LogOptions=00000000 02000011
      266 SimConnect_Open succeeded: waiting to check version okay
      266 Opened separate AI Traffic client okay
    18750 Running in "Lockheed Martin® Prepar3D® v4", Version: 4.0.23.21468 (SimConnect: 4.0.0.0)
    18750 Initialising SimConnect data requests now
    18750 FSUIPC Menu entry added
    18782 ... Using Prepar3D with Academic License
    18844 Ready Flags: Ready-To-Fly=N, In Menu=Y, In Dlg=Y
    18844 C:\Users\Andi\AppData\Local\Lockheed Martin\Prepar3D v4\Prepar3D_Default.fxml
    18844 D:\Prepar3D v4\SimObjects\Airplanes\IRIS Raptor Driver\Raptor.air

 

Log using joystick:

********* FSUIPC5, Version 5.101d (7th June 2017) by Pete Dowson *********
Running inside Prepar3D v4
Module base=7FFEF7410000
Windows 10 Home 64 Bit reported as Build 14393, Release ID: 1607 (OS 10.0)
Prepar3D.exe version = 4.0.23.21468
Checking the Registrations now ...
User Name="Andreas Giel"
User Addr="andreas.giel@web.de"
FSUIPC5 Key is provided
WIDEFS7 not user registered, or expired
        0 System time = 07/06/2017 06:51:33
        0 FLT path = "C:\Users\Andi\Documents\Prepar3D v4 Files\"
        0 ------ Module Version Check ------
        0        acontain.dll: 4.0.23.21468
        0             api.dll: 4.0.23.21468
        0        controls.dll: 4.0.23.21468
        0      fs-traffic.dll: 4.0.23.21468
        0             G3D.dll: 4.0.23.21468
        0        language.dll: 4.0.23.21468
        0            sim1.dll: 4.0.23.21468
        0        visualfx.dll: 4.0.23.21468
        0         weather.dll: 4.0.23.21468
        0          window.dll: 4.0.23.21468
        0 ----------------------------------
       16 FS path = "D:\Prepar3D v4\"
      157 #### Initialising Dlrectinput Axis Scanning ...
      157    (Entry from GetRegisteredOptions)
      157 ---------------------- Joystick Device Scan -----------------------
      157 Checking: \\?\hid#vid_0738&pid_1302#6&cf64c04&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
      157    Usage=4, UsagePage=1, =Game Controller
      172 Product= Mad Catz F.L.Y.5 Stick
      172    Manufacturer= Mad Catz
      172    Vendor=0738, Product=1302 (Version 1.51)
      172    GUIDs returned for product: VID_0738&PID_1302:
      172       GUID= {07C4D920-913A-11E5-8006-444553540000}
      172       Details: Btns=14, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R255,U255,V0,X1023,Y1023,Z255
      172 Checking: \\?\hid#ene0110#6&39a4dcf9&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
      172    Usage=12, UsagePage=1, =Flight Mode Switch
      172 -------------------------------------------------------------------
      172 ****** Registry scanning: VID=0738, PID=1302 ******
      172 Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_0738&PID_1302\Calibration\0"
      172    ... and a "GUID" value
      172    GUID= {07C4D920-913A-11E5-8006-444553540000}
      172    1st registry entry has Joystick ID=1
      172    Attempting to acquire this device for checking ...
      172    Acquired device, GetDeviceState to check values
      172    ... Okay so far
      172    Finding name in "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM\VID_0738&PID_1302"
      172    Joy Name = "Mad Catz F.L.Y.5 Stick"
      172 -------------------------------------------------------------------
      172 UserDevices: 1.GUID={07C4D920-913A-11E5-8006-444553540000}
      172    Acquired device, GetDeviceState to check values
      172 Device acquired for use :
      172    Joystick ID = 1 (Registry okay)
      172    1=Mad Catz F.L.Y.5 Stick
      172    1.GUID={07C4D920-913A-11E5-8006-444553540000}
      172 -------------------------------------------------------------------
      172 ---------- Making INI JoyNames Section ----------
      172     wJoyIDsUsed=0002
      188    Joy#1: Name = Mad Catz F.L.Y.5 Stick
      188    Joy#1: GUID = {07C4D920-913A-11E5-8006-444553540000}
      188 -------------------------------------------------
      188   Checking and assigning Joy Letters as needed
      188 #### Completed Dlrectinput Axis Scanning
      203 LogOptions=00000000 02000011
      203 SimConnect_Open succeeded: waiting to check version okay
      203 Opened separate AI Traffic client okay
     3891 Running in "Lockheed Martin® Prepar3D® v4", Version: 4.0.23.21468 (SimConnect: 4.0.0.0)
     3891 Initialising SimConnect data requests now
     3891 FSUIPC Menu entry added
     3891 ... Using Prepar3D with Academic License
     3907 Ready Flags: Ready-To-Fly=N, In Menu=Y, In Dlg=Y
     3907 C:\Users\Andi\AppData\Local\Lockheed Martin\Prepar3D v4\Prepar3D_Default.fxml
     3907 D:\Prepar3D v4\SimObjects\Airplanes\IRIS Raptor Driver\Raptor.air

Link to comment
Share on other sites

3 hours ago, ITholic said:

No CTD on loading Prepar3D v4 without the joystick now using 5101d :

Good. So ... fixed? Looks lke it.

Seems that device FSUIPC was picking up didn't respond well to queries made of it to see if it was suitable for button/axis assignment.

Pete

 

Link to comment
Share on other sites

Seems so. Well done Pete :-D

Btw is the old registration of WideFS valid for FSUIPC 5 ?

I will start to install Prepar3D v4 today in my full size sim. Sadly Prosim 737 users will have to wait till August / September to get v4 compatibility. ProsimA320 seems to be 99% compatible. As I am a long time FSUIPC user I will stay with your tool even if they go to use more of simconnect. I have a lot of tools that depend on FSUIPC.

So time to say thanks for your great work! I really appreciate the possibilities I get through FSUIPC :-D 

Allways three green and blue skies and best regards

Andi

 

Link to comment
Share on other sites

6 minutes ago, ITholic said:

Btw is the old registration of WideFS valid for FSUIPC 5 ?

Yes. If you are using a different name, though, you will need to do it by editing the KEY file.

8 minutes ago, ITholic said:

Sadly Prosim 737 users will have to wait till August / September to get v4 compatibility

Why is that? That will stop me using P3D4 then. Surely they don't need to do any changes?

Pete

 

 

Link to comment
Share on other sites

As they posted on their Facebook page:
 

Quote

Finally we’re allowed to tell you about this exciting development! As you may know in a week from now Lockheed Martin will release Prepar3D version 4. ProSimA320 is 99% compatible already today. For ProSim737 we have a bit more work to do, expected to be done in August or September, no additional charge.

Prosim-AR Facebook Page

They want to change it to simconnect - that's what i heared.

I will try it the next days and then see what happens. On my Notebook (Prosim 737 locally) i had stutters on all displays. MCP seems not to work at all. Let's see how SIOC and FSUIPC5 work together.

Best regards

Andi

Link to comment
Share on other sites

11 hours ago, ITholic said:

They want to change it to simconnect - that's what i heared.

That's an intention, for future independence, but the current methods should work completely with FSUIPC. However:

11 hours ago, ITholic said:

MCP seems not to work at all. Let's see how SIOC and FSUIPC5 work together.

You will probably need 5.101g, an interim update I will hopefully be releasing this afternoon. It should fix problems with some types of "offset" writing -- ones which could especially affect the PFCMCP.

Please see the thread about LINDA for more details on this. It's been a complex process to resolve.

Pete

 

Link to comment
Share on other sites

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.