KA350i Version 1.1 (SP1 - 1.1.29) [UPDATED MAY 24]

[jk.wall]

Yeah, still getting WX error in 1.1.9

[bmw969]

I no longer have such an error. Works great. Where are the reallight and trueglass textures located?

[FinnJacobsen]

I no longer have such an error. Works great. Where are the reallight and trueglass textures located?

The Textures for Reallight and Trueglass is located in:
\\Prepar3D\Simobjects\Airplanes\MV-KA350i\Reallight\
\\Prepar3D\Simobjects\Airplanes\MV-KA350i\Trueglass\

But there is no need and no benefit resizing the actual textures (I have tried to reduze the actual .dds files from 4096 to 2048)
What You do is to open the Reallight.xml and Trueglass.xml and then change all "4096" entries "2048".

Another thing You can try, is to delete the entire line in Reallight.xml where 4096,4096 is in, so no input for texture size exist.

I saw a modest decline in VRAM usage by doing so - but don´t ask my why .

But there is no doubt that Reallighty is the real contributer to the high VRAM usage.
Trueglass setting does not affect VRAM that much.

[jk.wall]

okay seem to have fixed the MV-WX.dll error, however as per topic Right engine crashes on every take-off every time I try a take off my left engine cuts out. This only started in v 1.1.8 and still in 1.1.9 happens everytime.

Welcome any suggestions I have tried removing everything MVAMS folders and ac and reinstalling no luck.

Not stressing the engines at all, MVAMS show engines as good.

Little frustrated

[bmw969]

Try the takeoff thrust 90%

[terjekj]

Have tested 1.1.9, and with rain on the windshield, FPS was 12-15.

If I change the TG and RL .xml-config files from 4096 to 2048, I only get a tad better performace, perhaps 2 or 3 frames per second better. Going to an outside view normally helps with FPS, but I see perhaps 15-18 FPS.

So, the problem must reside somewhere else. There is excessive computing going on in the aircraft and its systems, effectively ruining the performance of the aircraft. This happened from version 1.1.3 to the next, so the developers should be able to pinpoint what kind of computing and code has been altered since 1.1.3.

[eliott9417]

Same issues as terjekj here... little above 15 fps. Tried lowering everything in my graphics section but nothing seemed to changed the situation. Just bought the aircraft today but wasn't able to fly it. Kind of disappointing but I'm keen on making work if there is any solution.

[FinnJacobsen]

Have tested 1.1.9, and with rain on the windshield, FPS was 12-15.

If I change the TG and RL .xml-config files from 4096 to 2048, I only get a tad better performace, perhaps 2 or 3 frames per second better. Going to an outside view normally helps with FPS, but I see perhaps 15-18 FPS.

So, the problem must reside somewhere else. There is excessive computing going on in the aircraft and its systems, effectively ruining the performance of the aircraft. This happened from version 1.1.3 to the next, so the developers should be able to pinpoint what kind of computing and code has been altered since 1.1.3.

Strange...
I have a system far slower than Yours, but see 25 FPS on the grouns and 35 in the air (though flucturating quitea bit, but definitly smooth)

What is Your texture resolution in P3D set to, as well as dynamic reflections and shadow settings ?
Have You tried to clear Your Shader cache ?

[r601020]

SP 1.1.9
After install had no MVAMS. Attempted repairing but did not correct problem. Removed and reinstalled, now working.

Avionics
Terrain Fail
TCAS Fail
other?

Plane consumes(?) memory until P3D crashes.

[eliott9417]

Have tested 1.1.9, and with rain on the windshield, FPS was 12-15.

If I change the TG and RL .xml-config files from 4096 to 2048, I only get a tad better performace, perhaps 2 or 3 frames per second better. Going to an outside view normally helps with FPS, but I see perhaps 15-18 FPS.

So, the problem must reside somewhere else. There is excessive computing going on in the aircraft and its systems, effectively ruining the performance of the aircraft. This happened from version 1.1.3 to the next, so the developers should be able to pinpoint what kind of computing and code has been altered since 1.1.3.

Strange...
I have a system far slower than Yours, but see 25 FPS on the grouns and 35 in the air (though flucturating quitea bit, but definitly smooth)

What is Your texture resolution in P3D set to, as well as dynamic reflections and shadow settings ?
Have You tried to clear Your Shader cache ?

Might seem like a dumb question but how would you do that? (Clearing shader cache)

[frmdes]

The aircraft is getting better every version that you release, but i have to say, i'm still unhappy with the approach phase. Performed 2 flights today, and the aircraft is overshooting every turns when i activate the APPR button before IAF. Its hard to intercept the localizer, and sometimes it do not reach the FAF at the correct altitude (allways higher than it should). And another issue i had today, in 2 different airports (SBSV ILS-Z RWY10 and SBFN RNAV RWY12), is that the aircraft did not intercepted the GS and GP. The blue arrow has appeared in the navigation PFD screen, indicating the ILS, but the purple diamond didn't appeared in the vertical deviation bar. The automatic change from FMS APPR to GS (or GP) did not happened, forcing me to set VS and descent manually until disengages the AP for landing.
I'm using the latest version, 1.1.9

Regards,
Felipe Mendes.

[FinnJacobsen]

Might seem like a dumb question but how would you do that? (Clearing shader cache)

Find this folder and delete it:
C:\Users\{Your User Name]\AppData\Local\Lockheed Martin\Prepar3D v4\Shaders\

When You start P3D it will rebuild the Shader cache.

[Taguilo]

The aircraft is getting better every version that you release, but i have to say, i'm still unhappy with the approach phase. Performed 2 flights today, and the aircraft is overshooting every turns when i activate the APPR button before IAF. Its hard to intercept the localizer, and sometimes it do not reach the FAF at the correct altitude (allways higher than it should). And another issue i had today, in 2 different airports (SBSV ILS-Z RWY10 and SBFN RNAV RWY12), is that the aircraft did not intercepted the GS and GP. The blue arrow has appeared in the navigation PFD screen, indicating the ILS, but the purple diamond didn't appeared in the vertical deviation bar. The automatic change from FMS APPR to GS (or GP) did not happened, forcing me to set VS and descent manually until disengages the AP for landing.
I'm using the latest version, 1.1.9

Regards,
Felipe Mendes.

Felipe,

We have already discussed this:

viewtopic.php?f=105&t=12025

Regarding ILS intercept, you must be careful with the speed, especially when intercepting on a leg switch with tight angle. Try to be at 180 kias or less.
Besides, if using a wx addon like ActiveSky, select to keep barometric information for approaches, otherwise a change of baro value while in VPATH might produce a hard change in path angle, leaving the KA way above or below.

Regarding the FAF altitude, that is usually the bottom one, meaning you must not cross below, but there is no problem to capture the GS path before reaching FAF at a higher altitude; in fact that should happen 1 to 5 nmiles before.

Tomas

[tcarter.67]

Thanks for your refining efforts with the SP1 however with each new version is it possible to keep the changes made information up to date with the version....?
This has slipped in recent times and I would like to know what changes are being made to evaluate.
Thanks once again.

[qqwertzde]

Thanks for your refining efforts with the SP1 however with each new version is it possible to keep the changes made information up to date with the version....?
This has slipped in recent times and I would like to know what changes are being made to evaluate.
Thanks once again.

It appears to me that Milviz keeps the change log in the first post of this thread up to date.

Peter