General Category > General Discussion

P3D v1.4

<< < (3/4) > >>

Kosta:

--- Quote from: virtuali on August 28, 2012, 02:41:20 pm ---I'm sorry, but we already did the RIGHT thing, which is supporting P3D NATIVELY. We don't have any plans to do additional work, just to support a tool that shouldn't be needed in the first place, because they right thing for other developers to do, would be doing the additional work we ALREADY made, to adapt their installers to run in P3D proper.

--- End quote ---

Man, don't get angry that fast, we are just talking  ;)

Anyway, I am completely with you. All should just make installers for P3D and that would be that. I respect what you guys at FSDT did, making it all fully compatible.
Being what I am at AVSIM, I take a bit of burden on myself at looking at this stuff for our users there, as I know these questions will pop up sooner or later.

All is good Umberto, thank you for the hard work behind this!

virtuali:
After reading a bit on the support forum for the P3D migration tool, I think I understood what legacy mode does and yes, it shouldn't be used with our products.

One thing it does, it makes a copy of the prepar3d.exe to fsx.exe, and patches its version information, as it were FSX. So, an old program that checks for the existing FSX.EXE process, will be able to find it, complete with the version its expects to find.

However, this will entirely screw up our products because, we decide from the version information of whatever executable launched the Addon Manager, which version of FSX or P3D is running under and, based on that information, we set several offset in memory that we need to access.

This means, the information must be correct: if I'm getting an FSX version number from the renamed Prepar3d.EXE that launched the Addon Manager, I assuming I'm running under FSX (but I'm not), so I'll look into memory addresses that are valid for FSX, but will not work in P3D in the best case, and will make the program crash in the worse case.

The reason for needing direct in-memory access, is because there are things we can't get in any other way from the official Simconnect API like, for example, the actual coordinates of the eyepoint position, which are needed to enable Surround sound in GSX, but there are several others.

virtuali:

--- Quote from: Kosta on August 28, 2012, 02:51:14 pm ---Man, don't get angry that fast, we are just talking  ;)
--- End quote ---

I can't see any trace of angriness in my reply...I was merely illustrating the situation.

Kosta:
OK, so basically the problem lies in the fact that p3d mode of addon manager looks into different memory locations than it does with original fsx.exe, if I understood that correctly and that makes it impossible to run with the legacy mode. A 100% no-go.

I already thought this legacy mode is a bit of a drag, because you are going backwards instead of forward.

Well Umberto, thank you and look for a big comparison post soon in p3d forum, which will also contain some fsdt shots (although no comparisons for those as I didn't make them back in the fsx and fsx is already byebye).

Nitr0x21:
Hi Kosta

I had the same Problem with EFB. furtunatly this was the only addon that i had who needs legacy mode. Just in case you aren't aware of
there is a workaround until EFB 2 comes out: Just rename an executable (some kind of freeware Notepad as example) to fsx.exe and check
if it appears as fsx.exe in the Task manager. Then you can run EFB and have Prepare3d running in native mode.
Works fine for me, maybee that's an option ? In my mind it's clearly avilasoft fault who should release an P3d Version.

Navigation

[0] Message Index

[#] Next page

[*] Previous page