[ Closed ] a320neo JARDesign ver 3.0r1-6 WIN/MAC 64 bit (X-Plane 11) (Page 6 of 11)

xplane crashed after landing @ LCLK and during taxi to the gates , not sure if this is related to Jardesign v3 R3 but i thought i'd attach the log file incase you want to look at it

That was X-Plane crash
--=={This application has crashed!}==--

not aircraft or plugins crash in this case.

Dunno what to say: those "lines" were fixed in v3r1.
For me it doesn't matter which effect or FSAA settings I'm using - I don't see any lines.

I didn't had this in the previous Version v3r2 is fine for me... i only had issues with the MCDU "FL CRZ NEW" msg
wich were fixed in the v3r3 for me, but now i see lines all over the windows as i said if i play with "Visual Effects HDR"...

Lowering "Visual Effects to medium" was almost good... if that didn't kill my FLOOD LIGHTS they just disappear.

(I tried to move some files and folders and the only ones that sorted effects was when i used the Custume Avionics Folder from v3r2 on the v3r3, that would fixe the airplane windows... but would kill everything else... switch the file a320neo.acf from the previous version would do the same)

------------------

Not a perfect fix, but working around NVIDIA control panel i was able to make it so the lines are not noticeable or not there. ^^

Hello, guys. First time here, just bought my A320.
I found a bug regarding glass transparency + HDR:

Here is what it should look:

And here is what is rendered behind the cockpit glass, everything is lit, no light FX (note there is raining, maybe the raindrop is causing that?)

EDIT: Yeap, I cleared the weather and everything is ok now. The raindrop effect in the windows is causing that problem. How can I turn it of while not fixed?

Thanks

Hi, I uploaded v3.0r1.r3 and on the first flight I noticed broken black lines across the front screen from inside the cockpit, however they were not there looking from inside too outside in cabin view. They were not there in v3.0r1, it was running smooth, so it's something in the update.
I played around with the antialiasing, I find my XP 11 runs fine with the antialiasing set to FXAA. If I upped the antialiasing to 2xSSAA+FXAA the broken black lines disappear. This does have a hit on frame rate, in FXAA I was running in high 20's, in 2xSSAA+FXAA I'm getting low 20's. I changed nothing in setup from v3.0r1 too v3.0r1r3, so, to run the update without the lines I'm loosing performance, that's a bit disappointing.

To solve this issue i just build new pack. This version posted as release 4 and include only 1 additional function - for this pack, you can use MCDU MENU to turn Off rain from windows (look at Page 3, please)

Hello sir, i see that you have the same problem as me, i wasn't using the AntiAlising so i also got those lines in the r3 version.

As i posted above i found a way that worked for me to go around that and get more frames in'game (for me! i dunno if will be the same for you)

In XPlane11 Settings :

Visual Effects - High (HDR) if lowered the black lines disappear but you also lose FLOOD LIGHTS, so leave it in HDR;

Texture Quality - Medium (lowering or upping didn't effect the black lines for me);

AA - FXAA (anti alising does affect black lines, but i can't use more than FXAA or it would kill my frames);

Next step i went to NVIDIA Control Panel (don't know if you have nvidia if you do take a look, otherwise... i don't know how to help.

AntiAlising FXAA - Activate
AntiAlising Mode - Application Controlled (worked better for me)
AntiAlising Definitions - Application Controlled (worked better for me)
AntiAlising Transparency -Multisampling

Anisotropic Filtering - Aplication Controled
Texture Filtering - Anistropic Sampling Optimization - Activate
Texture Filtering - Trilinear Optimization - Activate
Texture Filtering - Negative trend of detail level - Allow

Those values affected the black lines for me, i guess anyone could work around them, as it worked better for me, it may not be the same for others.

Guys, whats the deal of the "NEW CRZ FL" ?
I can put Cost Index on 99 and get the airplane almost empty on weight. Even so the PROG page shows an OPT of FL390, any value I insert above 300 show the msg NEW CRZ FL and then is filled with something like FL260.

What am I doing wrong?

edit: it's a 800nm flight, so it's not too short for the altitude.

Test flights done with V3.0R4. Here is what I've noticed:

+ TERR ON ND seem to work fine now. No more extra black click. Great!

- When you set ND range to 10 you can click one more lower. Nothing happens click is heard. After this if you change one higher it still stays at 10 and does not move to 20. Seems like there is some kind of extra step below 10.

- IRS align. Once again I say this because no reaction or anything has been said. IRS aligns maybe in 3 minutes but upper ECAM still says "x minutes to align". I have said this in every patch but haven't got any response?

- Thrust to 50% to check stability before take off thrust does not work properly. Thrust goes all the way up to 55-60% and then comes back to 50%. Should not do that.

- Vertical profile is very steep. You have to always use speed brakes while descending. I don't think is something that should happen?

I am also asking are you ever going to do minor tweaks so aircraft works as it should? There is many weird things going on like lower ECAM seems like a mess (many pages are simplified, no status). ND misses lot of symbols. Overall I think none of "not yet implemented" features have been even as topic. Is this going to change now that X-Plane 11 has release and amount of compatibility fixes should not grow?

Concerning my post 138, I don't know what JAR did, but the broken black lines are gone in the v3.0r4 update with the antialiasing back at FXAA.
Good news.