This is from https://forums.flightsimulator.com/t/patch-1-8-3-0-ruins-converted-aircraft/274273/11

Quote

Among the utter failures of the new patch is a glitch where entering the cockpit of an aircraft converted from FSX will (most likely) immediately crash you to desktop.

I have about 10 aircraft that I have converted and flown multiple times. All of them worked ‘fine’ - still subject to the known limitations of conversions, but perfectly usable for my purposes - prior to the patch today. Now, I can only fly one of them without crashing.

Quote

Update: the crashes appear to be related to click spots in the cockpit. I have two aircraft which have no click spots and they still work.

I've got 67.5 hours in my ported Stearman, but it crashes immediately upon entering the aircraft after the patch.  Looks like I'll be flying the rest of the Cannibal Queen route in a different aircraft.  The Stearman has click spots, and they are a bit wonky.  Even with click spot problems it was great to fly.

I started from Niagara Falls and flew through Boulder to Washington State, then started flying my converted Golden Age Super Stearman.  I flew that to San Francisco, Las Vegas, El Paso, then east and north to Oshkosh and back to Boulder to complete the route in the book, about 2/3 of the entire route.  I made one flight out of Boulder to start the route again, intending to fly to Florida, Maine and back to Niagara Falls to complete the circuit.  

If anyone else is having the same problem with converted aircraft, go to the link at the top of this post and click the Vote button upper left.  Thanks.

Hook

This is NOT an utter failure of the patch. Porting of aircraft may in some instances be legally approved by their creators, in many cases not..... but how can this possibly be a fault of the patch? 

That is no different to complaining that you upgraded the engine in your car from a diesel to a petrol and now it does not run well on diesel anymore so the car engine manufacturer is an utter failure.

 

Converting old codebase and expecting them to work in MSFS is not the way to go. 

Jorg said in a recent interview that he had to convince addon developers to migrate to newer technologies/platforms/languages simply because these are much more powerful and capable than the ones we're deeply accustomed to in the past. It might take a while to get used to and establish newer processes and pipelines, but the end result is a much better performing product. 

So in a way, I'm happy converted aircraft's won't work. It's time to embrace the future which has much better possibilities.

i am kinda glad these dont work anymore, most was rubbish anyway.

The new patch hardly 'ruins' converted aircraft; they just don't work with it, which is not the same thing at all. This is not even remotely unexpected since the sim was never really designed to work with them anyway; many of those conversions were already either problematic, or had to jump through several hoops to be made to function. And let's be honest, most of those conversions were just people playing around with the possibilities and dipping their toes in the water to learn about file structures, formats etc.

If it was easily possible to make such conversions work well and survive patch deployments, we'd have seen pretty much every payware developer doing a quick conversion and banging their products out for sale again in the new sim; the fact that we have not seen this is because those developers know how problematic such conversions can, and will be.

It is of course interesting and fun to mess around with stuff and play with new options in the development tools and SDK, but we can certainly expect our modeling and other developing practices to be in flux whilst this occurs. For example, the most recent patch added a bunch of additional 'build' and 'clean' tool options for scenery production, which I've had a bit of a play with, some of which meant either re-doing or at least taking a slightly different approach to the creation of some bits for the scenery I was making, but I hardly regard this as having 'ruined' my efforts, it's just the way it is when you mess with a program which is undergoing some changes before being finalised in terms of development practices.

In the interim, all of those 'ruined' aeroplanes still work in the sims they were actually designed for.

Edited September 17, 20205 yr by Chock

2 hours ago, LHookins said:

If anyone else is having the same problem with converted aircraft,

Stop using the old nonsense.

2 hours ago, RaptyrOne said:

This is NOT an utter failure of the patch. Porting of aircraft may in some instances be legally approved by their creators, in many cases not..... but how can this possibly be a fault of the patch?

Please note that those were the words of the original author, not mine.  I decided not to edit what he said, even though it's not the way I would have said it.  Don't shoot the messenger;  go to the forum and complain there.  Lots of other people already have.

If we had ported aircraft that worked before the patch and after the patch they no longer work, I think we're on solid ground blaming the patch.  And we did have ported aircraft that worked.  Yeah, we had to jump through hoops to get them ported.  An early interview said we'd be able to do this, and to some extent we were.  Apparently no longer.

The Stearman looked surprisingly good in MSFS, and my next flight in the Savage Cub the super-clean cockpit looked a bit odd.  The Stearman flew quite well, too.  The only problems were the lack of sounds, which I hadn't tried to fix yet although the engine was fine, and the wonky click spots.
 

21 minutes ago, Chock said:

In the interim, all of those 'ruined' aeroplanes still work in the sims they were actually designed for.

Which I may well be doing.  I'm going to do one more leg of the Queen flight in the 172 and if it's as bad as the last, I'd rather fly the Stearman in P3D than the Savage Cub or similar in MSFS.  

Have you noticed the change from the constant slight motion in straight and level flight to what appears to be dutch roll yet?  The Savage Cub was certainly doing it for 1.8 hours.  Perhaps some people would prefer this.
 

13 minutes ago, Ricardo41 said:

Stop using the old nonsense.

I don't have enough years left in my life to wait for a native version.  Your mileage may vary.
 

Hook

Edited September 17, 20205 yr by LHookins

This is getting beyond ridiculous. 

You know, if it makes anyone feel better, even before the patch it didn't appear to be possible to do a proper port of other aircraft to MSFS.  I did a lot of work and was still missing a lot of functionality.  I don't think this is a fault of MSFS, but simply the fact that earlier sims did things differently.

I don't think you'll be seeing any straight ports from earlier sims, even from the original developers.

Hook

For the free thinkers there is a fix - 'ModelConverterX can remove all mouse rectangle assignments from the interior model.', for the sanctimonious there is no hope...

Converted aircraft were never officially supported. So if a patch breaks them, I wouldn’t expect it to get fixed unless it also effects officially supported features.

Well there goes hours of work down the dump flusher. Bummer.😕

12 hours ago, keithb77 said:

For the free thinkers there is a fix - 'ModelConverterX can remove all mouse rectangle assignments from the interior model.', for the sanctimonious there is no hope...

I'm game, but I'm not sure how to use the tool to delete click spots. Any insight?

https://forums.flightsimulator.com/t/fsx-import-showcase/165910/708 

Around Post 692

Quote

The 1.8.3.0 patch ruined many hours of work on converted aircraft. Here’s a workaround to get them flying again.

Those of you who are able to edit .mdl files in ModelConverterX can remove all mouse rectangle assignments from the interior model. Use the Object Heirarchy view, highlight all of the elements, and set the Mouse Rectangle field to None. Then export it back out, delete any related CVT folder that may be present, and you should be good to go.

I just tested this with about 8 different aircraft and all work again!

Yes!  Thanks.  I'll give it a try.  Requires a development version of ModelConverterX.

I was about this close -> <- to giving up.

I cannot describe the joy I felt flying this aircraft over this scenery.  Going back to a default aircraft just wasn't working for me.  

Hook

Edited September 18, 20205 yr by LHookins