Litjan

Hallo Jürgen, the only way to fix this would be changing the "increments" for the mousewheel - but then you would have to turn it a lot to achieve the desired dimming/brightening. I think it is a good compromise... Bis dann, Jan

b. look at my video - I think the problem is you using the mousewheel, it will "jump" the knob by certain amounts, so it looks like it moves backwards (strobe effect). EHSI brightness.mp4

Hallo Jürgen, this is a known problem with beta 15. You can update your avitab to fix it or wait for beta 16 which should be out fairly soon. Viele Grüße, Jan

Hallo Jürgen, I know about the DME ID´s - this seems to be an X-Plane issue - as there is no special procedure to tune and listen to them, compared to the VORs. The direction of the brightness knob for the Captain´s ND seems to be working fine on my end - make sure you are not misled by the "stroboscopic" effect when turning things really quick at low framerate (like a car´s wheels seem to turn backwards in old movies). The brakes don´t work exactly "opposite" - in real life you can depress the brakes to release it, just like in our plane. It is true, however, that in real life you have to depress the brakes to engage the parking brake, this is not modeled in our aircraft (we use the default X-Plane parking brake system). Changing the way the brakes work is not very easy in X-Plane, you can "fail" them (we do that to simulate them running out of hydraulic pressure) but to override them is a different thing (you can´t overwrite the brake dataref). Viele Grüße, Jan

Yes, I had the same synopsis. I could use the internet just fine, including playing online games etc. But when I tried to download (I think it was TerraMaxx) it would download most of it ok - but choke on some files. The daisy-chain may in your case be (beyond your control) in the way the data network is laid out in your building or so... I don´t think there is any other way to get you the installation files but as an online download. Some alternatives may be a connection through your cellphone or possibly a WLAN in a restaurant or at a friends place? I must admit I do not know if you can download the installation files on a laptop (while at McDonalds or Starbucks) and then later at home transfer them to your desktop and install them there? Hope any of this helps, Jan

Hi Iain, this explained it. The PLAN line "overwrites" the measure fuel quantity for planning purpose. Imagine you sit at the gate and wonder if you can make an altitude restriction on the SID or how much fuel you would have when you arrive at the destination... you put in your ZFW, but the fuel truck did not refuel the aircraft, so the GW calculated by the FMS (ZFW + measured fuel quantity) is not what you will actually have when you take off (too light). Another use for this field is entering the actual fuel value when the fuel summation unit messes up and the measured fuel quantity in the FMS is wrong. It would lead to all sorts of wrong calculations, so you can overwrite (hardlock) the value here. So you can enter this PLAN FUEL and this will effectively overwrite your "measured fuel". Until you eraze it. Cheers, Jan

While I am not an expert, often the "unable to download" errors point to a problem with the internet connection. I had this when having my computer behind multiple routers - plugging it directly into the DSL modem worked. Cheers, Jan

Hmm - I will try to recreate that problem by setting up your situation, 150NM northwest of YVO then to BEMOG,... I will let you know if I can reproduce that. Edit: Tried to set up your flight as close as possible but the LNAV was humming along very well and went after that magenta like the devil after the poor soul... so I am not sure what is interfering on your end. I doubt that the long range of the flight had anything to do with it. I recently took it from SFO to Honolulu and that went flawlessly... Also variation and latitude is not special for this flight. Cheers, Jan

Thanks for letting us know, teelo! I will try if I also get this with my Rift - and maybe it is also possible with the mouse? Normally the guard being closed will also close (connect) the battery, but maybe it is not checking the "state" of that guard but rather the "movement"... Cheers, Jan

Thanks for letting us know! Happy landings!

hi grizzly air, I have a hard time seeing it on your screenshot, but the mode annunciations on the EADI look correct. There are three reasons why the LNAV would not follow the magenta. First maybe you had a gizmo crash before and closed the window to keep on flying (this may mess up all calculations of the aircraft´s code) or second the waypoint did not sequence properly (i.e. you bypassed a waypoint too far abeam, so the FMS doesn´t consider it as "passed over"). The second problem can usually be fixed by going "direct" to the next desired waypoint again, so in your case click on the top (highlighted) waypoint - this will put it in the scratchpad - then enter it again on top of itself into the first line. This should give you a "dashed white" line emanating from the nose of the triangle-aircraft-position symbol to the desired waypoint. Hit the lit EXECute button and the plane should turn towards the waypoint. The first problem can only be solved by clicking the "reboot" option - but that will reset your aircraft to the startup situation, so make sure you pick "ready to fly" first and then "save" the flight like I show in my last video... The third possibility is that you have discoverd a bug...so if you can reproduce this situation somehow please let us know so we can track down why it happened? Cheers, Jan

Hi Torbinator, Tom has changed (fixed) the way that altitude and speed restrictions are read into the LEGS page, now you often see things like /5000A9000B which previously didn´t happen. He also enabled the user to input all sorts of combinations of speed and altitude restrictions, you can now enter 260B/5000A9000B which previously wasn´t possible. As far as the FMS actually considering these restrictions it is entirely possible that this got worse, as possibly the new format isn´t read properly by the FMS. So this will be fixed with the VNAV rewrite, but we will take no effort to band-aid fix this any earlier. I would say that if previously this worked somewhat for you, you got lucky! In general I would state that arrival scenarios with altitude restrictions simply do not work. Cheers, Jan

Hi, you can use the map view (key M) to set up for approach: 1. Extend flaps to 30 2. Set Vref for flaps 30 3. Pause simulator 4. hit key M 5. click on airplane 6. increase altitude and then speed, then drag airplane to position you like 7. click M, then P to unpause after landing, repeat

Hello! 1.) You should enter V1/VR/V2 for takeoff. Then fly to destination. Then before landing enter Vref. Do not set Vref before getting ready to land! 2.) PROG page is still not working well - we are working on making it calculate fuel and times better! All the best, Jan

It is normal if you use both autopilots - this is a feature called "mistrim" which the dual-channel approach does on purpose to make the nose pitch up (for safety!) if the autopilots disconnect on an autoland approach. If you intend to do a manual landing, only use one autopilot. Cheers, Jan

Too bad, I was hoping that was it... no, I am afraid there really isn´t a way to clinically compare the files. Another thought - do you have any type of live virus checking running? It could be that the attempt to read data from the NavData folder is not fulfilled in time because a live virus check is stalling that data stream. We have a similiar problem with the live checking of Windows Defender, and users have to exempt the X-Plane folder from checking or it will slow the data exchange down too much. Cheers, Jan

I may say that - I also fly the A320

Maybe a lua script writing to a dataref or something?

Oh, thanks! I will check that out! Cheers, Jan

Hi Ian, I recently tested a lot and always had the GW displayed on the APPROACH page as I need to be at a certain weight for my tests - and it has been updating just fine. I wonder if there is something unique to your setup that may influence this, as you also reported the problem with the grossweight being wrong after the turnaround? To my knowledge we never had any waypoint data on the ND, neither the times nor the restrictions (same for the RTE DATA on the LEGS page). This is planned, but not yet implemented. Cheers, Jan

Ok - I was hoping that would help Now I have to ask you to move all of your plugins (except DataRefeditor, the PluginAdmin and the two .framework and Gizmo) into a different folder to test if they affect your installation. Let me know if that helped? Cheers, Jan

Hmm, I can´t really tell anything wrong from the log files. Here is what I would suggest: 1.) Make sure you are updated to the IXEG version 1.32 (currently latest). 2.) Try to run the latest Gizmo beta (you should have gotten an email with a download for an "updater" which will keep your Gizmo version current). 3.) Remove (physically move to another folder) all other plugins and see if that somehow helps? If those steps don´t help, we need to wait for Tom to come home (Monday) or maybe @Ben Russellcan help with what that error message may mean? Cheers, Jan

I really can´t - I don´t even know what a paintkit is, to tell you the truth! Sad but true... Tom will be able to answer this, but he is out of town on family business and won´t be back until Monday. In all likeliness that is still the official paintkit, to my knowledge there was not a new one done. Cheers, Jan

After reading up on the forums - I decided to skip beta 15 and wait for 16, so I can´t verify your problem here. However I am convinced that it is isolated to your setup, as we would otherwise had more reports already. So please try and post a screenshot of when it is happening to you with the "brakes" value displayed on screen (little green numbers), also post a log.txt file and tell me which airport you are trying to taxi at. Thanks, Jan

Hello Hawk, we would need to see a full log.txt file attached (find it in your X-Plane directory) to start diagnosing this. I will also draw your attention to this post: this may help in singleing out the problem. Cheers, Jan