Jump to content

Recommended Posts

I am very sorry, but ....

I must now (again) ask for some more help and guidance with a problem, from any of the Members of this Forum with more experience and expertise, who care to respond ...

 

I am trying to use the A -Team's "B-26 Marauder" in my WW2 SFP1 installation.

Every time I do (whether as a Player-flyable craft, or as strictly AI, or even if it's folder just sits in "\Aircraft" and is never called for in a mission), I consistently get "SFP1 has stopped working and needs to close. Do you want to notify Microsoft about this?" error messages.

 

http://i1219.photobucket.com/albums/dd424/DARoot1/Miscellaneous/B26ERROR.jpg

 

Same thing happens with their "B-26b" and "B-26a ('Marauder,' in RAF livery)" models;

Same deal, tested in my PTO install, my ETO install, and my Korea install of SFP1.

 

Anybody else encountered this?

Anybody have any ideas why?

Any "easy fixes" available (that don't involve hexediting the .lods)?

 

If this helps, here is what I'm currently using --

SFP1, patched to v.8.30.6.9;

"Nations.ini" dated 12/16/2006, "Formation.ini" dated 4/10/2005, and "MissionControl.ini" dated 12/10/2006 (all from the "EuroWW2" Terrain Mod -- the most recent I could find. My PTO install includes "hybrids" of these, embodying more recent changes by Wrench and Baltika, that only affect Imperial Japanese forces...);

Windows XP, Svc Pack 3

Norton 360 Spyware/Antivirus

 

Any ideas, assistance, or encouragement will be MOST appreciated!

[i really like the B-26]...

 

DARoot

Share this post


Link to post
Share on other sites

Ask @ A-Team side.

 

What he said!

Share this post


Link to post
Share on other sites

MinBaseSize=LARGE < -------------- Change to MEDIUM or SMALL, For PTO/CBI/KAW major cause of CTD

Share this post


Link to post
Share on other sites

Appreciate the responses, but ....

Exerpt from my current "B-26B_Data.ini" --

 

PrimaryRoles=STRIKE,ANTI_SHIP

SecondaryRoles=CAS,ARMED_RECON,RECON

NormalMissionRadius=1485

MaxMissionRadius=1750

Ceiling=6615

MinBaseSize=SMALL

CarrierBased=FALSE

 

Still no joy ....

 

I even tried opening the "Data.ini" file in Notepad, saving it as a text file (in ANSI format) and re-naming it "B-26B_Data.ini" (because of some off-the-wall sidenote in one of the A-Team's other downloads, about possible CTDs if using THAT model in WOV or WOI). Who'd a thunk it?

 

Didn't help. Still getting errors ....

 

And yes, I could ask the A-Team directly, but the people here are so much nicer ....

 

DARoot

Share this post


Link to post
Share on other sites

But all their stuff is Free! (kinda,sort of ,maybe):blink:

Edited by RAVEN

Share this post


Link to post
Share on other sites

actually, that's Veltro's Marauder. They're just hosting it

Edited by Wrench

Share this post


Link to post
Share on other sites

We Have Liftoff :drinks: Comment out the "//CarrierBased=FALSE"

 

Raven

Share this post


Link to post
Share on other sites

Oh, this is just too much, really ...

 

Comment out the "CarrierBased=FALSE" line???

 

This sim is just too weird .. but, I'll try anything.

Thank you, Raven!

 

DARoot

Share this post


Link to post
Share on other sites

I just went over the B-26 And got some strange Rendering with the SF1 Game engine. I just checked the OUT. files and (DrumRoll) The Node Hierarchy dose not match from Lod =B-26 to Lod= B-2601 So comment out the entries for the second lod.

 

CockpitDataFile=B-26_cockpit.ini

 

[LOD001]

Filename=B-26.LOD

Distance=100

 

[LOD002]

Filename=B-26.LOD

Distance=250

 

[LOD003]

Filename=B-26.LOD

Distance=8000

 

[shadow]

CastShadow=FALSE

ShadowLOD=

ShadowType=1

 

Photos are Before And After

Raven

post-300-0-52527800-1341980593.jpg

post-300-0-69816900-1341980606.jpg

Share this post


Link to post
Share on other sites

Oh, now, really ---

Thank You,Raven, for trying to track down and squash what has (obviously) been a "bug" in that model since it's inception!!

[Forgive me, but several 3rd-parties have released alternate "skins" for that B-26 model over the years -- I simply cannot BELIEVE that the thing worked on their systems (but, unfortunately, not mine), until you, RAVEN, pointed out (what I consider to be) a VERY BASIC fault in it's construction/release version...

Thank You again!!!

 

[And, yeah, CAPUN, you can castigate me as much as you wish, for posting this, as it pleases you ...]

 

DARoot

  • Dislike 1

Share this post


Link to post
Share on other sites

Hooray for Raven!

I now have B-26b bombers to fly, in both my SFP1 PTO and ETO installations!!!

[With nary a CTD/Error Message, I might add ...]

B-26B.jpg

Many thanks, my friend ...

Thank You, and Thank You again

[This B-26 thing has been driving me NUTS for the past month, or so ...]

 

DARoot

Edited by DARoot
  • Dislike 1

Share this post


Link to post
Share on other sites

Sorry to do this (it isn't like me, really, but....)

The extreme hot weather hereabouts seems to have got my dandruff up, so I'll post this anyway....

That B-26 model has been out, and available for download, since about October 2011 (at least, that's the filedate on the one I downloaded).

Several folks have posted "reskins" for the thing (meaning, it must have worked for THEM, at some time back when).

So, Why does some jerk, like me, have to post a question,

And Why does some accomplished modder like RAVEN, have to devote time and effort to research, and post a response, to "fix" it, in July 2012?

[Mr. Rogers Voice -- "Can you say 'Quality Control?' Oh, I think you can..."]

:heat:

DARoot

  • Dislike 1

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×

Important Information

By using this site, you agree to our Terms of Use, Privacy Policy, and We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue..