Dirk98

Pete, while we are at it, could you please add just a few more words about PM integration and MSFS (FSX in your case). I never understood completely how the whole PM setup worked in FS without a dedicated plane? What plane in FSX do you assign your PM cockpit to? Is there a good 737NG plane with a decent FDE that can actually fly well and carry the precise PM instruments cockpit (along with your good self)? :) I understand you don't see any parts of the visual model of the plane you use in FS? Thanks, Dirk. PS: honestly, I bought IYP following your single comment that I saw somewhere only once, and I'll keep it, will try to adapt it better to my flying.

That sounds encouraging, I'll update IYP (which happens quite frequent as Roberts seems very prolific) and will try again. I was not sure if anybody else at all used PTT over IYP listen on/off facility on the client pc. Now it makes sense to try again and compare. Well, that talkative interface still needs to launch/reload faster and talk even less (after set to mum) or better not talk at all... Thanks, Dirk.

Pete, I'm uptodate with FSUIPC/WideFS. I'm trying to make IYP recognize my voice commands on the Client, so I speak to the auido card on my Client PC so to say. IYP fails to switch to the listening mode when I press and hold the assigned button on my joystick to transmit the PTT from Server to Client via IYP Listen On/Off facility. Anyway it works if I make it through the KEYSEND facility. But not very well at all. I agree my main purpose in IYP is not to run checklists but to voice control ATC (RC4 or PFE) installed on the Client PC in the first place, so it's quite different from how you mainly use it. As to checklists I prefer FS2Crew's approach who've gone all-voice recently. Cheers, Dirk.

Thanks, Pete. IYP is on Wideclient, so if I remove these lines and switch directly to IYP for the PTT keystroke it does not arrive to IYP' PTT assignment UI, which I can see on my 2nd monitor when I check it there. Whereas otherwise it does. Anyway, I think I'm ditching IYP, it's too clumsy and not exactly for my way of flying. Much better solution in my case just to use VAC (a light but quite versatile voice recognition payware) on my main PC and voice-send the keystrokes to my main PC that can be read by RC4 or PFEmulator installed on the Wideclient anyway. IYP's checklists are not my cup of tea either, FS2Crew or even FDC is the way to go. In principle I find the whole arrangement quite cumbersome to send PTT from Wideserver and have IYP listen on the Wideclient then respond back with the keystrokes to Wideserver which doesn't work always good compared to the VAC method (almost faultless). Cheers, Dirk.

Hello Pete, I'm trying to send PTT on/off events from my joystick on Wideserver PC to IYP on the wideclient PC. The Microphone Switch Key Assignment in IYP is set to SCROLL (as IYP's window shows it as Scroll Lock). The Scroll Lock keystroke event actually arrives to IYP from my joystick, because I can set it by physically pushing the button. But unfortunately IYP doesn't switch to the listening mode, unless I press and hold Scroll Lock button on the Wideclient's keyboard with my finger instead of receiving it from Wideclient. I checked the keysend on/off events on TS and Ventrillo and they work just fine, but IYP does not. I have the following lines in Wideclient.ini: [user] UseSendInput=Yes KeySend1=145,16 KeySend2=145,24 Could you please look into this. Thanks, Dirk.

Paul, it's amazing how close my ideas and feelings about FSX simming are to yours. I'd subscribe to everything you mentioned based on my own experience. I appreciate your time. Thanks, Dirk.

Thanks, Paul, all is clear. Basically I have used my CHCombo and Yoke in the same manner, I programmed more views in addition to the panning with TrackIR. Some of the additional views I had to finger through sequentially, which I wanted to change, so not anymore. I've learnt how to access them directly. FSUIPC makes it really easy to connect your joystick to those additional functions. One more question since you are so advanced with the Views/Cameras system in FSX: by any chance did you happen to figure out how to disengage TrackIR in 2D panel view completely? Do you remember how it worked in FS2004 with TIR: when you switched to 2D panel your TrackIR just disengaged because that mode was static in fs9 code. Now it is not static in FSX (as they call it "2D panel is just a special case of 3D cockpit" or smth like that) so if you are in 2D panel view and toggle your TIR inadvertantly your whole 2D panel will start swivel or bob up and down with the movement of the TIR tracker/reflector on your head , which is a huge spoiler and dissappointment for me in FSX. There are a few planes that I would still love to fly both in 2D and VC, but so far I couldn't stand that terrible rotation (even occasionally) of 2D panels by TIR, so I haven't used 2D panels at all in FSX. Thanks, Dirk.

Paul, sorry, it's still a bit confusing for me. Like, first you refer to the FSX "Hotkey=" feature. I don't know what "Hotkey=" switch is or where it is (in aircraft.cfg, Cameras.cfg, FSUIPC.ini etc.). For example, I understand what "HotKeySelect=n" is and as I mentioned earlier that I thought I figured out how to use it while I was posting, which you proved by the second part of your post. Now I'm curious about "Hotkey=" that you mentioned. Where is it? I couldn't find it in the parameters of Camera configuration of ESP SDK. Please elaborate. Thanks, Dirk. PS: basically my goal was exactly what you described above, so I'm slowly learning and moving in your direction with these assignments. Btw, do you happen to use TrackIR as well?

Thanks Pete, all is clear. I hope I'll content my self with the excellent mouse macros in FSUIPC for all my needs. Otherwise programming takes too much time. Dirk.

Guys, anyone who is reading this and while we are at it: if you find a way to ultimately inhibit TIR panning in 2D cabin view (like it was in FS9) please post here. A huge shortcoming of FSX for me is that 2D view (Title = Cockpit) is panable with TrackIr. And unfortunately TrackIR in its turn does not have a discrete Pause control, instead only Toggle, which always creates a possibility for desynchronization of the TIR view OFF toggle in 2D cockpit view, if you know what I mean. Thanks, Dirk.

The above numbers are taken from one of my aircrafts, dont use them specifically. Reference to the one you'll be experimenting with (if). Dirk.

Then good chance we'll have more functinality in future versions of FSUIPC. :D Yes, FSX allows great flexibility in creating different convenient views in 3D specific to each particular aircraft only. You can go to Aircraft.cfg and find [CameraDefinition.n] section. Pls try to experiment with modifying them. For example, you can remove some of the views that you don't like completely, or modify them to your liking. My favorite line is InitialPbh = X, X, X, that allows me to create certain views with angles on the instrument panel in VC (POV wider or narrow, higher or lower). The awesome result of one of my modifications is that my default TrackIR eyeposition is not centered anymore in the middle of the screen looking at somewhere far ahead outside the cockpit but instead looks somewhat aksew from a higher position downwards at the instrument panel, which feels and looks way more realistic in VC. So when I want to look outside I "raise" my eyes (with TrackIR) and then my eyeview goes back downwards more at the instrument panel. Anyway, I think I've found the answer already while I was asking. I hope hotkeyselect switch from the global cameras in Cameras.cfg will work in CameraDefinitions of Aircraft.cfg, the rest is easy with FSUIPC. Thanks, Dirk. PLS note, that: InitialXyz = 1.3, -0.2, -12.52 InitialPbh = 5, 0, 90 are referenced from eyepoint=27.90, -1.55, 2.50 and make sure to reload either the aircraft or FSX while experimenting each time.

Dear Pete, I created custom camera definitions for one of my planes by editing its Aircraft.cfg file, where I added new cameras. I can normally go through all of them one by one by using standard FSX's keys (a/shift-a keys, as an example) and there is a similar facility in FSUIPC (sorry I forgot its name now). The questions is: is it possible to assign access in FSUIPC to each individual camera directly, instead of flipping them one by one in a row? Please note for what it matters these are in Aircraft.cfg not Cameras.cfg . Many thanks, Dirk.

Great tutorial and discussion, very useful for assigning my usb input devices (GoFlight and other). I've been very comfortable with the mouse macros in FSUIPC so far. Is there any difference performance wise using mouse macros or lua-based commands? Since I've used only mouse macros, sorry if this question shows lack of my understanding of the subject. Thanks, Dirk.

Thanks, Pete! You know everything, the rest around are just slackers like me. :D

Thanks, Pete! Sorry, my memory hitches (figured it out myself after I asked). Ig.

Yeh, thanks, 3.72 here.

I got interested only because I noticed some unusual and unsolicited crashes to desktop since recently after my comeback to FS9. Had not seen any of those before, nor could I recall anything relevant. Thought it was due to my new hardware. So, is V3719c a keeper?

Thanks, Pete. Unbelievable what you can do via FSUIPC in MSFS these days. I don't know, I find the interface very convenient, enjoying every moment of the read. Also, time to completely reconfigure my CH, Goflight and Aerosoft MCP. FSX will stay on the shelf for a while though. Thanks again, and very happy New Year to you, Pete! :D

What do you mean by "current" FSUIPC? Where have you ever seen an "Aileron Trim Set" or "Rudder Trim Set"? FS2004 doesn't provide any such controls, only the Left and Right controls. Pete I was just pointing to the fact I was using 3.71 version. Had never gone deeper before. So nothing specifically meant and no assumption made on my end. Btw I've never seen Rudder Trim Analogue Axis in FS2004 neither, but that doesn't mean it is not in FSUIPC. :wink:

Hello Pete, I've noticed there are no Aileron Trim Set and Rudder Trim Set functions in the current FSUIPC, whereas Elerator Trim Set is available. Anything special with these 2? Could be useful to cancel Aileron/Rudder trim with a keystroke. Aileron/Rudder Set or Center do not provide it. Thanks.

While I'm at it: anyone knows if it is possible to stop FS9 making automatic assignments for the new axes it detects? Something like assigning 'READ ONLY' parameter to devices.cfg? Thanks.

Ok, have figured it out, excellent flexibility and convenient interface, Paul. Has been improved again, even since I've been away from FS9 for about 6 months. Now back messing wth the install on my new hardware. Can anyone comment on if there is any advantage of not assigning main control axes in the game's UI at all and instead setting them up only in FSUIPC? Normally before I did not calibrate the axes in FS9, always did it in FSUIPC. Now in addition to that I might want to remove all the axes from MSFS to FSUIPC. Do you like the idea? Thanks.

Merry Christmas and Happy New Year! Pete, I'd like to assign a spare axis on my joystick to Rudder Trim Axis functionality in FS2004. This analogue axis on my joystick is controlled by turning of the knob. The knob has its left and right limits. The knob also has a middle position/notch. I know that there is no Rudder Trim Axis provided in the game. But I see it in FSUIPC module, so, I'm trying to make an assignment for it. The Axis Assignment Tab in FSUIPC sees the axis on the knob, when I move it. But under Joystick Calibration Tab the Rudder Trim calibration does not see it. Anything I can do for it to be recognizaed as a Rudder Trim Axis? Or any other solution to use the knob for rudder trim? Also, can I remove rudder axis assignment in FS2004's UI completely, and assign it instead in FSUIPC only? I tried to play with it but can't get FSUIPC understand that I'm moving the Rudder Axis (according to Joystick Calibration screen). The idea is to have all the assignments in one place (or two - in CHManager at the top, skip FS9, down to FSUIPC) as much as possible. Thanks!

Thanks Pete. You need not, quite clear now. Igor.