My new Flysimware C414 has gone mad

[jfri]

I have been able to start the engines once. But next time things are crazy. After turning on battery and alternators I hear noises and the voltmeter shows zero volt. Indicators and avionics start flickering inspite of avionics off. Engines not possible to start even from the EFB. Yes there are fuel and the fuel selectors are on main tanksand magnetos are on. I see no circuitbreakers poped out.

[Gazzareth]

14 minutes ago, jfri said:

I have been able to start the engines once. But next time things are crazy. After turning on battery and alternators I hear noises and the voltmeter shows zero volt. Indicators and avionics start flickering inspite of avionics off. Engines not possible to start even from the EFB. Yes there are fuel and the fuel selectors are on main tanksand magnetos are on. I see no circuitbreakers poped out.

Never had an issue with it, does sound odd if Avionics are off and still flickering. Is this trying a second flight in the same session, or a new flight?

G

[jfri]

1 hour ago, Gazzareth said:

Never had an issue with it, does sound odd if Avionics are off and still flickering. Is this trying a second flight in the same session, or a new flight?

G

New flight after new launch of MSFS

[gunther]

One possible cause for such issues are broken liveries. Make sure you don't have any liveries installed that didn't come with the installer. 3rd party liveries need to be updated whenever a new version of the aircraft is released. FSW tend to fiddle with the behind the scenes logic on most releases. Happens with the Lear 35 too.

[ark]

4 hours ago, jfri said:

New flight after new launch of MSFS

Another thing to try is a "clean" Community folder. Rename your existing Community folder to back it up (e.g., Community_BkUp) and then create a new Community folder. If you bought the C414 from the MarketPlace, put nothing in the Community folder, start the sim and load the GNS530 version of the C414 using a standard Flysimware livery. If you bought the C414 from SimMarket or the Flysimware store, only put the C414 folder in the new Community folder and again load a standard GNS530 version of the plane, and see how that works.

And there always is the admittedly small possibility of a bad C414 install. To test for that, either uninstall the C414 from the Content Manager, or manually delete the existing install from the Community folder, and then redownload/reinstall the C414.

Al

Edited June 20 by ark

[jfri]

10 hours ago, gunther said:

One possible cause for such issues are broken liveries. Make sure you don't have any liveries installed that didn't come with the installer. 3rd party liveries need to be updated whenever a new version of the aircraft is released. FSW tend to fiddle with the behind the scenes logic on most releases. Happens with the Lear 35 too.

I have no such liveries

[jfri]

9 hours ago, ark said:

Another thing to try is a "clean" Community folder. Rename your existing Community folder to back it up (e.g., Community_BkUp) and then create a new Community folder. If you bought the C414 from the MarketPlace, put nothing in the Community folder, start the sim and load the GNS530 version of the C414 using a standard Flysimware livery. If you bought the C414 from SimMarket or the Flysimware store, only put the C414 folder in the new Community folder and again load a standard GNS530 version of the plane, and see how that works.

And there always is the admittedly small possibility of a bad C414 install. To test for that, either uninstall the C414 from the Content Manager, or manually delete the existing install from the Community folder, and then redownload/reinstall the C414.

Al

I bought it from the marketplace. In the community folder I see a lot of stuff but nothing related to the C414.

[ark]

2 hours ago, jfri said:

I bought it from the marketplace. In the community folder I see a lot of stuff but nothing related to the C414.

Something in the Community folder can cause a problem even if apparently unrelated to the C414. In the past there was a mod for one of the Boeing airliners that caused a big problem because that addon modified some standard sim code that the C414 used.

Al

[solito]

I had once a problem with a cockpit colour texture addon which caused issues with the altimeter digits. 

[jfri]

On 6/20/2024 at 4:18 AM, ark said:

Another thing to try is a "clean" Community folder. Rename your existing Community folder to back it up (e.g., Community_BkUp) and then create a new Community folder. If you bought the C414 from the MarketPlace, put nothing in the Community folder, start the sim and load the GNS530 version of the C414 using a standard Flysimware livery. If you bought the C414 from SimMarket or the Flysimware store, only put the C414 folder in the new Community folder and again load a standard GNS530 version of the plane, and see how that works.

And there always is the admittedly small possibility of a bad C414 install. To test for that, either uninstall the C414 from the Content Manager, or manually delete the existing install from the Community folder, and then redownload/reinstall the C414.

Al

I did try that. Removed all stuff from the community folder and then put things back one at a time. Things worked after each item being put back so no entry in this folder could be pointed out as the cause of the problem. Before doing this I tried to delete the plane and then reinstall it. But after that the problem remained. Strange indeed.

[ark]

5 minutes ago, jfri said:

I did try that. Removed all stuff from the community folder and then put things back one at a time. Things worked after each item being put back so no entry in this folder could be pointed out as the cause of the problem. Before doing this I tried to delete the plane and then reinstall it. But after that the problem remained. Strange indeed.

The next thing that comes to mind is the possibility of controller conflicts. To the extent possible, as a test I suggest you unplug your USB controllers and just use the mouse in the VC to see if that makes a difference.

Al

[jfri]

1 minute ago, ark said:

The next thing that comes to mind is the possibility of controller conflicts. To the extent possible, as a test I suggest you unplug your USB controllers and just use the mouse in the VC to see if that makes a difference.

Al

Well no need for that since the plane works as intended now

[ark]

4 minutes ago, jfri said:

Well no need for that since the plane works as intended now

That's good news, what was the "fix"?

Al

[jfri]

13 minutes ago, ark said:

That's good news, what was the "fix"?

Al

I don't know. The problem was gone after emptying the comminity folder. But the same was true after restoring the folder

[Fielder]

I have had the same issue with other planes. If I turn on Dev Mode and swap planes, and then swap back to the first plane, it usually goes away. So the problem might be something about the "state" the plane was in.

Also the same issue with the A2A P40 back in FSX. And the same method fixed it.

Edited June 22 by Fielder