rojo2021

Thanks John, maybe. I'll try it. As a matter of interest I tried adding the default FSX Aztec to the profile I set up for the Alabeo Aztec. The camera views don't work for that either. Is that something you would expect? Roger

In one aircraft I have set up various useful camera views I can access in flight using buttons/hotkeys in FSUIPC4. The camera definitions are in the aircraft.cfg file for the aircraft I did this for and it all works really well there. I would like to use one of these views in another aircraft and have tried pasting the camera definition into the second aircraft's cfg file (changing the number to avoid conflict). The GUID i/d is the same - I would only use one at a time anyway. However the button does not do anything when I fly the new aircraft. Am I doing something wrong? Or not doing something I should. Help needed please. FSX SE/Alabeo Aztec/Carenado Caravan EX. Caravan aircraft.cfg attached aircraft.cfg

Thanks Reinhard, First for putting my mind at rest regarding my remarks about profiles. But also as you suggest I have run out of hotkeys so your method looks very interesting. I'll have to study it before commiting myself to it! My old brain needs that kind of respite. All the best to you and your flying. Roger

Morning Reinhard, I guess this is to do with the Alabeo model which comes with a very limited GNS530 but ready to integrate a Reality XP750 which I did (many thanks to Jean-Luc and Bert Piet). So I have the original panel albeit resized for the 750. I use the 750 (in this instance) as my Com/Nav1 and Xpndr thus replicating all that I had when I flew this aircraft. I leave the screen on the home page. I use NpC to select frequencies on the 750 using the keyboard. As a matter of interest I have a third variant of the Aztec which does not use any of the camera views I set up. Again this would change the ini file for the other two variants if they were in the same profile so it will be a unique one-aircraft profile. With this one I will be getting used to head tracking where I can look in all the places the cameras went. This will be a largely VFR experience and very handy for taking those quick looks to the side to see where the runway is (or went to!). What do you think? I am not using profiles as Pete intended but I'm not actually misusing them so I don't think I'm piling up problems for the future. Sadly we have strayed somewhat from the original problem which I still have, although variant 3 will not suffer from it as it will not use Cam Def .003.

Evening Reinhard, Thanks for your interest. Profiles? Yes, I have something specific in mind and maybe it won't work although it seems to at the moment, apart from 'the problem'. I have set up one variant of the aircraft using its old fashioned IFR panel and I have used various camera settings to achieve views that help with a stable and clear view of the instruments and some controls otherwise difficult to see. The ini reflects this where hot keys select the views. Some of these views are retained in the other variant but here I use Air Manager and a GTN750 on separate screens. I have also reassigned two of the buttons to 'fine' elevator trim instead of views I no longer need for that variant. If the two variants used the same profile I don't think I could achieve all that - if I made a change to one variant it would affect the other and I might not want that. I know that is moving back to aircraft specific but it suits my purpose and - apart from the current problem - it all works. It seems that using profiles would restrict how I want to use the variants available; really that I have a choice of the same aircraft with different paintwork/regs but all the same in the cockpit. Incidentally I only use a handful of different aircraft so I can keep track of what's what. I hope I've explained all this satisfactorily. I would be really interested in your reaction. Maybe I'm publicly displaying my ignorance but, hey I've only been doing this for a few months and I'm learning thanks to the help from guys like you, Pete and John. I take your point about Joystick assignments. I think that comes about because I have to disconnect from time to time. I need to tidy it up! Regards, Roger

I hope someone can help. I'm using FSX SE, FSUIPC4 and an Alabeo Aztec. The aircraft comes in various registrations and paint jobs all in the aircraft.cfg I have developed various camera views and use hot buttons (FSUIPC) to select them when needed. The camera definitions are also in the aircraft.cfg file (the problem one is Cam Def .003 Fuel Select & Cowl Flaps - a view otherwise obscured by the side of my seat). If I load FSX and the a/c version F-BALY I get all the views as I want them but if I then change to aircraft version WHITE (no registration) they all work except the one I mention above. It is much too close and to the left. If I then change back to F-BALY I have the same problem. If I reload FSX the same pattern is repeated. The button press is the same for each aircraft in the ini file and using the same Cam Definition. Very odd. (I will mention that I have purposely set up a separate profile for each aircraft although I can't see that that would affect the camera view.) I attach the aircraft.cfg and FSUIPC.ini files. Help much appreciated as ever. aircraft.cfg FSUIPC4.ini

Okay I won't. It's easy to see why all this is overwhelming to most of us. Anyway the method works and I can trim out very well now. I'm using btns 4,5,6,7 on the honeycomb yoke so it's quite easy to flip from fast trim to slow as they are the rocker switches next to each other. Thanks again John, have a good day. No doubt will talk again! Roger

Thanks John. I do keep looking before pestering you! I've finished sorting it and ended up with a 150/50 combination which seems quite near the mark and I'll test it tomorrow. Getting this sorted out has been both frustrating but also a learning curve so anything in FAQs would be great (for others now!) I used the lines that I had before and it works but I am a bit puzzled because when I look at the numbers the decimal equivalent of 3FFF is 16383 but C001 is 49153 or have I got that totally wrong? The ini file saves as I wanted it. 84=RC,5,Cx42000BC0,xC0010032 -{offset sword decrement, offset 0BC0 (Decr=50, Limit=-16383)}- 85=RC,4,Cx32000BC0,x3FFF0032 -{offset sword increment, offset 0BC0 (Incr=50, Limit=16383)}- 86=RC,7,Cx42000BC0,xC0010096 -{offset sword decrement, offset 0BC0 (Decr=150, Limit=-16383)}- 87=RC,6,Cx32000BC0,x3FFF0096 -{offset sword increment, offset 0BC0 (Incr=150, Limit=16383)}- As I said it works but I am just curious. Roger

Thanks John, Yes, I did take something out of context and it didn't work. For the sake of sanity I'm going to take the simple, simple route and use four physical buttons, two with the fast trim delta (256) and two with the slower one. This way I can get back to actually flying. I can then experiment separately with trying the sophisticated method(s). I appreciate your patience. Each time I do learn something new! All the best. Roger

Hi John, After digesting what you suggested I thought I would try to replicate the entry you posted from your own ini file to get the slow entry to the trim up/dn. If I understood correctly a short press would give me small adjustments to trim and for bigger changes I hold down. That right? I attach my ini where I have added the amended entries - my yoke is 'C' . My buttons are 4 and 5 for elevator trim. I also attach the log file showing button presses. However I only get the first action either inc or dec, and only the small amount (125) and nothing more if I hold the button down. Should there be a Repeat somewhere here? Any help appreciated as always, Roger FSUIPC4.log FSUIPC4.ini

Ah, it went so I'll try to repeat my previous message. The original button assignment through FSUIIPC was too slow. The offset was much faster and I have now slowed that thanks to your help. Presumably I can now delete the entries in the .ini file for other elev trim lines without finding I've upset something else. The idea of being able to tweak the trim setting by using a single press really appeals so I'm going to try to fathom that now. Regards, Roger

Hi John, I've tried twice to reply to you but neither has appeared. Thanks for your help.

I am trying to get the elevator trim to work as I want it to! (FSX SE/Alabeo Aztec) It is much too slow using the button assignment to a button on my Honeycomb yoke and I found a very old post which seems to offer a solution. It was the same subject in June 2013 to/from a guy called John Fee. I have followed his approach and as you can see below from the .ini file I have used the offset for the elev trim. My problem is that if I reduce the increment (256) and then fly, nothing seems to change and on checking I find that the adjusted increment (eg 128) has disappeared and been replaced with 256. Can you help? Has something changed since 2013 - I know a lot of things have! Thanks in anticipation, Pete. [Buttons.Alabeo Aztec] 0=RA,10,C65607,0 -{ELEV_TRIM_DN}- 1=RA,12,C65615,0 -{ELEV_TRIM_UP}- 5=RA,14,C65607,0 -{ELEV_TRIM_DN}- 6=RA,15,C65615,0 -{ELEV_TRIM_UP}- 12=RA,1,C66243,0 -{INC_COWL_FLAPS}- 36=RA,13,C65615,0 -{ELEV_TRIM_UP}- 38=RA,0,C66244,0 -{DEC_COWL_FLAPS}- 48=PC,0,C66856,0 -{VIEW_CAMERA_SELECT_6}- 49=UC,0,C66851,0 -{VIEW_CAMERA_SELECT_1}- 52=PC,3,C65561,0 -{PAUSE_TOGGLE}- 53=PC,10,C66858,0 -{VIEW_CAMERA_SELECT_8}- 54=UC,10,C66851,0 -{VIEW_CAMERA_SELECT_1}- 58=PA,3,C65758,0 -{FLAPS_INCR}- 60=PA,4,C66079,0 -{GEAR_UP}- 61=PA,5,C66080,0 -{GEAR_DOWN}- 62=PA,2,C65759,0 -{FLAPS_DECR}- 63=RC,7,C66855,0 -{VIEW_CAMERA_SELECT_5}- 65=PC,6,C66857,0 -{VIEW_CAMERA_SELECT_7}- 66=PC,11,C66859,0 -{VIEW_CAMERA_SELECT_9}- 67=UC,11,C66851,0 -{VIEW_CAMERA_SELECT_1}- 72=PC,28,C66052,0 -{STROBES_ON}- 73=PC,29,C66053,0 -{STROBES_OFF}- 74=PA,6,C66416,0 -{PAN_VIEW}- 75=PC,20,C66239,0 -{TOGGLE_BEACON_LIGHTS}- 76=PC,21,C66239,0 -{TOGGLE_BEACON_LIGHTS}- 77=PC,22,C66059,0 -{LANDING_LIGHTS_ON}- 78=PC,23,C66060,0 -{LANDING_LIGHTS_OFF}- 79=PC,24,C66240,0 -{TOGGLE_TAXI_LIGHTS}- 80=PC,25,C66240,0 -{TOGGLE_TAXI_LIGHTS}- 81=PC,26,C66379,0 -{TOGGLE_NAV_LIGHTS}- 82=PC,27,C66379,0 -{TOGGLE_NAV_LIGHTS}- 83=PC,1,C66579,0 -{TOGGLE_CABIN_LIGHTS}- 84=RC,5,Cx42000BC0,xC0010100 -{offset sword decrement, offset 0BC0 (Decr=256, Limit=-16383)}- 85=RC,4,Cx32000BC0,x3FFF0100 -{offset sword increment, offset 0BC0 (Incr=256, Limit=16383)}- 86=PF,4,C66079,0 -{GEAR_UP}-

Thanks very much Pete, I hope I can sort it all out very soon. Roger

Morning Pete, I did reply to you yesterday morning but it doesn't seem to have gone to you so here goes again. First thanks for looking at the files and setting out everything so clearly. It is a bit of a mess. Above all though it seemed/felt there was something to do with the pedals themselves and since yesterday I have done some digging there and my suspicions have been confirmed at least partially. I have sent for some more pots - one is definitely not working so I'll change all three. However regarding the axis assignments I will need to sort this out even when the pedals are repaired. It's obvious that I will need to un-assign some things. Can I do this by removing the line in the .ini file? Or is it more complicated than that? In FSUIPC there is the option to reset all axis assignments. I did try that (I can easily do them again) but it didn't seem to remove all the axis assignments. Is the .ini file rewritten each time the FS is closed down? I'm going off to a dark room with the manuals but I can't recall seeing anything to help me but I will look again. Thanks again. Roger

Hi John, Here are the files. I notice lots of 'Right brake' entries. These were when I pressed the left pedal. Regards, Roger FSUIPC4.log FSUIPC4.ini

Yes the controllers are disabled. I'll send the files shortly. Thanks for perservering (if that's how it's spelt!).

Hi John, I went through that and sorry to report that I still have similar problems. (The register has updated entries) The rudder was flipping as before full left/right or sometimes centred. At one point the right brake operated the rudder perfectly! I have tried to go back to basics and remove the rudder/toe brakes from FSUIPC in both axes and calibrations. Strangely I still get the 'differential brake' message with the left pedal which I can lose when I press slightly on the toe control. But now nothing else. Obviously I can fly but without a rudder it's not perfect! It does look/feel like a problem with the hardware. Is there anything that I can do in FSUIPC that might confirm that? Roger

Yes, I will! And the words 'don't mess with the registry unless you know what you're doing' is always there, so.. as I'm no expert... Can I just check here. I've used Pete's HidScanner and my controllers appear there as follows: Vid 068e (4 folders) there seem to be 2 for the CH yoke (I no longer have) and 2 for the CH pedals. Vid 06a3 (4folders) one confirms this is the Saitek quadrant (which is working well) and replaced the throttle, prop and mixture on the CH yoke. Vid 294b (1 folder) My new Honeycomb yoke also working well. Logic (!) seems to suggest that the folders to delete are the four Vid 068e referring to the CH products. The yoke I no longer use and the pedals that I hope will get a new correct registry entry. That right? Sorry to be a pain. Roger

I did a dry run and seemed fairly straightforward. Thanks. Hope this works!

Good morning John and thanks for that. I notice it mentions versions of Windows up to 8. Can I proceed as suggested in W10?

I hoped to solve this myself but it seems beyond me. I can't decide if the problem is my CH Rudder pedals/toe brakes wearing out, but the coincidence of two pots going bad on the same day? I am using FSUIPC4 for everything with the controllers off in FSX. I am running FSX Steam. I can set the rudder axis but when I try to calibrate it I only get the extreme figures (-16384 or 16383) or zero. The result is as you'd expect the rudder flies from full left to full right or maybe centres. A few days ago this was not happening and the rudder worked perfectly. But then when I tried to assign the toe brakes they interfered with the rudder. Now I have the situation where the right brake is okay - assigned and calibrated. Even got a nice pause before the brake came on. The left brake is like the rudder - all or nothing. I am using an Alabeo Aztec but changing aircraft gives the same rudder performance (DC3 and Baron 58). I attach a log file. Thanks in advance. FSUIPC4.1.log

Thanks to both of you. I learned a lot during this and hope it helps someone else. I like the idea that you can get rid of the yoke, Roman, in the Alabeo Aztec. Who needs two? Thanks again. Roger

Hi Roman, I checked and set up camera 7 to move close to and above the ADF and peeking/tilted down so I get a view clear of the frequency behind the levers. Works a treat. Like before I didn't adjust the zoom instead I changed the xyz settings and the pitch is set to 60 degrees (in initial pbh). I'm not too clear what you'd like me to do as a favour. Your amended view of the radio stack seems good to me. Are you wanting me to test it? I would need to change the Hotkey as I have used 7 already. By the way just for the benefit of anyone following this thread I came across a couple of useful things when I was searching. One is under 'FS Tips and Addons - understanding cameras in FSX'. The other was 'Camera configuration in FSX' by Gabor Hrasko (in English!)

Right. Reporting back. After your help I have resolved the problem - just hope these settings 'hold'! I now have the two snap-to views using the rocker switch. Each has a hotkey assignment and I used 8 and 9 for the reasons you suggested. (I don't have Ezdoc either and now I don't need it!). However regarding the zoom adjustment that didn't seem to make any difference so I moved the camera instead! Changed (by trial and error) each of the config entries - the xyz settings. Now really good for a quick look. Final question on the same topic. Do you think I'll be pushing my luck to use Camera 7 for a hotkey for another view which would be useful. The ADF is hidden behind all the quadrant stuff and I can't see the settings very well. The I'll let you be and just sing your praises! (I will anyway!)