Jump to content
Sign in to follow this  
maverickvf142

Stock A-10 SEAD Loadout Error?

Recommended Posts

Hi all,

 

I recently got the urge to fly some A-10 missions with the stock aircraft and was having fun until I decided to try a SEAD mission. The default loadout seems to have an error where the CBU-24B's are on loaded on pylons that aren't cleared to carry the CBU-24B. I never noticed this before and was wondering if this is "normal" or if I had messed up with my install. I have it patched to the latest version (Jul 2013) and a hotfix patch installed from here.  I've attached an image of what I'm seeing in the loadout screen. 

 

 

Thanks 

post-79682-0-21070300-1463173142_thumb.jpg

Share this post


Link to post
Share on other sites

well, as the CBU is a bomb, it's loadable to any pylon with the "BOMB" in it's attachment type

I wouldn't worry about it

Share this post


Link to post
Share on other sites

Well, after looking at the A-10's data file, it seems like the reason the default loadout isn't working is because TK limited the max weight to 380 and thus preventing the CBU-24's from showing up. It seems that the A-10 didn't carry CBU's under those stations in reality anyways and the problem I'm having is more of the weapons being assigned to the wrong station. 

 

Not sure if it's just me though since I don't recall having this problem before... can anyone tell me if they're experiencing the same thing before I reinstall everything again? If you guys aren't, I will probably reinstall the whole nine yards after removing everything to make sure it works properly.  

 

Thanks

Share this post


Link to post
Share on other sites

Well, I installed SF2:E on another computer just now which is patched to September 2011 and it's still showing the same error. What I'll do is just create a loadout.ini file and correct the error. Thanks Wrench for putting my mind to ease about this.

Share this post


Link to post
Share on other sites

why not just extract the data and loadout inis from the cat, put them in the Hawgs folder, and edit from there??

 

no need to triple the workload by re-creating mods folders when simple ini edits will fix the problem

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
Sign in to follow this  

×

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..