Litjan

I assume you are saying that the files can not be unpacked or written to the destination folder? Make sure there is enough space on the medium (harddisk) and that you have administrator and writing rights. Jan

Hi, there could be several reasons. Landing gear still down, cruising at low altitude, wrong speed, not all tanks filled,... The plane will carry 16.000 kgs of fuel, that is enough for about 5+ hours of flight. Your fuelflow should be about 2200-2500 kgs/hour (both engines) with a speed of ca. 420kts. If you don´t get these values, you are doing something wrong :-) Cheers, Jan

Hi Sdwr87, yes, that is correct. Apply an exception to your antivirus program (Windows defender, etc.) for the whole X-Plane folder. That should cure it. Make sure that you are not running multiple AV suites, too. Another reason could be running X-Plane off of an external harddisk. This is not recommended for bandwidth reasons. Cheers, Jan

No, Litjan has full, flowing hair!

Your gizmo plugin is not running. You either have not done the installation correctly or you have failed to activate your product.

+ Vr config file + Custom particle effects

Who is Jean?

1.3 is independent of Vulkan - you can still make your choice in 11.5X (OpenGL or Vulkan) and the IXEG will work fine. It will also work fine in 11.41. Cheers, Jan

Thanks for that advice, will check it out!

Track up? Navigational blasphemy! I will put it on the list. Not sure what the extent of coding necessary would be. Cheers, Jan

Definitely on our list - we have changed a bunch of stuff in the cockpit, so a new vrconfig.txt would be good. I have to investigate and learn how to make one. Not sure if SimVRlabs would like to help us with that...

No problem - the "show vortices" option was a remnant from X-Plane 10 times when it still worked. It was a "semi-legal" way of coding it, and X-Plane 11 doesn´t like it anymore. Thats why it will be gone with our next patch (version 1.3). X-Plane 11 is now supporting "particles", so this effect is done natively. Cheers, Jan

Hi there, please try again with the option "Show vortices" NOT selected in the left-screen-popout-menu (Preferences) - and let me know if this fixes the problem for you? Cheers, Jan

Hi Torbinator, the volume for the radios is on our to-do list - but not for 1.3, unfortunately :-( Cheers, Jan

I have just tried on my installation but have been unable to reproduce your problem. Are you running any other "third party" camera plugin, like X-Camera or such? Alt-tabbing in and out did not change any of my views at all. But just maybe this is a side-effect of some code-change that Tom did (for the replay mode). Lets see if this still happens for you after 1.3 Cheers, Jan

No, not yet. It requires a total rewrite of the rendering engine, even Vulkan isn´t capable of fixing this - maybe DirectX21 will... just kidding ;-) We still have a few bugs around from back then that we haven´t fixed yet. I understand that this is very important to you, though! Cheers, Jan

Hi everyone, starting today I will aim to make a video every week for your viewing pleasure...talking about IXEG development, flying our aircraft, showing you procedures, techniques and various other stuff. Stay tuned to this channel!

That is correct!

Hi Jeff, yes, that problem has been known as long as the "workaround fix" for the braking issue has been found. It was new to me that other parts of the lighting don´t work, either. The whole thing came down when Laminar "fixed" or rather "tightened" some of their code which in turn exposed two authoring errors we made when initially making this aircraft. One was assigning a (wrong) spring constant to a wheel and the second was an authoring error pertaining to the light code. The first one could be fixed in planemaker, but saving your fix would enforce the new code onto the lighting - which would break that. So it is either or. We have fixed that problem for the next patch. I never quite understood why people with a "twisty" joystick are also affected, I always thought that that axis counts as a yaw axis as much as real rudder pedals do. Cheers, Jan

I think what you are seeing is not due to the camera shake system we have implemented. You can tell by the fact that the camera angle is changing, whereas our code only changes the camera position. We also don´t have any code that reacts to longitudinal acceleration (braking, accelerating). I have tuned down the camera shake effect you get for rolling down the runway (fast) for patch 1.3, in XP11 it was too strong so that it could move the viewpoint persistently instead of oscillating around its position - like "shaking it loose". Cheers, Jan

Not sure where you heard that ;-) As long as fuel on board is less than 9000kgs it is in both wingtanks. Each wingtank feeds it´s engine, the crossfeed is normally closed. If fuel is more than 9000kgs, the center tank gets filled and it will then get emptied first and feed both engines. If fuel gets unbalanced you can open the crossfeed and turn off the boost pumps in the tank which is less full, then the tank with the higher level will feed both engines. If you dont turn off the boost pumps, one of both tanks will feed both engines, because one pair of boost pumps is always slightly stronger than the other ones and will win the "tug of war" of who can create more pressure. Cheers, Jan

Yes, there is a certain connection between applying the "brake steering fix" and cockpit lighting because you have to save the .acf with the new planemaker version. Our next patch (1.3) will fix that - it isn´t far out! Cheers, Jan

Did you ever run any add-ons that alter the lighting/artwork/colour properties of X-Plane? Like Reshade, SilverLining, etc?

Well, if you have the brakes helping with turns I could imagine they would disengage the autobrake. But with an extra axis for the yaw this should not be necessary (even with a twisty stick). Maybe wait for 1.3 and see if that works out better for you. Cheers, Jan

Thats totally odd. I have never seen that before. Do you have HDR on? It is also possible that something went wrong with your installation and it is not displaying the _lit_ textures... No idea what could be causing that... Sorry, Jan