Litjan

You can configure all the views you want (well, up to 10) with the default X-Plane custom view system. Use CTRL-Numpad (number) to store a view, then just the Numpad (number) to recall it. You can even save these views to joystick buttons. Engine start too fast is known, it is a Laminar problem, Austin is working on it, we are providing an interim fix with the next update (it still looks weird, but the total time to idle is better). Cheers, Jan

I agree with Cameron, if this was a problem unique to our aircraft, we would have seen more reports like that. Laminar should be able to trace your crash and see what it is caused by, especially since you can invoke it so readily. They can also contact us (we are in communication with LR like most developers are) if they have any further questions or have an idea how to fix the problem from our side). Sorry we can not help you immediately.

Ok, thanks for testing everything so patiently! I will see what Tom will say, maybe there is something obvious that we can fix easily. Thanks again and I hope you can live with the blurries for now, Jan

Can you try do disable your simHeaven scenery just to test? You can add the _DISABLED into your scenery.ini file to disable them temporarily, like this: SCENERY_PACK_DISABLED Custom Scenery/X-Plane Airports - KBTV Burlington/

?

@AngelOfAttack I have identified and fixed the reason for the weird pitch during takeoff and landing. It will be fixed in the next version, so dont get too used to the effect ;-)

I have actually noticed, too - and have tried to fix this, but have not been succesfull yet. It was working in XP11, too. The setup for the blur seems to be correct, flames and sparks (damage) are working fine...just no heat blur. I have to investigate further...

Hmm, it surprises me that you are getting blurry textures at less than 3GB out of your total 6GB used! Maybe also try running at the highest texture setting and see if that helps? Does this only happen when running the IXEG? Or also with other aircraft?

You are right, I can see it with the "front galley lights" being on! I think it is an artifact of X-Plane´s lighting engine resolution, lights that are further away will have less resolution when it comes to their lighting effects to save on rendering performance (kind of like the shadows do, too). I think the ultimate goal her is to emulate the cockpit door and rear wall being really opaque...so that there is no lighting from the cabin if the door is open (in the real airplane the galley lights go dim when the cockpit door is open).

Hi Chip, this certainly sounds like Vulkan reducing your texture resolution to keep total VRAM use below your threshold. One thing you can try it so reduce your "Texture Quality" level in X-Plane globally, this will make ALL texture slightly less sharp, but not just SOME very fuzzy. Another thing is running at high monitor resolution or even multi-monitor, this will also fill up your VRAM quickly. Did you look at the VRAM PROFILER in the developers menu of X-Plane?

Hi axmiha, I thought you were talking about the screen itself - but the keys should have backlighting that comes up with the center pedestal rheostat, which they don´t! So thank you for reporting that! That "phong" you see is not showing on my screen, but I have seen something like that before, I think it may depend on graphics card settings/driver/anti-aliasing?

I think you need to disable the simHeaven scenery, it might be too much for your hardware - can you just try it to see if it helps? Copy it to another folder (so you can copy it back if that doesn´t help).

Works fine on my end...

It works fine here:

Yeah, I think he can not create new threads yet (his first post)...so I let it go uncommented ;-)

Hey Morten, great to see you chime in! I will take this up with Austin in a little bit, right now we are on his case to fix the too rapid N2 rise after fuel is injected. You know him, it is better to feed him stuff one after the other ;-) All the best, Jan

That may be the missing condition - I will check the code. As for the GS deflection, I can verify this with DATA OUT, I think there is a field for glideslope deviation.

Thanks for testing this, Jude. Let´s see what Tom can find out!

What country are you dialing in from, and what internet provider do you use?

You have many critical plugins in your installation (SAM, Xjet, XPRealistic, Terrain radar, VFR hungary, ...) Remove all third party plugins and scenery with plugins, then try again, please.

Hmm - can you post the log.txt from your X-Plane main folder after it crashed? Thanks!

Looks good! I am out of ideas, I will file this bug and hopefully Tom can figure out why this only happens to some people...

I have seen this, too - I am not sure how the real world deals with this, I believe there will be very poor reception on the upwind side so the GS doesnt show. But I don´t know if there is any code to "suppress" a GS warning if the aircraft is on the upwind side in the real GPWS? If an ILS is tuned and the plane is sufficiently below the GS, the warning will play. We are not doing anything with the glideslope as transmitted by X-Plane. Procedures will differ between airliners, but we never tuned the ILS for departure, unless it was part of the SID navigation (like at Marseille or Orly).

Well, the log you posted has a bunch of plugins loaded (including the 767), that is why I was asking...

I will doublecheck that, thanks Jürgen!