AirFlo737

OK, thank you very much for this enlightening dialog :-) I will solve my problem then with multiple writing of FS controls and a single Process call. I will also dig deeper into scripting and Lua, maybe this would simplify my task. So far, the machine is running pretty well with FS2004 and satisfactorily with FSX. We are still playing with SLI settings and other tweaks, but your hint towards the bus problem will definitely be a point of research. Thank you so much, as always I am very pleased with your support :-) Greetings from Bremen, Florian

Thank you so much for your quick reply! That is a great hint! The Controls NEXT_VIEW=65827 and PREV_VIEW=65828 do the job. If I rely on the main windows (view 0) being focused at start, then I can cycle through them and set their view mode, all with FSUIPC :-) Now, another question is: Can I pass multiple FS controls within a single FSUIPC_Process? Like: Pseudo-Code: Write(VIEW_MODE=0) (for view 0) Write(NEXT_VIEW) Write(VIEW_MODE=1) (for view 1) Write(NEXT_VIEW) Write(VIEW_MODE=2) (for view 2) Write(NEXT_VIEW) Process Or do I have to do separate Process-Calls? I also heard of FSUIPC's scripting capability, but I didn't use it so far. Would a macro or Lua script do the job? I have seen that there is an option to call such a script via FSUIPC... I am most of the time using FS2004, but I am also using FSX sometimes. I am striving compatibility between those two. So FSX-only facilities are not really an option. Would be an idea, but as I already have three NVidia GTX 260 cards in my machine I would rather use all of them. I don't know where the FOV limits are, but I am planning to cover 160°.

Hi everyone, I was able to change the view direction of the active view window via the offset 3126 successfully. But when I use multiple view windows, only the active window gets changed (the one with a white frame). Is it possible to select a window via FSUIPC, and change that view direction? Or can I specify WHICH window's view direction should be set? The background is that I am using a 3 beamer setup and would like to be able to switch the eye reference point at runtime. I configured the different view_*_eye and view_*_dir (e.g. *="forward") to create a setup with a centered ERP, one with an ERP for the left seat, and one for the right seat. So all in all 9 customized views (3 windows for each ERP setup). Is this possible?

Did you notice that most posts in this forum are English? Maybe you want to translate your text, so that more people can potentially help you... Greetings Florian

What programming language are you using? I managed to write a module for FS9 in Delphi. Greetings Florian

Well, what would you expect? Looks like 123°01'47" W to me. What Longitude does the Flight Simulator give you? Greetings Florian

Thanks for your reply, Pete. Unfortunately I cannot use these offsets since I'm using FS2004 (should have told you in the first place). So I guess I have to stick with the idea of looking up the position in the AIRAC database, unless anyone has a better idea? Greetings Florian

Hey Pete, is there a way to read the tuned NDB station's latitude and longitude (and maybe elevation) like with the VOR stations? I did not find such an offset in the list. I know that one way would be using the AIRAC database with all the navaids and search for the NDB station's identity and name, but maybe there is an easier way...? Thank you for your support Florian

Thank you very much, Pete. I found several files at AVSIM, both for FS9 and FSX. Maybe these documents and tools will provide me with the information I was looking for... Greetings Florian

Hey Pete, is there any chance you would give me the source code of your MakeRwys tool, or point me to where I can find more info about the format of the scenery files and how to decode them? I am especially interested in getting terrain elevation for a GPWS and a map presentation that I am currently working on for university. Greetings Florian

Hey Pete, thanks for your reply, there is a zip file called "Library for FS Internal Users" in the SDK, which includes a Delphi Unit for the internal interface to FSUIPC (if you coded a module for FS). There is a readme file that you wrote in 2006 ("Important Read Me"), but it does not tell how to use the unit. Maybe that would be a nice place for the info. Greetings Florian

Why did I even write this? Did you even read this? Well, I think you might sometimes feel the same, Pete. By the way, is there maybe some space in the manual for the SDK to include the above checklist for the Delphi version of the interface? It would make a transition from external to internal usage easier. Greetings Florian

Did that solve your problem?

Maybe I can help you, I have managed to create a DLL using Delphi... Make sure you have done the following things: - create a buffer variable e.g. as an array [0..65534] of byte (let's call it fsuipc_buffer for now), and make sure that it is globally accessible for all following code - use fpcinternal instead of fpcuser - use open2 instead of open. as additional parameters, pass on info about your buffer, e.g. FSUIPC_Open2(SIM_FS2K4, dwResult, @fsuipc_buffer[0], sizeof(fsuipc_buffer)); the @ and the [0] are important, as this will result in a pointer to the first element of the array All other things should be the same. It sounds to me that maybe you just forgot to make the variable accessible globally. Keep me posted, maybe I can help you if this doesn't work. And by the way, since some time, you don't need to have a registered version of FSUIPC if you only use the data I/O functions. Greetings Florian

Thank you very much Pete, that solved my problem! I cannot see any performance issues. It would be great if you could leave it like this in the next releases of FSUIPC (of course given that nobody else complains). Greetings from Goodyear, AZ Flo