2 minutes ago, kaosfere said:

Hi, Robert, it's really rewarding to hear that from someone whose work I respect, so thank you for that.    There shouldn't be any clashes with the other G36 mod, and in fact it is customized to take advantage of our extended system display pages to show, eg, the two different loads on BUS1 and BUS2 🙂

I'm curious what you mean by "slightly more optimistic readings", I can't think of anything we did that would change the way basic information is computed, just how it's displayed in some cases, but I could be overlooking something.

kaosfere, I realize the timing could not be worse than today with an update on hours away, but, if at all possible would you be willing to roll in the Working Title G1000 v3.1 into this already merged mod. I would love to get in the middle of the future updates but, it just flat will not load into my system.

I'm thinking if we start with the mods already merged then they will load and noops like me all over the world will be able to fly and enjoy them rather than pulling out what little hair I have left.

Regards,

Ray

7 minutes ago, kaosfere said:

I think I see your problem, Ray.  It looks like you may have unzipped the mod into its own folder named after the zip file?   I bet if you look inside there you'll find another directory called "workingtitle-g1000", and inside that you'll see two json files (manifest.json and layout.json).  For any MSFS mod, the directory with those is what needs to be in the Community folder.   If you have what I think you have, take that wokringtitle-g1000 directory and put it right in Community and it should work.

OK thanks. I did notice we had added the word _Turbo to the airplane title and the G1000 mod does not have that.

Regards,

Ray

13 hours ago, robert young said:

I've based V1 of my mod on the standard G1000 engine readouts as (at the time of V1 publication) but I have used the excellent G1000 mod. I don't have enough time with the G1000 mod to comment but for the upcoming V2 I will pay more attention to temperature details.

If the values in question are available in a simvar (in this case, I'm guessing we'd probably want "TURB ENG1 ITT") we can definitely display them on the engine pages.   If you'd like some help working on a custom panel file for the next version of the mod I'd be glad to help get it sorted.

10 hours ago, robert young said:

Yes you can, but you will need to edit the  layout.jsn file in the mod's top folder and aircraft cfg  in the mod's simobjects folder.

There is also a slightly easier method that can be used with MSFS.  You can create a livery as an entirely new package and declare in the aircraft.cfg declare that this is a "variation" of another model. This is an example from a little paint-kit I've been working on for the M20R.   You still need to generate layout and manifest files, but it doesn't require messing with already installed code, which I think is a great feature.   A person could easily copy a stand-alone livery, modify it slightly, and have another stand-alone livery of their own making.

 

@kaosfere

Rob- So glad to read this!  Rob Young is a towering figure in FS, and you'd be in very good company.

:)

C

9 minutes ago, raymar said:

OK thanks. I did notice we had added the word _Turbo to the airplane title and the G1000 mod does not have that.

Regards,

Ray

Thanks kaosfere, I moved the action folder up to the top of the heap and it appears to be working. I am confused as to why I am not seeing the engine management mods though. I understand the Track Up means I have the v3.1.

I see the new soft key for "engine" but nothing happens when I click on it.  Just the word engine is highlighted but no actions or changes.

31 minutes ago, kaosfere said:

Hi, Robert, it's really rewarding to hear that from someone whose work I respect, so thank you for that.    There shouldn't be any clashes with the other G36 mod, and in fact it is customized to take advantage of our extended system display pages to show, eg, the two different loads on BUS1 and BUS2 🙂

I'm curious what you mean by "slightly more optimistic readings", I can't think of anything we did that would change the way basic information is computed, just how it's displayed in some cases, but I could be overlooking something.

Hi Rob,

I should have couched that comment more carefully. There is nothing wrong with your gauge. It is superb. What I meant was that in settting power for climb rates for my mod the default G1000 seem to read very slightly lower climb speeds and cruise speeds for the same power settings. It is only a tiny amount and not worth worrying about. I don't think you've overlooked anything and I didn't mean to cause you any panic!

16 minutes ago, kaosfere said:

There is also a slightly easier method that can be used with MSFS.  You can create a livery as an entirely new package and declare in the aircraft.cfg declare that this is a "variation" of another model. This is an example from a little paint-kit I've been working on for the M20R.   You still need to generate layout and manifest files, but it doesn't require messing with already installed code, which I think is a great feature.   A person could easily copy a stand-alone livery, modify it slightly, and have another stand-alone livery of their own making.

 

Thanks for that very useful info. There is still a lot to learn about methodologies for similar tasks in this sim. It seems that users are beginning to write their own SDK step  by step!

19 minutes ago, kaosfere said:

There is also a slightly easier method that can be used with MSFS.  You can create a livery as an entirely new package and declare in the aircraft.cfg declare that this is a "variation" of another model. This is an example from a little paint-kit I've been working on for the M20R.   You still need to generate layout and manifest files, but it doesn't require messing with already installed code, which I think is a great feature.   A person could easily copy a stand-alone livery, modify it slightly, and have another stand-alone livery of their own making.

 

Now, this is exciting news.  I am one of those guys that seems to want everything, but, don't know enough to get in out of the rain.

Ray

@raymar

Ray- like me, but you could get a hat. I’d recommend a Tilly.

🙂

C

13 hours ago, jimcarrel said:

I've seen it discussed in other topics where some liveries conflict with other liveries and also conflict with other types of mods.

Yes:
https://www.avsim.com/forums/topic/587007-bonanza-g36-no-oil-pressure/?tab=comments#comment-4376291

Now. It was getting late when I resolved the issues, and the only check I made to see if the workingtitle G1000 mod was working was to check the menu key for brightness control.  I did not check trackup.  The engine readouts were functioning.  Not looking further into it this morning as I just read the MFS updates are underway.

48 minutes ago, raymar said:

kaosfere, I realize the timing could not be worse than today with an update on hours away, but, if at all possible would you be willing to roll in the Working Title G1000 v3.1 into this already merged mod. I would love to get in the middle of the future updates but, it just flat will not load into my system.

I'm thinking if we start with the mods already merged then they will load and noops like me all over the world will be able to fly and enjoy them rather than pulling out what little hair I have left.

Regards,

Ray

Hi Ray, 

I don't think merging mods is always a panacea for success. It's a shame you can't get the G1000 mod working but I'm pretty sure merging it will not solve the problem. I'm baffled as to why you can't get the gauge to work properly. If there is some background issue that prevents your system from making it work then merging will not help as the underlying glitch will still be there.

I wish I could suggest something but I just don't know what to suggest. Sorry.

I'm happy to help you as I have time today, Ray -- between work and the patch that just dropped I may not have much 😂 -- but let's take it to the G1000 thread so we don't keep pulling this one off topic.

 

Greetings everyone,

I'm sure not the most experienced out there in terms of sims or airplanes, but I just wanted to say this thing flies fantastic!

One suggestion is to make a note in the accompanying instructions to make sure FS2020 is set to "Modern" and not "Legacy". I discovered that in Legacy mode not only are the standard controls affected, but the elevator trim operates too slowly and the aircraft constantly "hunts" for target altitude on autopilot. Because of this it also cannot follow a glide slope properly.

Once I figured that out I became convinced this is the best flight model in the game. Thank you!