Jump to content

malibu43

+MODDER
  • Content count

    2,242
  • Joined

  • Last visited

  • Days Won

    6

Everything posted by malibu43

  1. FWIW - Here is some info on converstion from B to B+. Don't know how accurate it is. http://rds.yahoo.com/_ylt=A0oGkw0UTkRIilgB...et/avav8_3.html I used this to modify the countermeasure dispensers on my "B" and the B+.
  2. Interesting. I found this article: http://rds.yahoo.com/_ylt=A0oGkkz6S0RIOFAB..._Harrier_II.htm The numbers here, as far as payload for the pylons, matches the load limits in the stock weapons stations for the B+. However, the 454 kg specified for the middle pylons, would only allow 2 MK 82's to be loaded. I have no idea which one is right... Also some intersting info on the AV-8B+: http://rds.yahoo.com/_ylt=A0oGkw0UTkRIilgB...et/avav8_3.html *edit* - this article seems to support 907 kg on both inner and middle pylons. Click 'Characteristics': http://www.aviationphotoalbum.com/ATTACKER...ifications.html
  3. I did check the WOV installation before I added the Falkland mod. It worked fine. I was able to get it to work, though. I changed out eached mod folder with the stock ones, one by one. It ended up being options.ini...? I dropped my options.ini in from my WOV installation and it worked fine after that. I also had to change the terrain pointer to vietnamSEA.CAT instead of the desert one, otherwise the airfields were missing. I haven't had a chance yet to dig into the options.ini to see what the problem was... Now that it works, I must say Bravo! Really awsome work. The A-4 single mission that comes with the package is absolutely awesome. I haven't really had a chance to try the campaigns yet.
  4. OK guys. New problem. I re-did the campaign based on the vietnamSEA target.ini and LBI data.ini posted in the Steel Tiger campaign thread. It was working fine, with offesnsives and CAS missions and all that good stuff. Then, all of a sudden this mornign, I fire up a new campaign for some testing, and I get a CAS mission right off the bat each time, and regardless of the outcome, a peace treaty is signed and campiagn is finished. Tried and A/A mission, and same thing. Campaign finished after one mission. Anyone know why this might happen? Here are the files: Vietnam1985.txt Nam85_new_DATA.txt Obviously these would have to be renamed .ini. Any help would be appreciated! *edit* - I changed normal mission rate to 1 instead of 50, and it works fine now. If the rate is days between missions, and you have a campaign that's only 1 month long, a normal mission rate of 50 will only give you one mission.
  5. I already posted this in the minor bugs thread, but I'd thought I'd post it here too. I installed into a fresh WOV fully patched up. Followed the readme and added the C-130a lods to the C-130a and KC-130a folders. In single mission or campaigns, for either side, I get a crash to desktop after clicking "fly". I'm not sure what to do. Has anyone else been able to get this to work with WOV? Thanks! *edit* - I also added an aircraft from my WOV install and added the WOV terrain and tried a single mission using those. Still got a CTD.
  6. Not really a minor bug, more of a major one. I installed into a fresh WOV fully patched up. Followed the readme and added the C-130a lods to the C-130a and KC-130a folders. In single mission or campaigns, for either side, I get a crash to desktop after clicking "fly". I'm not sure what to do. Has anyone else been able to get this to work with WOV? Thanks! *edit* - I also added an aircraft from my WOV install and added the WOV terrain and tried a single mission using those. Still got a CTD.
  7. I was wondering if it's possible to add more than one nation to an aircraft's data.ini, which would allow the aircraft to use weapons from different countries, without having to change the weapon to exported. For example, I want to be able to load the AGM-65E (USMC nationality, not exported) on my F-18C (USN nationality). I could just change it to exported, or create a USN version of it, but then it could end up being loaded on aircraft that don't actually carry it. I know I'm being kinda picky and hardcore about it, but that's what I like doing in these games. So does anyone know if this is doable?
  8. Hmmm... thanks. Definitely different looking... I'll have to think about it then. While I'm at it though, did the AV-8B's carry AGM-65's, or was it only added to the B+'s?
  9. Hi all, I'm having a couple issues with AGM-65's. The first one is that I can't get the E to show up in the loadout screen. I have ensured that I'm using the correct nation and attachment types, but no matter what, it's never available for me to use. Has anyone else had this issue? Could someone confirm that it does or does not show up? I'm using Bunyaps weps pack. The second issue, is that on the MF F-18 and the new AV-8B, if the maverick specified in the loadout.ini isn't available (for service year reasons), the game is not automatically loading the closest available weapon. Say if I have an A specified in the loadout.ini, but run a mission in the mid 90's, the D is available in the loadout screen, but the game has not attempted to load that weapon on my plane for me. I checked with the stock WOE A-10, and the game automatically chooses the correct AGM-65 for the date, even if it's not the one specified in the loadout.ini. Does anyone know why this would happen with these add-on aircraft? Thanks!
  10. Thanks for the help, Dave. Also, FWIW, the AGM-65E issue was that its a laser guided rocket (LGR), not an EOGR. Added that to allowable weapon class, and that straightened it out.
  11. I guess that makes sense. I don't have a huge problem loading the weps myself. Just wanted to understand what the game is doing... Thanks.
  12. I think you must have misunderstood what I was asking about, or maybe I didn't explain it well. I realize that the USMC is part of the navy and that USMC is not an attachment type. I knew that USN was the attachment type I wanted. The real issue I was toying with was could I get an aircraft to have multiple nationalities assigned instead of having the desired weapon specified as exported. Doing this would allow a change to be made to just one aircraft (and it would affect that aircraft's loadout only) instead of changing a weapon, which could have an effect on every aircraft that does/could use that weapon. In this case I was trying to get a non-exported USMC weapon on a USN plane, and I was expertimenting with different ways of getting that to happen. So maybe a better example of what I'm trying to avoid, would be if you wanted to put a "non-exported" USAF weapon on a USN nationality plane. You only want it to be available on this one specific USN plane in addition to USAF aircraft. You would have to add USAF to the allowable attachment types for the USN plane, but then you will also have to change the weapon to exported. USAF is a very common attachment type in this game, so in addition to the weapon now being available on the USN plane (which you wanted), it would now also be available to every aircraft (in the applicalbe service years) that have USAF as an attachment type as well. If you know just not to use it on the aircraft that shouldn't, that's fine, but I like to rely on the loadout screen to tell me what I can or can't do, and not have to remember all the time. I don't know if I explained that well. Anyway, thanks for the input, and for answering the question about multiple nationalities. For the case of the F-18 and AGM-65E, I'm just going to change the weapon to exported. Thanks!
  13. The attachment types for weapon and weapon station already match up (both USN). What I recently disovered, however, was that the nation names for the aircraft and weapon either have to match, or the weapon has to be exported. So, for example, a weapon with USAF and USN as attachment types and USMC with the nation name, will only be usable on USMC aircraft with either USAF or USN as attachment types. If the weapon is exported, it will be usable on any aircraft with either USN or USAF as attachment types. Although what I just realized is that in my specific case, it may be doable just to change the AGM-65E to exported, since the only attachment type for that weapon is USN, and not many aircraft other than USN aircraft have that attachment type. So my chances of getting screwy loadouts is pretty slim. I may try the muliple nations thing anyway, just since it would be cool to know if it works.
  14. That's way cool Where did you get it?
  15. Thanks! Very helpful stuff!
  16. Thanks. Do you happen to know about TER's on the AV-8B? I haven't seen one that actually used them. Would they be used on both pylons, or just the inner?
  17. While we're on the subject of the loadouts, does anyone know if/when/how often TER's are/could be used on the inboard and middle pylon's for dumb bombs. Also are TLR (LAU-88) ever actually used for mavericks? None of the pictures or literature I've been able to find has shown either TER or TLR's being used at all... Thanks!
  18. The reason the mavericks won't show up on the default loadouts, could be that the maverick called out is the "D". The nation for this weapon is USAF, and AV-8B's nation is the USMC. This means the weapon will have to be "exported" for the AV-8B to use it. However, the "D" isn't exported until 1996, so if you try a mission in 94 or 95 with the default CAS loadout, the D's won't be there. The game should look to the next available maverick, but for some reason on mine, it wasn't doing it. Change the D's to E's in the loadout.ini, and hopefully they'll show up (The E's are available throughout the entire life of the AV-8B and are USMC nationality). I haven't had a chance to try this yet, since I'm traveling for the week, but maybe someone else can give it a try and report back? Similarly, for the GBU-12D's to be able to be loaded, USAF needs to be added as an allowable attachment type, and the weapon needs to be changed to exported. Or, the attachment types can be left alone and the GBU-12D_N (navy version and attachment type) needs to be changed to exported. Either way, the loadout.ini needs to have either GBU-12D or GBU-12D_N. The GBU-12 that's listed in the loadout.ini has a service end year date of 1976 or something. Also, to get the Lightning Pod to show up on the right wing station, it will have to be changed to exported. I think this is right anyway, since lots of countries use it. I should say that I'm using Bunyaps' weps pack, and that's what I'm basing all this on. Once I get a chance to test these loadout changes, I can post them if you like.
  19. Looks great! Once we have the C-130.lod, what are we supposed to do with it? Where does it go and how should it be named? Thanks!
  20. I'm working on a mid 90's campaign in Isreal (to use the new AV-8B!) and am looking to add a carrier station. I can copy stuff from the Vietnam yankee station stuff in the targets.ini to get most of it, but was wondering if someone could provide me the position values for a possible carrier station? I know nothing about terrain editing or how to determine what the positioning should be... Thanks!
  21. Couldn't find any carrier stations in the original, but I did find your update and was able to grab the carrier stations out of that. Thanks! Thanks!
  22. I've tried everything I can think of, but the only GBU's that will show up in the loadout screen for the AV-8B+ are the 16 and 123. Needless to say, they aren't showing up if I leave the default Strike loadout set either. To double check, I tried a mission in the same year with the stock WOE A-10, and was able to load the GBU-12D/B just fine. Changed the aircraft to the B+, and there was no GBU-12 available. The attachment types and mass limits seem fine. I'm using a merged WOV/WOE with lots of mods and Bunyaps weps pack. But seeing as the GBU-12 will show up on other aircraft, I don't get why it wouldn't show up for only the B+. Any suggestions? *edit* - figured it out. The nation is listed as USAF for the GBU-12D, and exported is not checked. The nation for the AV-8B+ is USMC, so it won't ever be able to be loaded. I changed the GBU-12D to exported (shouldn't have a big effect since the attachment type still has to be USAF), and it works now. However, I did also discover that the SEAD loadout has 3 rockeyes on each of the #2 wing pylons. However the load limit for these stations is set too low to allow 3 rockeyes. I'm not an AV-8B expert, so I don't know if 2 rockeyes is more accurate and the weight limit is correct, or if the load limit should be increased. Anyone know what would be correct? Maybe we should add the AV-8B+ to the KB loadout fixes...?
  23. Interesting. I thought I remember reading that targeting pods couldn't be fitted to the centerline. Maybe this isn't correct though...?
  24. In all pics I've seen, the LANTIRN pod would be hanging where you have the fuel tank. Also, FWIW, you can use the LGB's on a strke mission without the targeting pod, since primary strike targets in Thirdwire games are always being "lazed" by "special forces". But if you want to use LGB's in SEAD or CAS, then yes, you would have to load a designator pod. But if anyone has any input on my orginal (well... second) question about the Rockeye loadouts and load limits for the #2 pylons, it would be much appreciated!
×

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