Kosta

Hello Pete, Man, I hope you can help me, I'm pulling my hairs over here. I have all my devices assigned via FSUIPC. In my old W7 setup all was well. Yesterday I installed W7 new, and now all my assignments are mixed up. I figured already out after reading what is in the manual about this that it is about the GUIDs and how they are assigned. My old assignments are like this: [JoyNames] AutoAssignLetters=No 0=SideWinder Force Feedback 2 Joystick 0.GUID={6069C4D0-57D1-11DF-8001-444553540000} 1=Saitek Pro Flight Throttle Quadrant (USB) 1.GUID={C2282A60-767C-11E1-8001-444553540000} 4=Logitech G13 Joystick 4.GUID={DC6A74B0-5F42-11E1-8004-444553540000} 2=Saitek Pro Flight Throttle Quadrant (USB) 2.GUID={FA23FBB0-767C-11E1-8001-444553540000} 3=Saitek Pro Flight Rudder Pedals 3.GUID={3FA800F0-767D-11E1-8001-444553540000} 5...here is the yoke just apparently on the last boot up of FSX I didn't have the yoke on the table... What my FSUIPC on the new W7 install created looks like this: [JoyNames] AutoAssignLetters=No 0=SideWinder Force Feedback 2 Joystick 0.GUID={F8DB7420-F0A4-11E1-8001-444553540000} 1=Logitech G13 Joystick 1.GUID={F8DBC240-F0A4-11E1-8002-444553540000} 2=PFC Yoke 2.GUID={F8DCACA0-F0A4-11E1-800D-444553540000} 3=Saitek Pro Flight Rudder Pedals 3.GUID={F8DCD3B0-F0A4-11E1-800E-444553540000} 4=Saitek Pro Flight Throttle Quadrant 4.GUID={F8DCFAC0-F0A4-11E1-800F-444553540000} 5=Saitek Pro Flight Throttle Quadrant 5.GUID={F8DCFAC0-F0A4-11E1-8010-444553540000} As per old assignments table, 0 is my joystick, 1+2 are TQs, 3 are pedal, 4 is G13 pad and 5 is the PFC yoke. The new install says 1 is G13, 2 is yoke, 3 pedals, and 4+5 TQ. Now, my assignments in the FSUIPC are according to the old table, and changing them all would be a real real pain. Is there any way I can assign controllers as they used to be? Please say there is a way :neutral: Best Kosta

I'll give a 4.851 a spin tomorrow, now time to let this thing rest :) I will need couple of tries to see if its stable. No real way to test it as it is random.

Sometimes when I load FSX, I get a crash (error) while FSX is booting. It usually happens when I click somewhere else, eg. Firefox, while FSX is booting. Sometimes it's going to happen when I don't click somewhere else. I was hoping the loader might be helpful with this, as I guessed it might be a Simconnect thing. It never happens on a clean FSX.

I confirmed that after I went 4.85, the mouselook function is broken. I have mouselook on/off toggled with a spacebar, and since I updated to 4.85, it broken. After reverting to 4.83, problem disappeared.

Best I can answer you quickly, as I only got the email about the topic, is that yes, it is possible as I have done it. I don't like it though, so not using it, and can't tell you exactly how - but I remember something like assigning middle mouse button to my Logitech software and then assigning that in FSUIPC.

Yes yes, the Saitek bug, exactly that. Now all throttles show again as full range. But, I have another problem, which I am trying to fight now: in FSUIPC4.ini there are: [JoyNames] AutoAssignLetters=No 0=SideWinder Force Feedback 2 Joystick 0.GUID={6069C4D0-57D1-11DF-8001-444553540000} 1=Saitek Pro Flight Rudder Pedals 1.GUID={373E4120-767A-11E1-8001-444553540000} 2=Saitek Pro Flight Throttle Quadrant (USB) 2.GUID={37408B10-767A-11E1-8002-444553540000} 3=Saitek Pro Flight Throttle Quadrant (USB) 3.GUID={37408B10-767A-11E1-8003-444553540000} 4=Logitech G13 Joystick 4.GUID={DC6A74B0-5F42-11E1-8004-444553540000} 5=PFC Yoke 5.GUID={0AA06970-64A2-11E1-8001-444553540000} They should be: [JoyNames] AutoAssignLetters=No 0=SideWinder Force Feedback 2 Joystick 0.GUID={6069C4D0-57D1-11DF-8001-444553540000} 3=Saitek Pro Flight Rudder Pedals 3.GUID={373E4120-767A-11E1-8001-444553540000} 1=Saitek Pro Flight Throttle Quadrant (USB) 1.GUID={37408B10-767A-11E1-8002-444553540000} 2=Saitek Pro Flight Throttle Quadrant (USB) 2.GUID={37408B10-767A-11E1-8003-444553540000} 4=Logitech G13 Joystick 4.GUID={DC6A74B0-5F42-11E1-8004-444553540000} 5=PFC Yoke 5.GUID={0AA06970-64A2-11E1-8001-444553540000} How do I force those numbers in front to stay? This would mean I would have to do all my assignments all over again (a MAJOR pain in the ass).

Hi Pete, Need your help once again: My FSUIPC is recognizing the whole range on some axes on my Saitek TQ, and some only as half. That said, it has always been working, just suddenely out of the blue, since yesterday. Can't say if I changed something to cause this, nothing I can think of. I just want to know: is that normal? Basically always my first two axes on the TQ are recognized as 0 to 16384 and my last one as a -16384 to 16384. Furthermore, I don't want to calibrate in FSUIPC, due to known problems with NGX. Problem is: I'm using 2 TQs, and from 6 axes, I'm using two middle ones for Throttle 1 and 2 respectively. T1 is working OK. T2 is working only from about 80% N1, basically having a different range. In windows, both axes show up the same. When I try calibrating them, I can't do it with the "send axis to FS directly". EDIT: Ahhh, search is my friend.

Just a quick question... in my quest to better understand and apply Lua, I can't find the documentation on some commands I see being used...examples: if while true do etc. Is there a list or something? How do you know what to use and when/how to use it?

Now that is a swell idea! I have Dropbox account, so I'll just copy everything there. Only a matter of copying a folder or a file.

4.81, the issue is not an issue any more as it seems! Happy camper. Btw. it takes hours to configure even a small setup. I hope once it's done, I can save my files somewhere in a vault or something in case my computer dies, because doing this again... ugh.

Alright, testing. Just got it. Btw. mouselook-tooltips is fixed, many many thanks!

In FSUIPC4.ini, there are sections in which general key/button assignments are stored and then also per profile (aircraft). As in every setup, people have general assignments that are the same for every aircraft, and then those specific ones, only for that aircraft. As I understood it, it works separately in FSUIPC too, you can assign them separately. Yet on each flight reload, those two sections are recreated, according to the general assignments, in the specific profile of the aircraft. Let's take an example. These are my general assignments: [Axes] 0=0X,256,D,45,0,0,0 1=0Y,256,D,46,0,0,0 2=0R,256,D,47,36,0,0 3=3X,256,D,7,0,0,0 4=3Y,256,D,8,0,0,0 5=3R,256,D,3,0,0,0 [buttons] ButtonRepeat=20,10 1=R0,2,C65607,0 2=R0,3,C65615,0 4=R0,1,C1001,0 5=U0,1,C1002,0 6=R0,0,C65588,0 7=R0,6,C65624,0 8=R0,7,C65620,0 9=U0,7,C65622,0 10=U0,6,C65622,0 [Keys] 22=N79,8,66700,0 23=73,8,66699,0 25=N32,8,1127,0,1128,0 My aircraft profile is this: [Profile.Cessna 172] 1=Cessna Skyhawk 172SP Paint1 2=Cessna Skyhawk 172SP 3=C172N Skyhawk II BLUE 4=Cessna Skyhawk 172SP G1000 [Axes.Cessna 172] 0=0X,256,D,45,0,0,0 1=0Y,256,D,46,0,0,0 2=0R,256,D,47,36,0,0 3=1X,256,D,22,0,0,0 4=1Y,256,D,4,0,0,0 5=1Z,256,D,6,0,0,0 6=2Z,256,D,23,0,0,0 7=3X,256,D,7,0,0,0 8=3Y,256,D,8,0,0,0 9=3R,256,D,3,0,0,0 It's including axes, because over all my aircraft, throttle axes get customized, and you can only have the profile loaded, I made my axes manually by copying each section appropriately. Back to buttons... And if I start a flight, without entering FSUIPC or anything, this is what I get: [Profile.Cessna 172] 1=Cessna Skyhawk 172SP Paint1 2=Cessna Skyhawk 172SP 3=C172N Skyhawk II BLUE 4=Cessna Skyhawk 172SP G1000 [Axes.Cessna 172] 0=0X,256,D,45,0,0,0 1=0Y,256,D,46,0,0,0 2=0R,256,D,47,36,0,0 3=1X,256,D,22,0,0,0 4=1Y,256,D,4,0,0,0 5=1Z,256,D,6,0,0,0 6=2Z,256,D,23,0,0,0 7=3X,256,D,7,0,0,0 8=3Y,256,D,8,0,0,0 9=3R,256,D,3,0,0,0 [buttons.Cessna 172] 1=R0,2,C65607,0 2=R0,3,C65615,0 4=R0,1,C1001,0 5=U0,1,C1002,0 6=R0,0,C65588,0 7=R0,6,C65624,0 8=R0,7,C65620,0 9=U0,7,C65622,0 10=U0,6,C65622,0 [Keys.Cessna 172] 22=N79,8,66700,0 23=73,8,66699,0 25=N32,8,1127,0,1128,0 I don't want these assignments double. The reason: If I would decide at some later point to change the function to another button, and would do it in general, it wouldn't change in the profiles, but remain the old one. Right? I would have to change it for each aircraft separately, or go through fsuipc4.ini and delete all those buttons/keys sections, risking maybe deleting some custom made configurations for that aircraft. Is this in any way doable or am I doing something wrong?

Ah Pete, thanks. Nice that you've found another little quirk :razz:

Hi Pete, I noticed today when I wanted to fly my NGX, that my Tooltips are gone. I'm using them for Trim message, to see exactly what my trim is set up when rolling the wheel. Apparently, Mouselook function is disturbing the Tooltips function. Any chance of fixing this, if possible at all? Thanks Kosta

The reason I want to have 4 functions it to have 4 separate buttons for L.Engine Fuel Cuttoff and Idle and R.Engine Fuel Cutoff and Idle. Those two functions are a toggle mode, meaning each functions acts as a switch between Cutoff and Idle. Not disturbing, but I was hoping to have the setup the same way as on most of my aircraft. I'm currently in the middle of assigning all my hardware buttons same functions. Sorry, I don't know Nico Kaan's interface?

Pete, gotta keep you sane :razz: Found: LevelD767 Macro for the Fuel Cutoff Switch. Toggle function for L and R. Wish: 4 separate functions, L on/off, R on/off Tried with parameter, doesn't work. Looked into the MCRO file: 60=Fuel R=RX5250*X8300 61=Fuel L=RX51d0*X83cc What do the left numbers represent? They are looking into Module="B767Afds.GAU", so I guess that's the reference file. I never opened a gauge file... Is there a way to know how to create 4 functions?

Hmm, another question I wanted to ask: is there a way to change at what rate the chase distance is changed? I was right now thinking Lua if not possible via Parameter, maybe with the repeat rate in Lua?

Ahhhhhh, found the error! My aircraft profile had also Space assigned. I only had to check the profil checkmark, press space, and there it was, an old assignment disturbing. Log has shown me that even if I disabled Space in non profile, FSUIPC was still sending it. Then I got the :idea: . Thanks a lot for the help!

According to log, my space is sending MOUSE_LOOK_TOGGLE, although my Space is set to send Mouselook On and Mouselook Off.

See the edit above. I'll try the logging.

I know. I have changed it. I understood that part. I don't have or want to use the mouse middle button. My scroll wheel button is very very hard and very unpractical to use. I want to use the spacebar. Not that I was aware of. In FSX, if it's working in the cockpit, it's also working in external, and vice versa. If I disable controllers in FSX, if my Space in FSX controls is unassigned, what could be then interfering? OK, I tried really checking every corner: FSX controllers disabled. "Mouse - View Direction (on)" control in FSX unassigned MISC Mouse Look checked. On the Key Press page, Space assigned to Mouselook On when pressed, Mouselook Off when depressed, No repeats checked. And yes, FSUIPC says 4.802. And it centers. What am I doing wrong? EDIT: Also noticed if I uncheck the Mouse Look in MISC, I get the cross on the screen when pressing space, but nothing is moving. Also the cross position is being saved, meaning after I press space at later point again, the cross is going from the last position where I released space.

Hi Pete, Thanks for the effort! What do I need to do to have the space as a button to activate mouselook so that it doesn't re-center each time? I did read the manual, it states: "You can assign the space bar press to 'mouselook on' and release to 'mouselook off', with no repeats, to do the job well." - now, I did that, disabled controllers in FSX and also enabled mouse look in miscellaneous in the FSUIPC. I have noticed you are talking about the cockpit views. I was talking about the external view all the time. The external is still re-centering, also with the above setting. Cockpit is fully controlled by EZCA. Also if I close EZCA, I can use FSUIPC to look around and in the cockpit, it also recenters each time. And if I turn off Mouse Look in MISC, then it doesn't work at all.

Pete, don't sweat it. It's not life-threatening! I'll be looking out for the interim whenever it comes. Thank you.

Exactly. That's exactly what it's doing. I don't know how complicated this is to make. Right now, turning off FSX controllers is just a fancy thing, if I enabled it, I have no sideeffects. But it might come in handy some day (for instance, setup of Thrustmaster Warthog requires controllers disabled, or so I read on one thread) so maybe it wouldn't be a bad idea to have that functionality.

Yes, it only centers when first activated, but isn't the "first activation" every time your press mouse toggle param 1? Or is it supposed to center only once per session? My setup is simple: Mouse Look Toggle, with "no repeats" checked, on both when key pressed and when key released. So that means when holding space, I get to move. Now, again, let me try describing it again: - press space, move the mouse to the left, aircraft pans - release space, aircraft is kept in the panned position - leave the mouse left, where it was, press space again - aircraft pans back to the middle, together with the mouse - mouse is still on the left position on the mousepad Now, this is annoying for two reasons: - each time my aircraft pans to the middle - sounds change, and it's looks like an instant bug - also I'm required to pick up and recenter my mouse on the mousepad - and that each time I have been using space and turning Why did it annoy it in the FSX implementation? In FSX it just restores the old position... Maybe mine is the first, as I tried it just yesterday, but maybe not many are using it and still using FSX version. Best Kosta