Jump to content

TheStig

ENTHUSIAST
  • Posts

    370
  • Joined

  • Last visited

About TheStig

Recent Profile Visitors

6,487 profile views

TheStig's Achievements

Rookie

Rookie (2/14)

  • First Post Rare
  • Collaborator Rare
  • Conversation Starter Rare
  • Dedicated Rare
  • Week One Done Rare

Recent Badges

47

Reputation

  1. I'm using IRM as one of 2 versions, one for air, and the other is going to be an EOGR. I only know of LGB when it comes to laser. By the way I figured it out for the IRM. The problem was related to the specific station code not lining up.
  2. Hey guys, I'm working on an APWKS for SF2 but I seem to be running into a stop. I'm using the Mk4_MightMouse I changed from RCKT to IRM. I first tried to test it on the F-86D Sabre dog but the weapon completely disappeared. I then played with the allowed weapon class, changing it from RCKT to IRM but with no success. As part of my test, how would I get it to show with IRM characteristics? Here is how the rocket tray looks right now. Note I can swap out the lines with forward slashes if needed: [RocketTray2] SystemType=WEAPON_STATION StationID=1 StationGroupID=1 StationType=INTERNAL NumWeapons=24 AttachmentPosition024=-0.394,1.473,-0.461 AttachmentPosition023=0.391,1.473,-0.461 AttachmentPosition022=-0.391,1.473,-0.529 AttachmentPosition021=0.391,1.473,-0.529 AttachmentPosition020=-0.322,1.473,-0.467 AttachmentPosition019=0.322,1.473,-0.467 AttachmentPosition018=-0.322,1.473,-0.536 AttachmentPosition017=0.322,1.473, -0.536 AttachmentPosition016=-0.251,1.473,-0.475 AttachmentPosition015=0.251,1.473,-0.475 AttachmentPosition014=-0.251,1.473,-0.543 AttachmentPosition013=0.251,1.473,-0.543 AttachmentPosition012=-0.181,1.473,-0.481 AttachmentPosition011=0.181,1.473,-0.481 AttachmentPosition010=-0.181,1.473,-0.549 AttachmentPosition009=0.181,1.473,-0.549 AttachmentPosition008=-0.109,1.473,-0.484 AttachmentPosition007=0.109,1.473,-0.484 AttachmentPosition006=-0.109,1.473,-0.553 AttachmentPosition005=0.109,1.473,-0.553 AttachmentPosition004=-0.038,1.473,-0.492 AttachmentPosition003=0.038,1.473,-0.492 AttachmentPosition002=-0.038,1.473,-0.562 AttachmentPosition001=0.038,1.473,-0.562 AttachmentAngles=0.0,0.0,0.0 LoadLimit=1700.0 //AllowedWeaponClass=IRM AllowedWeaponClass=RCKT AttachmentType=USAF DiameterLimit=0.5 LengthLimit=3.2 BombBayAnimationID=10 BombBayOpenTime=.5 BombBayCloseTime=.9 MovingPylon=TRUE ModelNodeName=Rocket_Tray AutomaticDoors=TRUE SpecificStationCode=MMR
  3. This works thanks! Where did you get your Iowa? I am using the Iowa80s version but the 16 inch guns aren't firing even after the update.
  4. I'm working on a single mission for Leyte Gulf (basically the Battle off Samar). I've managed to get destroyers to shoot at IJN warships but not vice versa. Also when the destroyers fire their 5 inch guns, they fall significantly short of the ship. How do I fix this, and get the IJN ships to fire back? Thanks!
  5. Guys I figured 50% of this issue out. I changed ship classes to Battleship from Cruiser. The strike single missions that auto generate are now pointing to land based targets but single mission editor still crashes when selecting the flight to change the target. Only on this map does the CTD occur.
  6. Hi, I'm getting a crash to desktop when using the single mission editor. If I select the player flight, no matter what, it immediately crashes. What would cause this? The terrain is Formosa WW2. When automatically generating a single mission, it only targets a single ship too that appears to be underway on land! Thanks in advance.
  7. I basically just grabbed a ship names ini from another download and populated accordingly for all carrier numbers and names. Even put the dates in when they were sunk (St. Lo off Samar due to IJN pilot rage quitting his miserable life)
  8. Found the issue. An INI file for ship names must be present for them to show in single mission. I created it for the CVEs and now there's so many missions starting with CVEs I had to dial down the availability. Thanks for everyone's responses.
  9. Yes definitely marked true for naval map. In using the Leyte Gulf terrain, all other carriers (Essex and Independence class) show. Casablanca class carriers from the Rising Sun pack do not. I downloaded everything again last night from YAP for Phase 2. I added the lines above to the data INI, changed the availability to VERY_COMMON and no luck. [MissionData] NationName=USN ServiceStartYear=1942 ServiceEndYear=1945 GroundObjectRole=WARSHIP Availability=VERY_COMMON FormationSizeBase=1 FormationSizeVariation=0 Exported=FALSE WarshipClass=AIRCRAFT_CARRIER CarrierBaseSize=SMALL CarrierNumSquadrons=2
  10. Going to try adding this and see if it makes a difference: WarshipClass=AIRCRAFT_CARRIER CarrierBaseSize=MEDIUM CarrierNumSquadrons=6
  11. Hey guys, I download Rising Sun several years ago for my full merged SF2. I never got the chance to install it until now. Unfortunately, the YAP carriers, using Lexington as an example do not work in single missions. I checked the data ini and noticed there is no string showing TRUE for an aircraft carrier. Is this the reason why?
  12. What's a good Terrain Editor out there so I can take a stab at it?
  13. Okay good to know. I can use mission editor to remediate but it just gets annoying after a while.
×
×
  • Create New...

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