martinlest

Not too many visitors here these days, but I'll give it a go :-) ... Is there a way to use the LVL CHG option in XP11? If I engage it to descend from cruise altitude, the aircraft more or less falls from the sky - it is descending at 6000ft/min (or more: that's as high as the gauge shows) within five seconds. Even if I reduce the SPD value first, the descent rate is basically 'plummet'; and of course, overspeed quickly follows. I always have to resort to engaging and setting V/S to descend. Thanks.

Thanks very much for the informative reply. I may still have another go and see if I can amend the dials myself (I don't think my 'skills', such as they are, are going to suffice in this case, however!), but glad to hear that IXEG will have a look at this problem (small though I suppose it is, in the general scheme of things!). Any 'fix' will include one for XP11, I very much hope. :-) M.

Well, I found that removing all the instances of 'manip_placebo' in the VRConfig file makes a huge difference (but not a very helpful one!): the dials now spin round so quickly that getting an accurate value set for altitude, IAS, heading etc. is virtually impossible. Changing the DEG_PER_ACTION values has no effect. Also, making any changes results in a warning in XP about 'minor problems' in the VRConfig file... No mention of 'manip_placebo' in the Laminar vrconfig file format specifications BTW.

OK, thanks anyway Jan. The information to edit could also be in one of the cockpit obj files: I'll have another look and post back if I do find a solution. :-)

Jan, any info on this? :-)

If it wasn't the TO warning (it sounded the same) then I have no idea what it could have been. Yes, next time I will pause the sim and take some screenshots. I haven't had any issues before this week (and I have had the 733 for some years now!). Odd. Thanks.

Hi. Yes, I know of that incident, . I always move the pressurization switch to 'FLT' after takeoff and I always set the FLT ALT & LAND ALT values during flight preparation (part of my checklist). The warning started the second I changed the cruise Mach value from 0.74 to 0.75 in the CRZ page of the FMC. I thought at first it was an overspeed warning, then realised in was the TO config. I went over and over the switches, but as I say, everything looked just perfectly normal. In the end, no way I could fly on with that loud horn sounding. Had to cut the flight, as I said.

Hi. Why would I get this alert (traced to toconfigwarn.wav) when I am at levelling off at cruise altitude? There were no annunciator alerts/warnings of any kind - everything looked perfectly normal (e.g. no inadvertent flaps), but the horn went on and on.. I found no way to shut it off and in the end had to switch off XP11 altogether to stop it. Frustrating after having been setting up and flying for almost an hour. Any suggestions as to the cause please? A bug?? Thanks!

Hi. Sorry, I should have added more detail to my post; I had already tried that, to no effect at all. (I wonder what the 'placebo' is at the end of each line). Thanks for the suggestion :-)

Hi. I only fly XP (11.55) in VR, and though for the most part the B733 has been pretty well set up in this respect, I find the dials/rotaries on the MCP (COURSE, IAS/MACH, ALT & HDG) hard to manipulate, in that for each full rotation of the wrist/VR handset, the values advance relatively little. To set up a flight altitude of 36,000 takes dozens of such twists. Unfortunately, holding the VR beam steady on the dials has no effect in the 733, you have to keep twisting and twisting and twisting. Given my less than youthful (slightly arthritic) wrists, this can end up being rather painful. Mapping the rotaries to a joystick dial or wheel doesn't help, as again there is so little movement of the MCP dial for any given input. (In any case, I don't have enough spare buttons or whatever on my joystick to allow this). Often, I can modify this myself, either in the vc_config or the cockpit.obj file, but in this aircraft, I don't seem to be able to make it happen. Is anyone able to help with this? Either the dials need to turn much more to the VR input, or keep turning as long as the VR handset beam is activating them. Thanks!! :-)

That's great, thank you. I have not moved over to XP12 (I only installed the demo), as the implementation of VR isn't as good as in XP11 yet (performance), at least on my setup, though I am sure Laminar will get there before too long; so I hope any fixes will go into the XP11 plane as well. I have been flying nothing but the 737-300 for some days now, trying to get this to work. As it happens, my last flight, with both options 'Disable Ghost Throttles' and 'Throttle mouse ops for VR' checked, produced the desired results, at least on this most recent flight: I could control the throttles with my Saitek X52 as soon as I disengaged SPEED mode (and yes, A/T auto-disengaged on touchdown). Only one flight, but encouraging. I'll try another later.. Thanks again :-)

Hi. Can I come back to this old thread? For the past 18 months I have only been flying in VR, so I no longer see the ghost throttles at all in the cockpit (they are only visible on the monitor). So I cannot sync the hardware throttles with them - and all too often end up with 737 throttles that ignore all inputs from my Saitek hardware. Irrespective of whose 'fault' this is, I must admit that I am now fed up with 737-300 flights ending in near crashes because, just when I need them most, I cannot control the throttles. The bottom line is that it is just not enjoyable flying this way and as much as I love the IXEG 733, I am put off from loading it up now, when so many of my flights end in near disaster because of this issue. Is there a way that I can turn this off, so that the throttles respond to my joystick as they do in any other aircraft I fly in XP11? I've watched and studied all the videos, but in VR it seems I am never going to get this working reliably. As I type this, my 733 is on the runway, just landed, and stuck: A/P is off, A/T & SPEED are off, F/D is off, I have matched the A/T ghosts by looking at my monitor, I have the correct profile and mappings... but my X52 throttles refuse to move those in the cockpit at all. After a two-hour flight, it's very frustrating. Please, if I am not now just to put this aircraft in a retirement hangar, to avoid the frustration of all this, could someone kindly help me to remove this throttle locking 'feature'. (I have tried with the option 'Disable Ghost Throttles' checked, but the throttles still lock up. I don't know what 'Throttle mouse ops for VR' does, I can't find any reference to it anywhere, but I can try it anyway I guess. Maybe it will help (I don't use a mouse in VR)??). Thank you!

When flying VR, does anyone have a sure-fire method of controlling the throttles with a joystick after landing? Though I haven't yet run off the end of a runway, it's occasionally a near miss, as the throttles sometimes (not always) 'stick' and cannot be moved with my Saitek X52 throttle quadrant. So far, more by luck than judgment I think, I do usually manage to guess where the ghost throttles might be and get the 'real' throttles down to idle in time, but there must (surely?) be a way to do this reliably every time? Is there a 'feature' I can turn off for VR flights (never fly any other way), so that the throttles will never 'lock' and not respond to input from my joystick? (I do not want to have to use my VR handsets on the throttles: on touchdown there is enough to do, without trying to use a handset - much too awkward Moving the throttles to idle has to be accomplished via my Saitek). Thanks for any advice.

I hope so too Jan! An aircraft much loved in the XP community of course: deserves all the TLC you can give it.

To avoid double-posting: https://forums.x-pilot.com/forums/topic/18521-i-dont-have-any-menu-in-vr-mode/

It's getting on for two years now since the O/P's comment. In the current version (1.33), I still cannot access the menus from within VR. That sure is "not very high priority"! Will this happen soon now please? Switching from VR to monitor to access the a/c menu is really not very practical. Thanks

Great! Please make it very soon.. OK, it's not quite a 'deal breaker' perhaps, but having to come out of VR and mess around on the screen disinclines me to fly the 733 at the moment (I have only flown in VR from the moment I first gave it a first try!). Which is shame, 'cos like everyone (I imagine) who flies the IXEG 733, I just LOVE it to bits... Maybe add the options to an CDU/FMC menu, as some other developers do? Even a temporary workaround (having the menus fixed somewhere under the captain's side window - there's plenty of room!) would be welcome. Can't wait to fly this plane in VR. Thanks.

Hi. Just wondered, a year on, whether the setup menus are working from within VR somehow now (can't see how to bring them up?). If not, will they be any time soon? Not so big a deal at the start I guess, but later on, closing doors, disconnecting GPU etc. before pushback means removing the VR headset, coming out of VR and starting on the monitor again, then going back... not great! Thanks

OK, thanks. If X-Aviation really needs to put the Gizmo plugin there, then yes, I can if needed always disable it and just have it active for my 733 flights. For now though I have tested the problem I mentioned a bit further and the Gizmo plugin is not the one responsible for it, so the search for the 'rogue plugin' will have to continue (and I'll leave Gizmo.64 active)...

Hi.. a general question on addon plugins like Gizmo: I have spent many, many frustrating hours over the past three days trying to find out why one of my payware a/c (not IXEG) has a number of issues in flight: it turns out that it is due to a clash in the resources/plugins folder with a different developer's plugin there (I have yet to find out which, but when I removed the non-Laminar plugins from that folder, the problems disappeared: so I am now at the stage of adding the plugins back to see which is/are causing the problems - a long, frustrating process as the issue only occurs if you set up a flight afresh from the gate and fly to above 10000ft). The developer in question wonders (in an email to me) why creators of other aircraft for XP11 have to have their plugins install into a default XP folder, where they can potentially clash with others, rather than stick to somewhere within their own aircraft folder structure (as indeed they themselves do). I don't know yet whether the Gizmo plugin will turn out to be the source of the issues, probably not (should know in the next few hours!) but I'd like to ask whether there is a reason why this plugin (as an example) cannot stay within the folder structure of the 733, and has to be installed into this XP common folder instead? The risks of that are clear from my past two days of trying to trace the source of the issues I am having with non-compatible plugins in the same folder. If the Gizmo plugin were in a IXEG/plugins folder and so (presumably) only loaded when the 733 were itself loaded up for flight, rather than every time XP starts, that would be OK, no? Many thanks.

I see, thanks for the clarification. I too assumed (since I thought I'd had the latest version installed) that something had been corrupted. I certainly do not recall seeing the wires before today (quite obvious with the colours of course - you can't miss them). Yes, must be because the pilot view has changed. That's fine - I am sure I'll learn to love the splash of colour.... doesn't look very safe though. Shouldn't an engineer have fixed it? (Had another flight this afternoon, BTW, and still all going well re. 'bank/roll' (so to speak))

Thanks. I only have Windows Defender active, but no, I didn't disable it. I do have a backup of my previous installation though, I could copy over files from there: would that fix this? Or I could even replace the new installation with the old one I suppose (if necessary), given that reinstalling did not fix the problems I was experiencing.

Wondering why (after reinstalling the aircraft yesterday) I now see bare wires hanging from below the MCP.. there's no clickspot I can find to close any little door. Googled and searched this forum for 'wires' but no results came up. Also, in the OH panel, what was my logo light is now labelled 'INOP'. Just cosmetic (I assume; hardly 'deal breakers' of course), but would prefer to have the a/c as it was (certainly no wires hanging out from the panel). Thank you.

Jan, you will be almost as relieved as I am to know that this seems to be fixed. I found at first that replacing the miscellaneous.prf file with the default one stopped the banking. But then if I re-engaged my IXEG joystick profile (from the XP onscreen joystick menu), the roll returned. So I deleted the IXEG profile and used the default one instead. I was able to map both the toggle gear and the TOGA function to the joystick in that default joystick profile.. and the past several test flights have been just fine, nice and straight after TO. I don't want to tempt fate though: 'tomorrow is another day' of course, and I wouldn't put it past my PC to spite me and reinstate the problem after I boot up in the morning: but otherwise.... Just FYI I attach the IXEG prf files (you may, in an idle moment, should you ever have one, want to see if you can find the problem: if I reinstate these files and go back to using them for the 733 in XP, the roll issue returns, so I think these files must be the cause). Also, a screenshot of my wing lift now, which looks a lot healthier. Thanks so much for your input... customer service here is clearly as impressive as the IXEG 733 itself! Martin IXEG B733 - Joysticks.prf.zip

I really thought this would do it - as I have a backup, I uninstalled (via the uninstall.exe and then installed again, via the installer. Fresh setup). Then back to the runway. Same thing. Here's the screenshot. However.... Given this result (I perhaps should have done this before), I tried the 733 in my 'vanilla' test installation of XP11.50: I simply used symlinks from the relevant IXEG folders (and Gizmo) in my full XP11.50 setup across to the clean installation. In that test, the a/c flies straight as a die. So no doubt there is something in my XP setup that is interfering with the IXEG a/c... all I have to do now is locate it! Haha. I'll let you know of course when (not 'if'!!) I find the culprit, (and we can ritually burn it, as it were)!