ghrasko

It seems, only 0x4 (esc pause) is signalled on 0x0264 offset. The value is 0 if running or if in active pause. It is 4 if it is in esc pause. Presently i can't detect the active pause state on this segment.

It seems, only 0x4 (esc pause) is signalled on 0x0264 offset. The value is 0 if running or if in active pause. It is 4 if it is in esc pause. Presently i can't detect the active pause state on this segment. Gábor

In fact I have not too muvh time to play with FS, so I had to re-configure quite a lot of staff to be able to answer you. Still yesterday I more refined the installation: [user] Log=Errors+ Run1=D:\Progs\IVAO\TS\TeamSpeak.exe Run2=D:\Progs\IVAO\IvAp\usrhost.exe UseSendInput=Yes KeySend1=123,16 KeySend2=123,24 Close1=Yes Close2=Yes I.e. I moved the ivapnetint.exe from the 2nd PC and run it on the 1st (FS) PC. With the previous setup messages did not appear in the FS (only in IvAp) and also I had to manually connect the mutliplayer session to the 2nd PC. With the setup here it is all OK and automatic. Of course you have to run the IvApconfig utility on both PCs to set up IvAp correctly: 1st (FS) PC: - IP of flight Simulator PC: 127.0.0.1 - IP of Network Interface PC: 127.0.0.1 - IP of User Interface PC: 2nd PC: - IP of flight Simulator PC: - IP of Network Interface PC: - IP of User Interface PC: 127.0.0.1

There were errors in my examples. The keys should be as follows: KeySend1=123,16 ;press F12 KeySend2=123,24 ;release F12 123,8 means the F12 key itself. +8 means press and +16 means release So my working copy is as follows: [user] Log=Errors+ Run1=D:\Progs\IVAO\TS\TeamSpeak.exe Run2=D:\Progs\IVAO\IvAp\ivapnetint.exe Run3=D:\Progs\IVAO\IvAp\usrhost.exe UseSendInput=Yes KeySend1=123,16 KeySend2=123,24 Close1=Yes Close2=Yes Close3=Yes

Well, I downloaded Spy++ from http://www.windows-spy.com/download/ and tested the solution with the following settings: KeySend1=123,8,TMainForm KeySend2=123,16,TMainForm ... TMainForm being the main window class name of TeamSpeak based on Spy++. I also tried... KeySend1=123,8,TMainForm,"TeamSpeak 2" KeySend2=123,16,TMainForm,"TeamSpeak 2" It still does not work for me. I just repeat, that KeySend1=123,8 KeySend2=123,16 works fine. TeamSpeak version: 2.2.0.32.60 Gabor

I am using a two PC setup, possibly the same way you are using. Some IVAP components are running on the 2nd PC with WideFS Client and TeamSpeak. On the 1st (FS) PC I run FS9, WideServer and FSUIPC. I configure FSUIPC/Buttons+Switches as: Joy# 0 Btn# 1 Select for FS control: check COntrol sent when button pressed: KEYSEND 1-255 (WideFS) Parameter: 1 COntrol sent when button released: KEYSEND 1-255 (WideFS) Parameter: 2 I use the following settings in wideclient.ini: [user] Log=Errors+ Run1=D:\Progs\IVAO\TS\TeamSpeak.exe UseSendInput=Yes KeySend1=123,8 KeySend2=123,16 When WideClient starts, it also starts TeamSpeak. You might also "auto" start here IvAp Network Interface and IvAp User Interface with Run2 and Run3. KeySend1 generates F12 keydown command and KeySend2 generates F12 keyup command. It is sent to the Windows main queue, thus all applications receives this. It controls TeamSpeak if PTT is set to F12. So it is going to TeamSpeak, not to IvAp. In fact it works fine without IvAp running. IvAp is needed here as if you tune frequency in your cockpit or if you select ATC on IvAp User Interface, then it has to be located on the same PC where TeamSpeak is located to be able to switch channel. But IvAp has nothing to do with WideClient here. The slight problem is that F12 is received by all running programs on the 2nd PC. It might or might not be a problem - depending on how the programs react on F12 (or the key you define). There is a second version of KeySned that direct the keystroke to the application that was started by the appropriate Runx command: KeySend1=123,8,Run1 KeySend2=123,16,Run1 This is unfortunatelly does not work for me. With this setup TeamSpeak is not receiving the keys at all (and not any other apps running on the 2nd PC - I used to open notepad and configure letter 'A' instead of F12 when doing testing). There is a more advanced form of KeySend, but i have never tried - though that might work: KeySend1=123,8,, WIndow name is only required in case there are multiple windows with the same class name - that is most probably not the case with TeamSpeak. One needs a "Spy" program to determine the internal Window name of a given program if it is not documented. I am too lasy to set up one and determine it for TeamSpeak - but i am interested. You can find all this information in "WideFS Technical.pdf". Gabor

Oops, I somehow missed this. I will check. Thanks

Is there any variable providing the actual CoG or CoG%? I guess I can quite easily calculate it from the load and fuel parameters, but there might be an automatic way...? Can I change the load and fuel through FSUIPC as if I would change it from the Aircraft menu? I read somewhere that it is possible, but not realy working correctly as FS is not making some necessary recalculations. Gabor

Gary, I have the same problem. I also believed that it was wideFS and today I made several tests. I removed all nonstandard dlls from the modules directory and the problem still remained. I switched off all unneccesary Windows services - still remained. I have Windows XP SP2 and I run two monitors (1 LCD, 1 CRT) from a single VGA card (not too strong card, ATI RADEON 9600 AGP 128Mb DDR). I am generally running undocked panels on the second screen. I closed, still no relief. Finally I went to Diplay Properties/Settings and I removed the Windows desktop spreading to the second monitor (I do not know the exact checkbox title in English as I have Hungarian Windows). The problem dissapeared. I do not know what is causing the problem, it also occures if the second monitor is totally empty. Anyhow for me it was totally independent of WideFS. Gabor

Thanks, I mostly understand. Remaining problems are most probably due to the fact that I am not (yet) experienced in AdvDisplay. I will give a try. As documentation says AdvDisplay has a feature to capture text (ATIS etc.) otherwise appearing on the cockpit windows and displays it in its own window. It also copies the text to FSUIPC 0x3380 to make it available to other programs. But if I understand correctly text written into this offset will be displayed on FS cockpit window by FSUIPC itself. Isn' that a loop? How long a text inserted to 0x3380 by an application (AdvDisplay or other) stays there? Isn't that disappear as soon as FSUIPC processes the request? Does ShowText.exe polls this offset for not NULL or modified text very frequently? By the way is there any chance to get the info how AdvDisplay captures the messages, or is it part of your private know-how? Please don't misunderstand me, it is OK. But it seems to me a rather cumbersome solution to add AdvDisplay to my package for this simple feature. Gabor

Opps, sorry, possibly my English... FS is displaying various messages in that green line on top of the page. I am interested wether I can access those messages in any FS buffers through FSUIPC (or directly from my FS module). I know that I can ask FSUIPC to create (pass) such messages to FS. I had seen that IvAp also uses FSUIPC to display messages in the green line either indirectly or directly. If I ask for a METAR in IvAp client, or if I tune an ATC and receive the ATIS, these messages appear not only in the IvAp user interface, but in the green line as well. Now, putting together the two things: I would like to get the METAR and ATIS displayed by IvAp, but IvAp does not have its own FSUIPC offsets for this purpose. I can trigger IvAp via FSUIPC to display a METAR or an ATIS, but the requested info is not available for my application through FSUIPC, but it is displayed in the IvAp User Interface window and on the FS screen in the green line. I am speaking about the following IvAp offsets in FSUIPC: http://www.ivao.aero/softdev/IvAp/fsuipc_sdk.asp I write the airport ICAO code into FSUIPC 0x6650 and number 1 to FSUIPC 0x6641 and then IvAp will display the airport METAR in the IvAp screen AND in the FS green line. But unfortunately it does not make it available to my program. That is why I would like to capture the info what is scrolling in the green line. Hope it is better now... Gabor

Hi, Is it possible to read the text what is actually displayed in FS? As I understand offset 0x3380 is for defining such texts, but I would like to read a text of any resource. In particular I would like to read messages generated by IvAp client and displayed in FS also. Through FSUIPC I can even ask for METAR, ATIS etc and the requested info appears in IvAp and in FS. I would like to grab these texts. Gabor

I thought through - you are right. Gabor

Hi, I have a CH Flight Sim Yoke. It controls aileron and elevator, but not rudder. I use autorudder to make coordinated turns. I know I need a pedal, but I do not have it at the moment. I miss the rudder in two situations: 1/ Cross-wind landing OK, let's by a pedal if really bothers. 2/ Nose-wheel steering on ground While taxiing on ground I do not realy need the aileron, but I definitely need the rudder, especially as it controls the nose-wheel as well. In fact during take-off run it is rather dangerous that I keep the aircraft on the center line using the ailerons. When the nose gear is already in the air I could bank the aircraft dangerously. This is especially disturbing during cross-wind take-offs. It would be very good to have an option that allows me to automatically switch the yoke "turn" axis between aileron and rudder control based on the "On the ground" (all three gears) flag. Would it be possible to implement in later releases of FSUIPC as a switch box selection? On the other hand is it possible to program it using the FS SDK (I know it is not a question to here)? Gabor

It is cleared now, as I read the WideFS doc... In FSUIPC "Buttons" tab I defined Joy# = 0, Btn# = 1. "Select for FS control" is checked. "Control sent when button pressed" = Keysend 1 "Control sent when button released" = Keysend 2 On the client PC's WideClient.ini: [uSER] UseSendInput=Yes KeySend1=123,16 ; Press F12 KeySend2=123,24 ; Release F12 TeamSpek PTT button is defined as F12. Gabor

Hi, It is not clear for me. In FSUIPC "Buttons" tab I defined Joy# = 0, Btn# = 1. Select keypress is checked and I defined character '0' (zero) to be generated. I set '0' as PTT button in TeamSpeak on my second computer where WideFS Client is running (and connected). This is not working. The same setup worked on a single PC. I think it is not as simple as I believe. FSUIPC-WideFS is working fine with some other apps. IvAp is configured as multiPC the User Interface running on the 2nd PC with the TeamSpeak. IvAp is working correctly, changing TeamSpeak channels. But this is not related ti WideFS I guess. Gabor