Complex Number of Engines issue...

[StuartWhelan]

Hi Pete,

This is one me confused for a while, here is what I believe I am seeing. :)

I have an FSUIPC accredited flight sim DLL is using the internal method to access an unregisted FSUIPC.

If I start up FS with my A/C set to my 767, the number of engines offset (0xAEC) reads 2. Enabling IPC Read logging shows it being read as 2, everything is fine. I then stop the IPC Read Logging.

I then switch to a A/c with no engines, for example the default sailplane.

FSUIPC Log shows no problems, everthing appears to be working okay..

If you then enable IPC Reads, you get instantly get the 'One or more of the programs you are using are not accredited.' message.

The log contains (among other things):

Illegal read attempt: offset 0AEC, size 2

The internal program can no longer access any FSUIPC variables.

Changing A/C back to a powered A/c does not fix the problem...

External programs are not effected.

I have a log file for the session if you want to see it...

EDIT:

If you do not turn on IPC Read logging, you never get an error, but the internal DLL always reads 0's for the number of engines from the moment it tries to read 0xAEC on the sailplane, regardless of what plane you switch to afterwards.

[Pete Dowson]

I have an FSUIPC accredited flight sim DLL is using the internal method to access an unregisted FSUIPC.

Which one is that, please? I can see here if it has been given a Key. Does it register itself, or did you register it manually?

I have a log file for the session if you want to see it...

Please run that with both IPC reads and writes logged. Send me the LOG and also the KEY file, zipped please, to petedowson@btconnect.com. Perhaps if you include the DLL so I can reproduce it here, it will be quicker.

If you do not turn on IPC Read logging, you never get an error, but the internal DLL always reads 0's

That effectively means the same thing -- 0's are suppliied if it thinks the DLL is not accredited. The warning message normally only occurs at some stage at most once in an FS session in any case. I suppress it at other times to avoid multiple message boxes and/or filling the disk up with log entries because the unaccredited DLL keeps retrying.

Also, whether the DLL access is accepted without a Key is random -- the whole area is deliberately complex to dissuade piracy, you see. :wink:

Regards,

Pete

[StuartWhelan]

I have an FSUIPC accredited flight sim DLL is using the internal method to access an unregisted FSUIPC.

Which one is that, please? I can see here if it has been given a Key. Does it register itself, or did you register it manually?

Thanks Pete, email sent with DLL and answers to all but one of the above questions, which I forgot to answer:

The DLL is self registering by writing to 8001.

[Pete Dowson]

Thanks Pete, email sent with DLL and answers to all but one of the above questions, which I forgot to answer:

The DLL is self registering by writing to 8001.

Okay, I looked at the log. There's no terminating zero in what you write to 8001, so the comparison check being done by FSUIPC will depend on whatever other rubbish might be there before. when that is zero, it'll work, when not, it won't.

If you still have problems after correcting that, let me know, with the same sort of data please.

BTW for DLLs, FSUIPC automatically also makes an entry in the KEY file, so you should check that next time too. It does this because it renews the accreditation scan every time an aircraft is loaded -- GAUges of course load with aircraft. Since the same mechanism is used by Gauges and DLLs, but DLLs may write 8001 only once at the start, it has to remember the details (which it does in the KEY file, as it has to check that in any case), so it can check without the 8001 write recurring.

Regards,

Pete