• There seems to be an uptick in Political comments in recent months. Those of us who are long time members of the site know that Political and Religious content has been banned for years. Nothing has changed. Please leave all political and religious comments out of the forums.

    If you recently joined the forums you were not presented with this restriction in the terms of service. This was due to a conversion error when we went from vBulletin to Xenforo. We have updated our terms of service to reflect these corrections.

    Please note any post refering to a politician will be considered political even if it is intended to be humor. Our experience is these topics have a way of dividing the forums and causing deep resentment among members. It is a poison to the community. We appreciate compliance with the rules.

    The Staff of SOH

  • Server side Maintenance is done. We still have an update to the forum software to run but that one will have to wait for a better time.

HELP: A-26B Invader_SOH makes the sim crash

MaskRider

Tiller of Soil
HELP: A-26B_Invader_SOH makes the sim crash

Hiya Guys,

Was ist los?

I downloaded the A-26B_Invader_SOH.zip from here at SOH.

When I choose it in FF all of the load outs are there in the preview window and everything seems fine.

However, when I click "Fly Now" I get the following error message and the sim crashes.
attachment.php


I am loading it straight from the extracted download. No changes or tweaks.

It isn't an issue with having too many planes, I am way under the limit and I am also nicely below the limit on object_dp's.

I also tried deleting all index and filelist.dat files

I can choose all other planes and go flying in FF no problem.

It seems something specifically about this plane that my sim doesn't like.

Any ideas?

Thanks!
MR

Oh, and PS: I noticed this when looking at the aircraft.cfg file:

[fltsim.0]
title=Douglas A-26B Invader (FS9) 3rd Bomb Group, Phillipines 1945

Don't know if the bit about (FS9) is relevant or not. Just grasping at straws.

MR
 

Attachments

  • a-26-invader-error-00.jpg
    a-26-invader-error-00.jpg
    179.9 KB · Views: 10
Last edited:
Here is another hint.

When I start the sim in FF, with another AC loaded, and go to spot plane view, I can switch over to the A-26 and fly it no problem.

However, as soon as I switch from spot-plane view to cockpit view the sim crashes, no matter whether I am sitting on the ground engines off or in the air engines running.

Also, so long as I am in HUD or Maximize everything is jake. But when I switch to Panel, crash.

A panel issue of some sort?

MR
 
Last edited:
Going to guess a pre Win7+ plane that only uses a 1024x768 panel. If yes open the panel.cfg and remove render_3d_window=1 or set to render_3d_window=0
 
Thanks Allen,

I opened the panel.cfg file and there is no line containing the word "render" or "3D".
Are you suggesting that I should add such a line and if so where does it go?

BTW, two more points of interest:

  1. the A-26 also runs fine in VC view.
  2. my gauges folder already contained all 87 gauged contained in the a-26 zip so I didn't over-write any of them.

Its something about the 2D "Panel" view that is making it go haywire.

MR

PS: just for the heck of it, I over-writ the gauges.

Still no joy.
 
Last edited:
MR: It sounds like you may have a corrupted panel.cfg. Try downloading the plane again and replacing the old panel.cfg with the new one. :wiggle:
 
MR....

......I may be in the weeds here, but check your folder name against the name in the cfg. file. If yours is straight from the d\l the names are different. The plane folder reads "A26 Invader_SOH" and the cfg reads "Douglas A-26B Invader (FS9) 3rd Bomb Group, Phillipines 1945." (Quote marks are mine) They are different. Maybe make them the same and see what happens. Also, and I am not really sure on this as it could be a mix-up in my library, I think there was a later ,mdl change.
I had changed mine and the plane flies in all the panels and screens with no problemos.
 
Try using a stock panel like the P-38 for a test. Maybe it is gauge related...
 
Try using a stock panel like the P-38 for a test. Maybe it is gauge related...

Hiya Allen,

Thanks for the input. Yes. It works fine aliased to another panel.


Fibber said:
......I may be in the weeds here, but check your folder name against the name in the cfg. file. If yours is straight from the d\l the names are different. The plane folder reads "A26 Invader_SOH" and the cfg reads "Douglas A-26B Invader (FS9) 3rd Bomb Group, Phillipines 1945.".....They are different. Maybe make them the same and see what happens.....

Hiya Fibber,

Thanks for the input. I'm pretty sure it makes no difference to the sim whether or not the folder name and the title name in the aircraft.cfg file match. I change the AC folder names (add the initials of the creator) and the titles (make sure the title starts with the manufacturer name and model) all the time and it has no adverse effects.

MR
 
Ah yes...one of my favorite conversions. Sorry for the trouble Chris. I noticed that the main panel bitmap is a bit larger than standard 1024x768, something my XP rig has never had any trouble with, although a Win7/Win10 rig might choke on this in CFS2. Its the FS9 original at 2048x1536 (125 dpi). Try resizing the bitmap to 1024x768. If it works you may have to re-position the gauges with an panel editor to fit the new size.
 
Hiya Fibber,

Thanks for the input. I'm pretty sure it makes no difference to the sim whether or not the folder name and the title name in the aircraft.cfg file match. I change the AC folder names (add the initials of the creator) and the titles (make sure the title starts with the manufacturer name and model) all the time and it has no adverse effects.

MR

That is correct Chris....

But to satisfy the curiosity, the " (FS9) " thingy in the title was just an useless leftover marker i used in working on the project. Should have deleted it in the upload but overlooked it.
 
That is correct Chris....

But to satisfy the curiosity, the " (FS9) " thingy in the title was just an useless leftover marker i used in working on the project. Should have deleted it in the upload but overlooked it.

Hiya Bearcat,

I deleted the (FS9) from the ac.cfg file. Still no joy.

But it at least now it is tidied up!

MR
 
Ah yes...one of my favorite conversions. Sorry for the trouble Chris. I noticed that the main panel bitmap is a bit larger than standard 1024x768, something my XP rig has never had any trouble with, although a Win7/Win10 rig might choke on this in CFS2. Its the FS9 original at 2048x1536 (125 dpi). Try resizing the bitmap to 1024x768. If it works you may have to re-position the gauges with an panel editor to fit the new size.

Okay. Will do.

Stand-by....

Nope. Still no joy.

MR
 
Well, there's your clue...you may have to use the resized bmp to create a new, basic panel with entirely different gauges and no auxiliary windows.

Heh heh. Well, maybe. Perhaps someday when I am feeling bit more inclined to do so. ;^)

I will think on it.

Cheers and thanks Bearcat,
MR

PS: BTW, BC, is the 125 dpi a big issue? I just reduced the dpi to 1 and resized the image to 1024x768. Should I then change the dpi back to 125?
 
Is this the same plane this thread is talking about ??
I may have to post an update for win 7 users ?
I also still hang onto and even replace my Win XP computers.


Viet_A26.jpg

A-26 Counter Invader

by Milton Shupe and Crew, converted by Bearcat241 and SOH crew

Includes 2d and VC panel by Bearcat241
a great Dp with multi loadouts
Includes two paint versions
Brief Viet history text file, great sound file

Download ****

http://thefreeflightsite.com/Aircraft_CFS2_8.htm
 
Is this the same plane this thread is talking about ??
I may have to post an update for win 7 users ?
I also still hang onto and even replace my Win XP computers.


Viet_A26.jpg

A-26 Counter Invader

by Milton Shupe and Crew, converted by Bearcat241 and SOH crew

Includes 2d and VC panel by Bearcat241
a great Dp with multi loadouts
Includes two paint versions
Brief Viet history text file, great sound file

Download ****

http://thefreeflightsite.com/Aircraft_CFS2_8.htm

Its one of three listed in the SOH CFS2 library as:

Listed as A-26B_Invader_SOH_with_fix.zip (downloads as A-26B_Invader_SOH.zip)
Listed as A-26C_Invader_SOH_with_update.zip (downloads as A-26C_Invader_SOH_with_update.zip)
Listed as B-26K_Invader_SOH_with_fix.zip (downloads as B-26K_Invader_SOH.zip)

The first one listed, the B model, is the one we are messing around with in this thread.

But I have tried the other two and the same thing happens with them.

MR
 
I put the Bravo on the flight line again for a test on my XP rig and had no issues at all when loading in FF, changing models within FF or changing views and such. I don't have any more clues on this, except as Allen suggested about using a different panel. If the bitmap size isn't the cause then its got to be one of the gauges. Which one is anyone's guess...

Not sure if the dpi matters much. My desktop screen is defaulted to 96 dpi and handles the 2048 ~ 125 dpi bmp just fine in sim.

I can mess around with building a replacement panel for you, just have to find the best gauges to fit the look of the bitmap and hope they work out for you.
 
I put the Bravo on the flight line again for a test on my XP rig and had no issues at all when loading in FF, changing models within FF or changing views and such. I don't have any more clues on this, except as Allen suggested about using a different panel. If the bitmap size isn't the cause then its got to be one of the gauges. Which one is anyone's guess...

Not sure if the dpi matters much. My desktop screen is defaulted to 96 dpi and handles the 2048 ~ 125 dpi bmp just fine in sim.

I can mess around with building a replacement panel for you, just have to find the best gauges to fit the look of the bitmap and hope they work out for you.

Gee Bearcat. I don't feel right about you spending your time making a new panel just on my account.

Whats funny is I am pretty sure that I used to run these ac on my XP rig, too. With no issues at all. I wouldn
t swear to it but I am almost certain.

Did I mention, in case it matters, that I am running everything on my Window 8.1 Pro HP laptop? Screen-res 1920x1080

Unfortunately my old XPPro desktop bit the dust a couple of years ago. I rebuilt everything and got up and running again on this rig which, up until then, had very much been my back-up/travel computer.

My gut on this situation is that some gauge or other is behind it. Guess I could delete groups of gauges until I delete a group that make the problem go away. And then add-back the gauges from that group one by one until I hit on the one that makes the problem come back.

I guess one of the best places to start would be deleting the sub-panels one by one?

We'll see.

Thanks, for the offer to remake the panel. I won't absolutely forbid you to do ;^) so but maybe I should try this trial and error approach first.

Cheers,
MR
 
Last edited:
Try this...i didn't resize the 2D bmp, just stripped down the number of gauges in the 2D and applied common-use stuff i've used in other conversions with no issues.
 

Attachments

  • A26.zip
    4.4 MB · Views: 1
Back
Top