Jump to content
The simFlight Network Forums

ShortAircraftNameOk=Yes Problem with 4.85


Recommended Posts

Hello,

I understand that Pete is away at the moment. However am I the only person that's finding that ShortAircraftNameOk=Yes isn't working with FSUIPC 4.85? Sadly I deleted the last version of the FSUIPC.DLL file as it was overwritten by 4.85, but I have an older version 4.80 and using the same ini file it's working as it should.

It's a shame Pete doesn't leave the last version before the latest available to download in case of a problem such as this. Although I'm sure I'm not missing too much on version 4.80.

Thanks,

Jack

Link to comment
Share on other sites

Hi,

Definitely the ShortAircraftNameOk=Yes is broken in 4.85. I can confirm, that's the same here, since I have upgraded. But It's not a shame, that Pete doesn't supply old names. This would lead to complete confusion. You should keep old versions in case something doesn't work for you as expected ;-)

But how I know Pete, this soon will be fixed. In The meanwhile you can add the complete profile name of the aircraft you are flying and that works.

Rgds

Reinhard

Link to comment
Share on other sites

Looking at other threads it seems as though there are also other issues with 4.85 then. Can anyone upload the dll for version 4.84 before Pete's return by way of a PM or something?

Stupidly, the day 4.85 came out I had deleted most of the other old versions that I had kept. Teaches me a lesson!

Many Thanks,

Jack

Edit: Someone's kindly provided me with the old (working) version that I wanted. Thanks.

Edited by JackRichardson
Link to comment
Share on other sites

Same thing with P3D ver 1.4 ...and FSUIPC 4.85.

If I load the sim P3D the e.g. throttles (profile) are not remembered .. so I select FSUIPC from the P3D menu, then go to calibration, then select (check profile specific) my previously saves profile (mooney in this case) , click ok

No I got my throttles back.

Note: I just checked FSX ..same problem(s) with FSUIPC 4.85 / profiles.

I went back to ver 4.80 and all ok with profiles loading FSX/P3D profiles.

Link to comment
Share on other sites

Yes profiles are busted at the moment, the easiest way to get it working again at the start of a new session is to open the FSUIPC GUI and select the buttons and switches tab or Axes tab and click on the "reload all buttons" err..... button, lol.

Looking at all this now, but meanwhile reloading or changing the flight or aircraft after FSX / P3D is ready to fly should fix it. Apologies for the mess -- it arose because of a re-ordering of initialisation events in order to overcome issues with SimConnect trust crashes. Seems I moved something in there I shouldn't have.

I'll fix it this weekend.

Regards

Pete

Link to comment
Share on other sites

Definitely the ShortAircraftNameOk=Yes is broken in 4.85

It isn't "ShortAircraftNameOk" which is broken -- tested here and it works fine. What is "broken" is the initial matching of the aircraft name when first loading, and that applies with or without ShortAircraftName. Changing the aircraft later works.

I'm fixing the initialisation problem now -- 4.851 later today.

Same thing with P3D ver 1.4 ...and FSUIPC 4.85.

P3D 1.4? Is there a version 1.4 now? And FSUIPC runs? It shouldn't!

Since John Nicol left P3D no one there contacts me any more and my license for 1.3 has expired. Not sure who the contact is now.

Regards

Pete

Link to comment
Share on other sites

Yes 1.4 works, I got a warning from FSUIPC saying that it didn't know about version 1.4 of P3D but it loaded ok once I accepted the warning. 1.4 was released on the 20th. I'm slowly but surely going to move across to P3D and once RealityXP get their arse in gear and get there GNS product working in P3D I'll probably not use FSX anymore.

Link to comment
Share on other sites

Yes 1.4 works, I got a warning from FSUIPC saying that it didn't know about version 1.4 of P3D but it loaded ok once I accepted the warning. 1.4 was released on the 20th.

Can you enble "Extras" logging in FSUIPC, please, then restart P3D 1.4 and show me the log file? Unless they've not changed much several functions in FSUIPC are unlikely to work including the G3D patch, Mouse Macros, wind smoothing, the timer protection for things like E+number, or pushback direction, and maybe even the list of assignable FS controls. All of these depend on the relative location of things in memory and need checking and possibly updating with each update.

What changes are there between 1.3 and 1.4? Are they listed on their site? I'll take a look when I get a chance.

Regards

Pete

Link to comment
Share on other sites

Can you enble "Extras" logging in FSUIPC, please, then restart P3D 1.4 and show me the log file? Unless they've not changed much several functions in FSUIPC are unlikely to work including the G3D patch, Mouse Macros, wind smoothing, the timer protection for things like E+number, or pushback direction, and maybe even the list of assignable FS controls. All of these depend on the relative location of things in memory and need checking and possibly updating with each update.

What changes are there between 1.3 and 1.4? Are they listed on their site? I'll take a look when I get a chance.

Regards

Pete

I don't think a lot has changed to be honest, they do mention a g3d fix though, the logs are below.

Install;

Installer for FSUIPC4.DLL version 4.85

Looking in registry for FSX install path:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\10.0
Parameter"SetupPath"
... >>> OK! FOUND FSX! <<< ...
Looking in registry for ESP install path:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft ESP\1.0
Parameter"SetupPath"
Not there, so looking in:
HKEY_CURRENT_USER\ESP
Parameter"AppPath"
... NOT found! ...
Looking in registry for Prepar3D install path:
HKEY_LOCAL_MACHINE\SOFTWARE\LockheedMartin\Prepar3D
Parameter"SetupPath"
... >>> OK! FOUND Prepar3D! <<< ...
===========================================================

INSTALLATION FOR FSX:
SetupPath="E:\Microsoft Games\Microsoft Flight Simulator X"
Checking version of FSX.EXE:
... Version 10.0.61637.0 (Need at least 10.0.60905.0)
Checking compatibility with installed SimConnect:
Found SimConnect build 60905 (Original)
Found SimConnect build 61242 (SP1 May07)
Found SimConnect build 61259 (Acc/SP2 Oct07)
Checking if there's already a version of FSUIPC4 installed in:
E:\Microsoft Games\Microsoft Flight Simulator X\Modules\FSUIPC4.DLL
... Version 4.850 found.
FSX Modules folder already exists.
Okay -- installed FSUIPC4 into "E:\Microsoft Games\Microsoft Flight Simulator X\Modules\FSUIPC4.DLL"
Looking for the current user's Application Data path:
... found as "C:\Users\Andy\AppData\Roaming"
Now finding \Microsoft\FSX\FSX.CFG for all users, including this one
Looking in "C:\Users\All Users\AppData\Roaming"
... No FSX.CFG there
Looking in "C:\Users\Andy\AppData\Roaming"
Found FSX.CFG in "C:\Users\Andy\AppData\Roaming\Microsoft\FSX\FSX.CFG"
Now checking DLL.XML ...
... There is a previous DLL.XML, checking for FSUIPC4 section.
... FSUIPC4 section already exists but will be replaced.
(for FSUIPC4, without Loader)
... FSUIPC4 section of DLL.XML written okay
Now checking for a SimConnect.XML file ...
... No SimConnect.XML file found. This is okay.
Looking in "C:\Users\Default\AppData\Roaming"
... No FSX.CFG there
Looking in "C:\Users\Default User\AppData\Roaming"
... No FSX.CFG there
Looking in "C:\Users\Public\AppData\Roaming"
... No FSX.CFG there
Looking in "C:\Users\UpdatusUser\AppData\Roaming"
... No FSX.CFG there
"Modules\FSUIPC Documents" folder already exists.
Now installing additional files into the "Modules\FSUIPC Documents" folder:
Installed "FSUIPC4 User Guide.pdf" okay
Installed "FSUIPC4 for Advanced Users.pdf" okay
Installed "FSUIPC4 History.pdf" okay
Installed "List of FSX controls.pdf" okay
Installed "GlobalSign Root.exe" okay
Installed "FSUIPC Lua Library.pdf" okay
Installed "FSUIPC Lua Plug-Ins.pdf" okay
Installed "Lua License.pdf" okay
Installed "Lua Plugins for VRInsight Devices.pdf" okay
Installed "LuaFileSystem.pdf" okay
Installed "Example LUA plugins.zip" okay
Installed "Offset Mapping for PMDG 737NGX.pdf" okay
FSUIPC4.DLL installed and signature checked out okay!
Deleted GlobalSign Root fix program ... no longer relevant
===========================================================

INSTALLATION FOR Prepar3D:
SetupPath="E:\Prepar3D\"
Checking version of Prepar3D.EXE:
... Version 1.4.4747.0 (Need at least 1.0.677.0)
!! WARNING !! This version of Prepar3D is later than any known by this FSUIPC4.
There may be problems. Please check for a later version of FSUIPC4!
Checking if there's already a version of FSUIPC4 installed in:
E:\Prepar3D\Modules\FSUIPC4.DLL
... Version 4.850 found.
Prepar3D Modules folder already exists.
Okay -- installed FSUIPC4 into "E:\Prepar3D\Modules\FSUIPC4.DLL"
Looking for the current user's Application Data path:
... found as "C:\Users\Andy\AppData\Roaming"
Now finding \Lockheed Martin\Prepar3D\Prepar3D.CFG for all users, including this one
Looking in "C:\Users\All Users\AppData\Roaming"
... No Prepar3D.CFG there
Looking in "C:\Users\Andy\AppData\Roaming"
Found Prepar3D.CFG in "C:\Users\Andy\AppData\Roaming\Lockheed Martin\Prepar3D\Prepar3D.CFG"
Now checking DLL.XML ...
... There is a previous DLL.XML, checking for FSUIPC4 section.
... FSUIPC4 section already exists but will be replaced.
(for FSUIPC4, without Loader)
... FSUIPC4 section of DLL.XML written okay
Now checking for a SimConnect.XML file ...
... No SimConnect.XML file found. This is okay.
Looking in "C:\Users\Default\AppData\Roaming"
... No Prepar3D.CFG there
Looking in "C:\Users\Default User\AppData\Roaming"
... No Prepar3D.CFG there
Looking in "C:\Users\Public\AppData\Roaming"
... No Prepar3D.CFG there
Looking in "C:\Users\UpdatusUser\AppData\Roaming"
... No Prepar3D.CFG there
"Modules\FSUIPC Documents" folder already exists.
Now installing the Prepar3D SimConnect interface for FSUIPC4 into the "Modules" folder:
Installed "SimConnectP3D.dll" okay
Now installing additional files into the "Modules\FSUIPC Documents" folder:
Installed "FSUIPC4 User Guide.pdf" okay
Installed "FSUIPC4 for Advanced Users.pdf" okay
Installed "FSUIPC4 History.pdf" okay
Installed "List of FSX controls.pdf" okay
Installed "GlobalSign Root.exe" okay
Installed "FSUIPC Lua Library.pdf" okay
Installed "FSUIPC Lua Plug-Ins.pdf" okay
Installed "Lua License.pdf" okay
Installed "Lua Plugins for VRInsight Devices.pdf" okay
Installed "LuaFileSystem.pdf" okay
Installed "Example LUA plugins.zip" okay
Installed "Offset Mapping for PMDG 737NGX.pdf" okay
FSUIPC4.DLL installed and signature checked out okay!
Deleted GlobalSign Root fix program ... no longer relevant
===========================================================

All installer tasks completed.
Registration for FSUIPC4 was successful! (result code 00)

*************** End of Install Log ***************[/CODE]

fsuipc.log

[CODE]
********* FSUIPC4, Version 4.85 by Pete Dowson *********
Running inside Prepar3D on Windows 7
Module base=54A20000
User Name="xxx"
User Addr="xxx"
FSUIPC4 Key is provided
WideFS7 Key is provided
624 System time = 24/08/2012 17:17:05
624 FLT UNC path = "\\ANDY-PC\Users\Andy\Documents\Prepar3D Files\"
640 Trying E:\Prepar3D\Modules\SimConnectP3D.dll
640 Found it: trying to connect
718 FS UNC path = "E:\Prepar3D\"
1373 LogOptions=00000000 00000011
1373 Wind smoothing fix is only partially installed
1373 SimConnect_Open succeeded: waiting to check version okay
1373 Trying to use SimConnect Prepar3D
1404 VRI port 1 "com4" opened
2371 Ready Flags: Ready-To-Fly=N, In Menu=N, In Dlg=N
2387 Running in "Lockheed Martin® Prepar3D®", Version: 1.4.4747.0 (SimConnect: 1.4.0.0)
2387 Initialising SimConnect data requests now
2387 FSUIPC Menu entry added
2403 Ready Flags: Ready-To-Fly=N, In Menu=Y, In Dlg=Y
2403 \\ANDY-PC\Users\Andy\Documents\Prepar3D Files\Previous Flight.flt
2403 C:\Users\Andy\Documents\Prepar3D Files\\VFR Barton to Woodford.PLN
2403 E:\Prepar3D\SimObjects\Airplanes\Carenado Skymaster 337\C337.AIR
2403 C:\Users\Andy\Documents\Prepar3D Files\\VFR Barton to Woodford.PLN
3120 VRI MCP2B ("MCP2 Boeing") detected on port com4
30717 Ready Flags: Ready-To-Fly=N, In Menu=N, In Dlg=N
31497 System time = 24/08/2012 17:17:36, Simulator time = 17:17:08 (16:17Z)
31746 Starting everything now ...
31762 LUA.0: beginning "E:\Prepar3D\Modules\ipcReady.lua"
31762 LUA.0: ended "E:\Prepar3D\Modules\ipcReady.lua"
31778 Ready Flags: Ready-To-Fly=Y, In Menu=N, In Dlg=N
31778 LUA.1:

31778 LUA.1: [INIT]LINDA:: Loading...
31871 LUA.1: LINDA:: Aircraft: C337 Skymaster RED
31871 LUA.1: LINDA:: Aircraft module detected: Carenado Skymaster 337
31902 LUA.0: LINDA:: AivlaSoft library loaded...
31918 LUA.0: LINDA:: FSX standard library loaded...
31918 LUA.0: LINDA:: IAO library loaded...
31918 LUA.0: LINDA:: RealityXP library loaded...
31934 LUA.0: LINDA:: A2A MAP library loaded...
32854 Advanced Weather Interface Enabled
36458 LUA.0: LINDA:: Loading a fallback joysticks config...
36473 LUA.0: LINDA:: Loading Carenado Skymaster 337 joysticks config...
36473 LUA.0: LINDA:: Module: Carenado Skymaster 337 Started...
36473 LUA.0: LINDA:: Ready to go, Captain!
36473 LUA.0: LINDA::
133085 Ready Flags: Ready-To-Fly=Y, In Menu=Y, In Dlg=Y
133085 Sim stopped: average frame rate for last 102 secs = 39.6 fps
135253 Ready Flags: Ready-To-Fly=Y, In Menu=N, In Dlg=N
138825 Ready Flags: Ready-To-Fly=Y, In Menu=Y, In Dlg=Y
193707 Ready Flags: Ready-To-Fly=Y, In Menu=N, In Dlg=N
199915 Ready Flags: Ready-To-Fly=Y, In Menu=Y, In Dlg=Y
212349 System time = 24/08/2012 17:20:37, Simulator time = 17:19:00 (16:19Z)
212349 *** FSUIPC log file being closed
Average frame rate for running time of 112 secs = 39.6 fps
Memory managed: 80 Allocs, 80 Freed
********* FSUIPC Log file closed ***********
[/CODE]

The FSControls list in the drop down menus appear to be fully populated too, although I can't be 100% certain of this.

No idea on Macros as I don't have anything installed that is amenable to them anyway, its a very fresh install, I only got P3D two days ago.

Wind smoothing does mention only a partial install.

g3d.dll isn't mentioned at all in the log as far as I can see.

Apart from the profiles bug I've not noticed anything else amiss so far.

Link to comment
Share on other sites

I don't think a lot has changed to be honest, they do mention a g3d fix though, the logs are below.

Thanks.

The FSControls list in the drop down menus appear to be fully populated too, although I can't be 100% certain of this.

If it contains most of the FS controls they'll all be there. The CONTROLS.DLL table start location doesn't change often in any case. In fact I think it was the same in P3D 1.0 through to 1.3.

No idea on Macros as I don't have anything installed that is amenable to them anyway, its a very fresh install, I only got P3D two days ago.

Wind smoothing does mention only a partial install.

g3d.dll isn't mentioned at all in the log as far as I can see.

The WEATHER.DLL will have changed, which explains the wind smoothing problem. The G3D bug they've fixed is probably the one I patched (I did supply them all the gen on that a while ago), so that explains that. Whether the other things work or not depend on other modules.

I'm downloading 1.4 now just to install and look at the changes. In order to test it I'll probably have to buy it (thought I don't use it -- my FSX installation is running so well and don't feel any need to move yet. Maybe I will with version 2). John Nicol was supplying 3 month licenses for each version update so I could test.

Regards

Pete

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
 Share

×
×
  • 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.