Release: Working Title G1000 v0.3 - updated to v0.3.5 on 14 Apr!

That’s good news.

Thanks.

You guys are on fire ! Super impressive results, ZeraKnight.
Can’t wait to see what you have in store for us in the next releases :slight_smile:

When I had this installed, the terrain on the C208 and the TBM930 went brown and not showing terrain at all on the screen

Wonderful job. Is there a way the g1000 can remember your brightness settings?

Did you have nexrad on? That sounds almost like nexrad in full overcast.

It should do it by default with this mod, along with a number of other settings. If you find that that’s not hte case, let me know.

Hi guys!
Any chance of including @aznricepuff G3000 enhanced mod to the Working-Title project? It has some conflict files with the G1000 mod.

We’ve been working with @aznricepuff already to do some joining of forces. They’ve adapted their changes to the WT file structure and pulled in a few of our enhancements and there’s a PR to pull it all in. I’m hopeful we’ll be able to release the next version of this as a Working Title project managed by a new team member and help each other improve both mods.

That said, I think that version 0.3.1 of the G1000, which I’m about to post here as an update, should remove any conflict between the current G3000 mod and this one, but I’ll need to double check on that.

3 Likes

New update.

We have a new version that takes care of the two biggest bugs that were reported with v0.3.0 – the broken synthetic vision on G3000s and map overflows on WPT/NRST pages when running track (I mean heading) up.

As part of the solution to the G3000 problem this update does something we have been meaning to do for a while. It moves any of the files we touch that are shared between avionics or airframes into their own location where only modified code can access them. This will avoid the sort of conflict we saw with the G3000 synvis. It will also improve our compatibility with other mods out there, and hopefully serve as a good example for others to follow. :slightly_smiling_face:

For this reason everyone who has v0.3.0 is encouraged to upgrade to v0.3.1. Please be sure to delete your existing workingtitle-g1000 directory before installing this if you haven’t already tried the pre-releases.

https://github.com/Working-Title-MSFS-Mods/fspackages/releases/download/g1000-v0.3.1/workingtitle-g1000-v0.3.1.zip

(This release is exactly the same as the second pre-release. If you had -pre2 installed, you don’t need to update at all.)

6 Likes

Hi! Thanks for the update.
Just wanna report that there are some files missing in comparison to 0.3.0. The files are still listed inside layout.json, but not present on the 0.3.1 release. AttitudeIndicator.js for example, and other files.

That’s exactly how I had to do it.

Thanks for the info I almost asked this same question. I don’t necessarily have an interest in the G36 (though maybe I should check it out) was hoping more to use it in the DA40’s. I do have a question though, other than the now fixed G3000 conflict, in the off chance I do use the G36 mod and this together, are there any other planes that may potentially be affected? Similar to how the A32NX project apparently interferes with the anti-ice buttons on the CJ4 for instance? (both the WT and stock suffer the same issue). I have no problem swapping mods around when I want to fly a particular one, just want to make sure of which mods need to be swapped around :slight_smile:

Can you double-check that? Some files moved between 0.3.0 and 0.3.1, but from what I can see they’re still in the zip file. Here’s that portion of layout.json as I see it:

{
    "date":  132464091510978693,
    "path":  "html_ui/WorkingTitle/Pages/VCockpit/Instruments/NavSystems/Shared/Templates/AttitudeIndicator/AttitudeIndicator.js",
    "size":  30366
},

And here’s an inventory of the zip file:

1 Like

Not that I can think of, no. Unless I overlooked something, every file that we modify should now be outside of the stock location with the exception of a stub HTML file what we use to load the instruments. For example, this is the entire contents of the HTML file in the stock location for the G1000 PFD in this mod:

<script type="text/html" import-template="/WorkingTitle/Pages/VCockpit/Instruments/NavSystems/AS1000/PFD/AS1000_PFD.html"></script>

That loads code from our own location and everything else boots from there.

That said… I did just double-check my inventory as I was writing this and I’m reminded how there is one stock file we still modify in place, html_ui/Pages/VCockpit/Instruments/Shared/Utils/XMLLogic.js. That’s because it’s referenced in the “base” HTML that loads everything in the cockpit and for now we’ve decided against messing with that and potentially causing larger issues.

I don’t know of anything else that touches this file but there could always be something. I’m hopeful that by the next major version we’ll have a safe way to take care of that one as well. In the interim, as long as no other mod you have changes that file you should be good.

Now I got it, they are inside “WorkingTitle” folder, not on the default directory. Now I see what you mean by “It moves any of the files we touch that are shared between avionics or airframes into their own location where only modified code can access them.”
Thanks!

Yep, you got it! That said, we have two different methods… some stuff has WorkingTitle right at the root, others has it somewhere down the directory path. The version with it right at the root is the method we have decided to use for everything going forward. I didn’t want to move more than absolutely necessary for this version, so the remaining items will be brought into conformance with the best practice for the next major revision. :slight_smile:

2 Likes

Any idea if the flybywire A320 mod is using that? Easy enough just to pull it out to be safe. I think I was more looking at it from the angle of the CJ4 mod or the default aircraft that also us G1000’s

It’s not, no. I checked. :slight_smile:

Your last version solved my issue.

This was exactly the way to go.

Thanks for that.

Ever since using the latest version I constantly get MFD freezes during my flights. Everything works up to a certain random moment where speed and altitude are not updating anymore.

Also, I still get the vanilla U-Turn-back-to-the-last-waypoint-thing when loading an approach in-flight. However, this already happen with the previous version of the mod.

The only other mod I am using is the G36 fixes and improvements.

Ever since using the latest version I constantly get MFD freezes during my flights. Everything works up to a certain random moment where speed and altitude are not updating anymore.

Try setting your Graphics/Glass Screen Refresh Rate to High, it worked for me.