Jump to content
The simFlight Network Forums

Recommended Posts

Posted

I'm developping a FS pause and screenshots utility.

For screenshots functions, I'm looking for :

- the name of fs2000 and fs2002 process (fs9.exe for fs2004)

- the language.dll file of english, spanish and deutch versions of FS

Thank you for your help.

Posted

I'm looking for :

- the name of fs2000 and fs2002 process (fs9.exe for fs2004)

- the language.dll file of english, spanish and deutch versions of FS

If you mean programmatically, you can find the FS process by finding the top level window with Class Name "FS98MAIN". So far, since FS98, all versions of FS use this as their main top level Class.

The only way I can think of for identifying the labugage is to look at the DLLs in the main FS folder. Older versions used different names, like "English.fll", but now the different languages are obtained by different Language.dll's as you have said.

Regards,

Pete

Posted

Thank you so much Pete.

Finding the fs windows classname is more elegant than the process name.

I ask for language.dll because I need to know the localize name of views

(cockpit view,spot view...)

I have a problem with FSUIPC.

I use the VB.NET or C# FSUIPC class and I make a read every three seconds.

For some data ( wind speed and direction, fuel), sometimes the result is false ( a big number generally) then all the next reading are false too for a short period (10 to 40 seconds).

After this laps of time, readings are correct...

for a certain time ??

Posted

I ask for language.dll because I need to know the localize name of views

(cockpit view,spot view...)

The language DLLs are simply resources. You can read the strings using the Windows LoadString API with the appropriate module handle and string ID. You can use something like ResHacker (a freeware program) to obtain the string IDs you need.

For some data ( wind speed and direction, fuel), sometimes the result is false ( a big number generally) then all the next reading are false too for a short period (10 to 40 seconds).

After this laps of time, readings are correct...

for a certain time ??

Check what you are reading against a well-known working program such as FSInterrogate, or simply use the real-time monitoring provided in FSUIPC (Logging options, right-hand side). You evidently have a bug which you will need to fix. I assume VB.NET and C# come with Debuggers just like the MSVC and C++ compilers?

Regards,

Pete

Posted

Sure, Pete.

It's for that reason that I ask localized language.dll to the community of this forum.

For my problem with fsuipc, perhaps I can send you my code ?

It's a random problem so not easy to fix and describe.

Posted

For my problem with fsuipc, perhaps I can send you my code ?

It's a random problem so not easy to fix and describe.

Sorry, neither VB.NET nor C# are any use to me. I would not know what to do with them.

Don't you have a debugger with the compilers so you can find your errors? How do you manage else? It sounds like you are corrupting your own data areas. Trace it through, work out where it is going wrong.

I provide as much in the way of tools as you should need to verify the FSUIPC part of this. If FSUIPC logs the values correctly or displays them on screen (using the monitor) correctly, and if FSInterrogate shows them correctly, then they are certainly correct --- and will give you something to compare with.

I am very sorry, but I simply cannot undertake to develop and debug other folks programs as well as my own, and most certainly not in languages with which I am not familiar.

Regards,

Pete

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • 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.