Friction access lost with 4.929

[abax2000]

I just installed today 4.929 and then 4.929c.

In FSUIPC4.log, gets logged

 

                   2652 ### Failed to obtain SIM1 Frictions access: no frictions facilities available!

 

Haven't touched anything else.

What this can be?

[Pete Dowson]

I just installed today 4.929 and then 4.929c.

In FSUIPC4.log, gets logged

 

                   2652 ### Failed to obtain SIM1 Frictions access: no frictions facilities available!

 

Haven't touched anything else.

What this can be?

 

What flight simulator are you using? What version & update? What was your previous version of FSUIPC? 

 

The change in 4.929 is that it checks that the frictions data is default before hooking to it. If you are using an already patched version of SIM1.DLL (which some folks are), then, for safety, FSUIPC will not allow further changes.

 

The previous versions also did a similar check -- the main change is that it now logs a failure.

 

Pete

[abax2000]

FSX sp2.

Previous fsuipc version was 4.928.

As far as I remember I dont use a hacked sim1.

I use the relevant lua plugin.

I will check again and report back.

[Pete Dowson]

As far as I remember I dont use a hacked sim1.

 

Well, as far as I know that's the only cause of the log entry. In 4.928 FSUIPC would still not have patched the entries 9even with Lua) but it simply didn't log it -- an omission on my part.

 

If you think your SIM1.DLL is correct please do send it to me for checking (ZIP it and send it to petedowson@btconnect.com). I'm using Acceleration so mine will be different in any case.

 

Pete

[abax2000]

Pete,
I think the sim1.dll in my system is the original one. I have forwarded by email as requested.

Thanks for helping out.

[Pete Dowson]

I think the sim1.dll in my system is the original one. I have forwarded by email as requested.

 

 

That SIM1.DLL is indeed the same one I have for SP2. So there's something else odd somewhere. Can you please paste the whole of the FSUIPC log, not just the one line, please.

 

Pete

[abax2000]

I could not paste for some reason, so I attach it in a txt file.

 

 

 

Pete_FSUIPC4log.txt

[Pete Dowson]

I could not paste for some reason, so I attach it in a txt file.

 

I think you must be using a newish version of Windows Explorer. There's some option you need to change to allow pasting.

 

Most folks find they can't attach files. Odd how things differ.

 

Anyway, I can't see anything wrong which could cause the frictions access to fail. It is most odd -- and I can't reproduce this here. 

 

I'm adding some extra logging to tell me what it is stopping this. Later today I'll provide a link to an interim update for you to try and show me the log again.

 

Pete

[abax2000]

okee dokee Pete.

[Pete Dowson]

Please download and install FSUIPC4929g.zip. There will be some extra lines in the log telling me why it can't provide the frictions access.

 

Pete

[abax2000]

Here is the new log file.

 

I just loaded a flight and then closed the sim.

Note (unrelated to the issue discussed):

The log file is full of records related to a lua plugin, which should not be there since the aircraft did not take off.

G_Pete_FSUIPC4.txt

[Pete Dowson]

Here is the new log file.

 

Hmm. I'm now really puzzled. FSUIPC is looking in the location in SIM1 applicable to the Acceleration version. Yet the version number returned for FSX by Simconnect is correct for SP":

 

    11060 Running in "Microsoft Flight Simulator X", Version: 10.0.61472.0 (SimConnect: 10.0.61259.0)

 

 

So I'm a bit concerned. The only way FSUIPC can use the Acceleration values is if it sees the version number of FSX.EXE reading 61637. Can you look at the FSUIPC INstall Log for me please, find the section like this:

 

INSTALLATION FOR FSX:

SetupPath="E:\FSX"

Checking version of the FSX EXE:

... Version 10.0.61637.0  (Need at least 10.0.60905.0)

 

That's my Acceleration install, of course. Yours should show 61472.

 

Note (unrelated to the issue discussed):

The log file is full of records related to a lua plugin, which should not be there since the aircraft did not take off.

 

Sorry, is this something for me? Why would an aircraft not taking off affect what a Lua plug-in does?

 

Pete

[abax2000]

From FSUIPC4Install.log:

 

INSTALLATION FOR FSX:

SetupPath="C:\Program Files\Microsoft Games\Microsoft Flight Simulator X\"

Checking version of the FSX.EXE:

...Version 10.0.61637.0 (Need at least 10.0.60905.0)

 

I've looked my FSX.exe properties and it is:

Product version: 10.0.61637.0 (FSX-Xpack.20070926-1421)

Size: 2.61 MB

Date modified: 9/26/2007 16:09

 

If this is Acceleration, this is totally unexplicable. I have the Deluxe version installed, updated to SP2 via the downloadable updates. Never installed Acceleration.

Most of the other files in install directory have properties with "Product version; 10.0.61472.0 (fsx-sp2.20071210-2023).

 

Note (regarding previous note)

I just mentioned it, because normally there are no such records in FSUIPC4.log, when I just load a flight and then close (no take off).

So, this was a "question" if something was ubnormally triggered by the new FSUIPC.dll.

But, is probably better to leave this aside for the moment, since it seems that we have a major mystery in our hands, regarding the core issue here.

[abax2000]

I remembered that I had noticed way back this issue with fsx.exe version number in my installation.

Never had any problems, but I posted a question in fsdeveloper (http://www.fsdeveloper.com/forum/threads/fsx-version.84549/) from which I did not receive any helpful info.

[Pete Dowson]

If this is Acceleration, this is totally unexplicable. I have the Deluxe version installed, updated to SP2 via the downloadable updates. Never installed Acceleration.

Most of the other files in install directory have properties with "Product version; 10.0.61472.0 (fsx-sp2.20071210-2023).

 

I don't really know what edition was what, but certainly you have the Acceleration version of FSX.EXE installed. I'm surprised there aren't other problems. Try renaming the FSX.EXE and re-installing the SP2 update -- it should put the correct, matching, EXE in.

 

Note (regarding previous note)

I just mentioned it, because normally there are no such records in FSUIPC4.log, when I just load a flight and then close (no take off).

So, this was a "question" if something was ubnormally triggered by the new FSUIPC.dll.

 

Well, nothing has changed on the Lua side of things. But I can't really help without knowing what this Lua is doing. I don't know what you mean by "abnormally triggered". FSUIPC is not an active component, but one that responds to requests.

 

Pete

[abax2000]

This is driving  me crazy. Acceleration is only available in cd, so there is no way to install it by accident with a download.

I cannot figure out what can be possibly wrong.

 

Even if I have installed Acc without realizing it ( :cry:), all the other files should have been version 61637, which they are not (they are all 61472) !!!

 

I suppose that reinstalling sp2, will overwrite a lot of critical files, that due to addons or mods, have been altered.

 

So, this leaves me with two questions:

1. Is there any way to extract the exe file from the sp2 update installer?
2. If I live with this error in FSUIPC, will the rest of its functions (and the friction lua plugin) operate as they should?

Thanks for helping out with this.

[Pete Dowson]

I suppose that reinstalling sp2, will overwrite a lot of critical files, that due to addons or mods, have been altered.

 

I don't think so. Yu could make a safe copy of your FSX.CFG file, and maybe your SCENERY.cFG file, but I can't really think what else could be disturbed at all.

 

Is there any way to extract the exe file from the sp2 update installer?

 

 

 

You should be able to. I don't recall the name of the unpacker at present. Google should find it -- aren't they just packed with slight variations on the filenames, like a final __ or something? Have a look on the disk. i don't think it's a monolithic ZIP, I think all the files are separate but compressed.

 

If I live with this error in FSUIPC, will the rest of its functions (and the friction lua plugin) operate as they should?

 

 

 

The frictions can't be patched because it can't locate the correct place in memory. I am not aware at present of any other difference which would affect you, but if you can't resolve it I'll check for you.

 

I would be more concerned about the inter-compatibility of that EXE with its DLLs. I would expect problems to arise because of incompatible functions, links, and so on, in both directions -- the EXE calling the DLLs and vice versa.  It is simply not a desirable situation at all. For sure, I know for recent experience with P3Dv2, even different Beta's for the same release can have different function entry points in DLLs from one week to the next.

 

Pete

 

[abax2000]

Thanks for putting up with this.

 

I just extracted (not installed) the sp2 installer. In there, there is ROOT_fsx.exe, which I suppose that if renamed can be put in its proper place.

 

The strange thing is that the exe in the sp2 installer has a timestamp "12/12/2007 20:30", while the Acc one is "9/26/2007 16:09", meaning that sp2 is later than Acc ?!?!?!?!

 

Anyhow, I will try tomorrow to rename the existing exe and place in the extracted from the sp2 installer (if you do not think that there is anything wrong with such a trial).

 

Of course I will report back.

[Pete Dowson]

The strange thing is that the exe in the sp2 installer has a timestamp "12/12/2007 20:30", while the Acc one is "9/26/2007 16:09", meaning that sp2 is later than Acc ?!?!?!?!

 

Yes, I think that is so. My memory is not too good these days, and it was over six years ago, but I think the Beta releases themselves, the ones I tested with, were in the order you'd expect, but the actual release to users was different. The payware Acceeration was probably available before the SP2 download became available. Probably a marketing decision.

 

My SP2 modules including the EXE are all dated 10/12/2007, two days earlier than your EXE. Not sure why. Probably mine was a slight pre-release for Beta testers.

 

Pete

[abax2000]

I copied the sp2 exe in the installation folder.

Fired up ok and closed.

The new thing I see in FSUIPC log is the lines regarding the G3D fix which I think that were not recorded in the past.

 

I'll try a sort flight and report back.

sp2_FSUIPC4.txt

[Pete Dowson]

The new thing I see in FSUIPC log is the lines regarding the G3D fix which I think that were not recorded in the past.

 

I'll try a sort flight and report back.

 

Looks okay now. I hadn't noticed the G3D patch being missed in the last one -- that's evidently another FSUIPC action not possible if it doesn't get the correct EXE. Sorry, I didn't go all the way through my code to see what else might be affected. I was really more concerned that there would be real conflicts between your EXE and the mismatched DLLs.

 

Pete

[abax2000]

I concluded normally a 1.5hr flight with no adverse findings.

 

I checked all the files in root directory one-by-one; all are 61472, except the exe (which was 61637, and now is swapped with the sp2).

I don't know of course what other files (besides the exe) are updated by Acceleration to a newer version (newer than sp2).

 

It still beats me how this exe version was found in my installation. It is there for quite some time now, without any visible or persistent problems !

And what is more strange, is that FSUIPC (at least at the latest version) would reveal such problem in other users also, but I see nobody else reporting anything, so I guess this case was one in a million !!!

 

Anyhow, it seems settled. 

 

flight_FSUIPC4log.txt

[Pete Dowson]

It still beats me how this exe version was found in my installation. It is there for quite some time now, without any visible or persistent problems 

...

Anyhow, it seems settled. 

 

Yes, very strange. Glad it's sorted.

 

Pete

[abax2000]

Pete, thanks again.

 

Could you tell me one or two dll's that get updated to 61637 by Acceleration, so I can do a final check?

[Pete Dowson]

Could you tell me one or two dll's that get updated to 61637 by Acceleration, so I can do a final check?

 

Sorry, that's not easy to tell without doing a binary comparison -- they all have different date stamps so I assume they've all been recompiled.  Ceretainly differences are known to FSUIPC, but sometimes it handles these differences by going through a sequence of tries -- i.e. try this address, try that, till a fit is obtained.

 

These are the differences which matter to FSUIPC4:

 

SIM1.DLL for wind smoothing hack and the frictions/braking tables

API.DLL for SimConnect text and menu diversion for WideFS

G3D.DLL for the most common G3D crash patch

ATC.DLL for the nearest airports list

 

Pete