26 minutes ago, L3m0n said:

The only issue with mod installed in the community folder is a slow down in start up loading time.

Well, to be fair, the other issue is that mods can overwrite each other, and if you just throw a bunch in willy-nilly, especially ones that affect common systems like avionics, you could end up in a situation where things step on each other.    That's one of the downsides of using a system like Asobo has.  There are a couple things that can be done to help prevent that, though.

One is for mod builders to work in way that deliberately limits the amount of stock code they change.   I talk about this in the readme for my titlebar handle remover a bit.  We have not been the greatest about this at Working Title ourselves, but we are deliberately building new things in such a way, and taking steps as we go to upgrade existing work in that same fashion.

(I can also tell you that the CJ4 and the G1000 teams work in the same repo and share a code base.  If nothing else, no Working Title mod will conflict with another.  I can at least promise you that. 🙂 )

A second would be to take a moment to examine any mods you download to see if they overwrite files that any other mod is changing.   For small things this may be easy, but for larger mods like ours that could be a fair bit of work.  I've been playing with the idea of a small tool which would check peoples community directories for possible conflicts, but haven't had time to do anything with it.

Oh the whole, though, as long as you only install a small set of mods that touch "core" functionality (as opposed to just adding new scenery or altering single planes) you're not likely to have a lot of trouble.

With the release of the MSFS 1.9.3.0 patch today, you can expect most if not all mods to require updates to work correctly. The Working Title team advises you to remove all mods, including our CJ4 and G1000 mods, from your Community folder until such time as they are updated. As has been the case with past updates from Asobo, there were significant changes to the codebase. In fact, this update is the most invasive from a file structure standpoint, with many files moving locations and quite a number of name changes. About 17,000 files were changed. We are currently in the process of assessing these differences and will shortly begin incorporating them into our code. We will try to get updates out as quickly as possible.

5 minutes ago, cwburnett said:

With the release of the MSFS 1.9.3.0 patch today, you can expect most if not all mods to require updates to work correctly. The Working Title team advises you to remove all mods, including our CJ4 and G1000 mods, from your Community folder until such time as they are updated. As has been the case with past updates from Asobo, there were significant changes to the codebase. In fact, this update is the most invasive from a file structure standpoint, with many files moving locations and quite a number of name changes. About 17,000 files were changed. We are currently in the process of assessing these differences and will shortly begin incorporating them into our code. We will try to get updates out as quickly as possible.

Thanks and sorry you guys have to go through the hassle again. Hopefully, update will bring something good!

2 minutes ago, sd_flyer said:

Thanks and sorry you guys have to go through the hassle again. Hopefully, update will bring something good!

Ha, we all knew from the start it would be just an occupational hazard developing against a moving target. We've already seen some hints of some promising progress in the code, so hopefully this will be a net positive!

Can confirm this mod breaks the MFD in the new patched release. Just tried the King Air 350 Japan tour - AI could not fly the route and MFD totally blank. Deleting these is painful! 🙂

Edited September 29, 20205 yr by Flyfaster

The next version is out:

 

 

This hits me at the beginning of a 10 hour lateshift...well done! 😛

Seriously, many many thanks for all your efforts! I have absolutely no idea of that programming stuff and am greatly pleased that this community has more to offer than toxic posts and things...

Best regards,

Tom

Any idea how to reduce the screen brightness on a plane that dont got the external brightness knob ?  Like the diamond for example ?

 

EDIT - Never mind found it 🙂 

Edited October 1, 20205 yr by roi1862

24 minutes ago, roi1862 said:

Any idea how to reduce the screen brightness on a plane that dont got the external brightness knob ?  Like the diamond for example ?

 

EDIT - Never mind found it 🙂 

You could tell the rest of us. 🙂

 

11 minutes ago, bahnzo said:

You could tell the rest of us. 🙂

 

Ohh sorry i assumed i am the only one who doesn't know 🙂  

Click on the 'menu' softkey and there are 2 values in % one for PFD one for the MAP. with the below knob you can change the value.

In the B58 at least, the brightness control knobs are under the righthand seat yoke

I was plodding along in the C172 with G1000 (Working Title 0.3 modded version) now. About 50 minutes into the flight over Japan at 5000ft, on AP, GPS NAV, I wanted to initiate a climb to clear mountains ahead. Realized that on the left (pilots) G1000 display, ALT and Speed were ‘frozen’. Turning the knobs made the normal clicking noise but the numbers on the display were not moving.  Also the NAV and COM tuning knobs made clicking sounds when turned but the numbers here remained frozen. The frequency swapping button also had no effect on swapping active frequency. However, I could still select heading knob and heading bug would move as normal. The display was still on and responsive other than that. I could select heading and the Synthetic Vision was working. On the right side panel, all seemed to work ok. So the panel was not outright frozen, just elements of it.
 

Switching off AP to take manual control resulted in an immediate uncontrolled dive for the ground. Recovered and trimmed but the G1000 remained in that condition to landing. OAT showed +12 and switching on pitot heat made no difference. 
 

I cycled both the avionics switches and even the master switches. The panels started up again and ALT and Speed indications immediately froze at the new values that the aircraft was at, at that moment.
 

Is this a new or known bug? I have AI and multiplayer aircraft set to Generic. Done several hours in the aircraft, 1st time this has happened.

On 9/29/2020 at 11:27 AM, cwburnett said:

Ha, we all knew from the start it would be just an occupational hazard developing against a moving target. We've already seen some hints of some promising progress in the code, so hopefully this will be a net positive!

Hello. Want to say "Thanks" for the tweaks. Just wondering, I loaded both the G3000 and G1000 fixes this afternoon and when I load the TBM 930, the MFD is black with the borders for the engine instruments and the flight info at the top (in red). Neither area has anything else (no engine info or flight info). What could I be missing? Thanks for any help.

5 hours ago, rwilsonlj said:

Hello. Want to say "Thanks" for the tweaks. Just wondering, I loaded both the G3000 and G1000 fixes this afternoon and when I load the TBM 930, the MFD is black with the borders for the engine instruments and the flight info at the top (in red). Neither area has anything else (no engine info or flight info). What could I be missing? Thanks for any help.

This was an unintended consequence and the team is hard at work squashing that bug. Update coming soon I believe to fix that.

8 hours ago, RaptyrOne said:

I was plodding along in the C172 with G1000 (Working Title 0.3 modded version) now. About 50 minutes into the flight over Japan at 5000ft, on AP, GPS NAV, I wanted to initiate a climb to clear mountains ahead. Realized that on the left (pilots) G1000 display, ALT and Speed were ‘frozen’. Turning the knobs made the normal clicking noise but the numbers on the display were not moving.  Also the NAV and COM tuning knobs made clicking sounds when turned but the numbers here remained frozen. The frequency swapping button also had no effect on swapping active frequency. However, I could still select heading knob and heading bug would move as normal. The display was still on and responsive other than that. I could select heading and the Synthetic Vision was working. On the right side panel, all seemed to work ok. So the panel was not outright frozen, just elements of it.
 

Switching off AP to take manual control resulted in an immediate uncontrolled dive for the ground. Recovered and trimmed but the G1000 remained in that condition to landing. OAT showed +12 and switching on pitot heat made no difference. 
 

I cycled both the avionics switches and even the master switches. The panels started up again and ALT and Speed indications immediately froze at the new values that the aircraft was at, at that moment.
 

Is this a new or known bug? I have AI and multiplayer aircraft set to Generic. Done several hours in the aircraft, 1st time this has happened.

I had this exact issue tonight while flying the G36. Not the AP issue, but the partially frozen PFD. 

And I apologize as I managed to get it unfrozen and working as normal again, but I can't remember how. I think a softkey on the PFD did it, but again I can't be sure.