Pete has pulled an early Christmas Plum out of the air and gotten FSUIPC working for FSX Steam Edition!

 

version 4.938 http://forum.simflight.com/topic/66139-updated-modules/

And the Lord said, "Let there be Autosave and Command Mapping"

Thanks for the HU, Bill!

Pete has pulled an early Christmas Plum out of the air and gotten FSUIPC working for FSX Steam Edition!

 

version 3.999z8 http://forum.simflight.com/topic/66139-updated-modules/

 

Its not 3.999z8. In the compatibility thread he said 4.938

 

Install complete FSUIPC version 4.938 Install FSUIPC4938 for FSX, FSX-SE and Prepar3D versions 1.4 and 2.0-2.4

-- Deletes orphaned profile entries from INI

-- Keeps axis assignments for new profiles if so requested

-- Fixes error in Lua mouse.wheel function.

-- Provides OOMcheck=Quiet option (no audible VAS warning)

-- Single byte offset 3124 gives P3D EXE version number, 10-14, 20-24.

-- Installs and operates with the FSX Steam Edition

And the Lord said, "Let there be Autosave and Command Mapping"

 

Amen!

Now I can quit cursing and pulling my hair out!

Its not 3.999z8. In the compatibility thread he said 4.938

Corrected. Thanks for the eagle-eye report. I copy/pasted the wrong version number in my eagerness...

 

...that sounds so much better than blaming my ever increasing senility!

Corrected. Thanks for the eagle-eye report. I copy/pasted the wrong version number in my eagerness...

 

...that sounds so much better than blaming my ever increasing senility!

Far from an eagle eye... I installed that first version and was banging my keyboard trying to figure out why it didn't work. Then I went back and realized I blindly followed the wrong link. Lol!

Oh, now that makes me feel so much better... :unsure:

Pete is so now - awesome!

Pete:

I've seen you mention somewhere that the g3d.dll fix isn't included in the 'emergency' version of FSUIPC.

With 4.938a, I got two CTDs with FSXSE clearly attributed to g3d.dll in Windows' Event Log.

I've seen you mention somewhere that the g3d.dll fix isn't included in the 'emergency' version of FSUIPC.

With 4.938a, I got two CTDs with FSXSE clearly attributed to g3d.dll in Windows' Event Log.

 

FSUIPC4 only ever patched around ONE very specific G3D crash, out of the many different ones which folks can get. The code that was patched in FSX is not the same in FSX-SE -- nothing like it, in fact. So I can't apply the same patch, and I can't patch anything without knowing what I'm doing.

 

Whether or not your two G3D crashes are similar to or related to the one FSUIPC4 patched cannot be determined from a report which says simply "I got two crashes". You need to post the details -- not here, but in my Support Forum. I don't mind having a look to see if they are at all similar and whether patchable, but I may not get to it anyway till I get back in January.

 

Pete

FSUIPC4 only ever patched around ONE very specific G3D crash, out of the many different ones which folks can get. The code that was patched in FSX is not the same in FSX-SE -- nothing like it, in fact. So I can't apply the same patch, and I can't patch anything without knowing what I'm doing.

 

I see, thanks.

 

Well, the crashes were rather random and I couldn't reproduce them with the same steps, so I'm not sure if there is even a systematic issue. The exception error code is "0xc0000005" which points to an access violation.

If this goes in the same direction as the old bug, I'll post the EventViewer logs in your forum.

 

 

- E:

 

There were actually several errors related to this, but only two of them listed g3d.dll as the faulting module.

No problems experienced with fsuipc in FSX SE except my user registration wasn't recognised. I copied the relevant files from my registered fsuipc in FSX to solve.

Well-I've been trying to find the latest version of FSUIPC. I have located it, but the sites that have it are selling it, not making it available for free. I was  under the impression that these were freeware. This is just a hobby with me...can't afford any large outlays.

NikolaiB