G1000 frame has returned (and the trim indication)
1 Like
Hotfix for Asoboâs update
Changes
- Fixed missing PFD frame and missing trim indication
- The power setting is kept when switching between PropControl and Full FADEC
- Added windshield defrost (permanently on as the levers are static)
2 Likes
It works!!! thank you!!
1 Like
Asobo appear to have made some fundamental changes to the DA40 visual model for no apparent reason.
I now get a strobing effect on the cockpit glass, as some of the reflective textures continually pop in and out, when viewed from outside. More noticable with a bit of cloud.
The changes have also affected the textures, as I am getting getting a bleed though of the decal plate used for the wing tip and tail graphic as you zoom out in external view. Also affects the rego as the top of the X in the registration is missing as you zoom out.
Also the interior textures for the sides and dash top pop in and out as you zoom in and out, but not the seat textures. Seems to be a LOD thing as it goes thorugh a few changes before it disappears. This past screen shot is from the hanger but the same happens in a flight.
I think someone was experiementing with the DA40 model and Asoboâs usual sloppy change control has let it through with the last update. The missing texture in the cockpit is just more evidence of this. I initially noticed this using the DA40X and one of my own repaints. But emptied the community folder and checked again to make sure it was Asoboâs core content that was the problem.
2 Likes
I was about to post about that too, the flickering on the cockpit glass is annoying as hell, itâs unbelievable their skill to â â â â up things that were working. Also in the bonanza I get a weird distorted tooltip when looking down to the lights panel, it suddenly flashes like a huge artifact.
1 Like
i only put the old interior LOD0 file back in.
perhaps i should have put all of the files back in 
1 Like
A definite yes from me.
Found I had a backup copy of the orginal DA40 myself I had used for repaints. Added the external model to the DA40X and all my repaints are now back to normal. Only the strobbing glass problem left now. Must have been a change to MSFS generally rather than the DA40.
Edit - spoke too soon. Fixed the black decals appearing everywhere but added a white rectangle on the top of the left wing. This is visible even on aircraft with white wings. There must be other changes that affect the DA40.
There are 19 textures missing from DA40 in 1.12.13.0 that were in previous versions. Only the last 2 texture files are required to fix the white rectangle problem I encountered when using the old external model. So if you decide to add in the old external model to the DA40NGX, then also add the following textures to the texture folder. Note that some of these textures relate to the internal model, so you should add those anyway. After adding the exterior model, you just have to chuck the textures into the texture folder and add them to the main .json file. No special action required.
Looking at the mess the DA40 is in, I think we must have got a developerâs test plane with the update. Whatever it is, it wasnât tested before being released.
I hope youâve reported all of this to ZenDesk.
Still canât believe that with 40 QA people and a now 4 week release cycle, they canât spend a half hour checking each aircraft before release.
2 Likes
This particular problem, and lots of others, is caused by some unannounced changes by Asobo in the texturing of aircraft. It looks like they are combining textures into larger single sheets, which would explain the âMissingâ texture files. The same thing happened with the 747. They moved at least 4 textures into a single sheet. But didnât tell anybody they were changing things. So now us repainters are scrambling to figure out exactly what Asobo did. When they could have just included at least a hint of the issue in the release notes.
The funny thing is, they left the _NORM files of the texture files behind. Thatâs how I was able to figure out which files were in the new texture for the 747.
There are other issues too, and the DA40 may also be affected. They screwed up the Registration decal on at least the Savage Cub and the VL-3. Perhaps on other planes. So, if you use the Panel.cfg hack to remove the registration on the outside, but still allow it to be used on the interior and for ATC, you have to change the
texture=$RegistrationNumber to texture=RegistrationNumber
Or the background of the Registration decal will be solid white on the outside of the fuselage, like it is for parked AI aircraft.
This isnât true for all planes, for instance, the C172 and C152 are unaffected by the issue. Not that I understand the fix. It just is what it is. Maybe somebody with a WASM programming background can explain the change?
Hi @MrTommymxr
Iâve just landed after my first flight with your mod and Iâm absolutely amazed! Finally this airplane is flyable and how well you made it, thanks a LOT!!
I noticed two things you might or might not be aware of so I wanted to tell you but using it with the latest WT G1000 mod it might not be up to you but maybe up to them? No idea 
-
The fuel transfer: The fuel actually drains correctly from the left tank only but the fuel gauge shows fuel decreasing equally in both tanks. This makes fuel transfer quite difficult, obviously.
-
FADEC: Iâm using the Honeycomb Bravo Throttle quadrant and using the FADEC option it only uses the âupper halfâ of the mixture axis. The sim normally uses the axis correctly over the full travel.
Is there any chance for you to fix these things?
Cheers and thank you a lot for this mod. =)
Asobob stuffed up a few things in 1.12.13.0 with the DA40. The cockpit and external visual problems can be fixed by using the old model files. But using the old models neither improves the glass strobing nor makes it worse.
Have been doing a bit of investigation and I think the strobing of the cockpit glass in external view is being caused by the DA40 NGX. Using MSFS default DA40 the strobing is only visible if you zoom in as far as you can. Then disappears if you zoom out even a tiny bit, so may have always been present. With the DA40 NGX installed the glass strobing is present at any zoom. The strobing is not related to the fix for the missing PFD instrument surround fix, as got the same strobing effect when I reinstalled version 6.4 of the NGX. Isnât related to the lighting effects, as removing them saw no change to the glass strobing. Finally I removed the DA40_cockpit.xml file from the NGX and the glass strobing effects disappeared. So I am guessing that there is some small part of the cockpit.xml that needs to be updated to match the default aircraft.
2 Likes
DA40 NGX ver 0.4.6.1 added the cockpit models from the pre 0.12.13.1 DA40 to fix the missing surround for the PFD. But only the LOD00 files were added. Adding the remaining LOD01 and LOD04 files to the NGX cured the cockpit glass strobing without the need to modify the DA40_cockpit.xml.
2 Likes
I am having trouble with the DA40-NGX autopilot and altitude.
Can someone please tell me what is the correct sequence to input a level (eg 8000ft) with the ALT knob.
Then how to get the aircraft to climb and maintain the level?
Then how to input a lower level and have the aircraft descend to and maintain that level.
When I input a new level then click AP and ALT, the aircraft just levels out at its current level.
Thanks in advanceâŚ
You assign altitude and then have to assign a mode which will be used to get there.
VS selects a specific climb rate (vertical speed) - you can dial that one on the ground as wellâŚ
or
FLC (Flight Level Change) will have it climb and select a pitch to maintain current airspeed. That would be a mode you activate in air once you reach a desired airspeed.
Once you have the mode selected, the AP will climb to assigned altitude.
Hrmmm, Baron Fripp sounds familiar.
If in level flight, set your new altitude with the ALT knob, then click the FLC button. This sets the current speed as the speed to be maintained for climb or descent. You can see the set speed value above the speed tape in Cyan in the PFD. If your new altitude is higher than your current altitude, increase power to climb. If your new altitude is less than your current altitude, reduce power to descend. The autopilot will adjust the angle of attack to maintain the set speed and climb or descend at that speed. The rate of climb or descent is controlled by the power set. The aircraft will automatically level off at your set altitude. When using FLC mode the autopilot will transition from FLC mode to ALT mode at about 300ft above/below the set altitude and the speed bug disappears from the PFD. When this transition occurs you then adjust your power to maintain the desired cruise speed.
Just clicking the FLC button while in level flight will do little unless you also adjust power. If you are already in a high cruise when you want to climb, you may not be able to increase power enough to climb. In this case, after you have clicked the FLC button, just reduce the set speed using the nose up button to the right of the FLC to set a speed less than the current speed, and up you should go. You can also use the nose up/down buttons to adjust your speed during climb or descent when in FLC mode. When you do this the autopilot will adjust the aircraft pitch to allow it to match your new speed.
2 Likes
Thank you both for your answers. Much appreciated.
Will give this a try next time I fire up MS2020 
Changes
- Textures and Models fixed by @BilingualHarp7 <3
- Added His liveries and Prop mod too
(if you have his liveries already you can remove them) - Fixed fuel tranfer rate (actually 1gal/min now)
5 Likes
Hi,
the download button says âDownload v0.6.4.2â, but the file name is âDA40NGXv0.6.4.1_WE4B1.zipâ.
Is this the correct file to download?