YAP Rising Sun version 2 Carriers not working

[TheStig]

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?

[Flanker562]

Wow... Maybe the YAP-RW team has fixed that with their downloads...

[DoctorQuest]

It might work better to contact the YAP-RW team via their Facebook page. I got this from the installation instructions.

"If you are experiencing issues, feel free to contact us. The best place is Facebook: YAP_Revamp_Works"

[daddyairplanes]

ditto on contact on FB

but will also say, did you experiment and try adding said line? copy and paste from a working mod install (say ODS30AE or Crisis in the Med)

[DoctorQuest]

And............just curious. What exactly isn't working? 

[swambast]

3 hours ago, DoctorQuest said:

It might work better to contact the YAP-RW team via their Facebook page. I got this from the installation instructions.

"If you are experiencing issues, feel free to contact us. The best place is Facebook: YAP_Revamp_Works"

Uh yeah, LOL...this!

[TheStig]

Going to try adding this and see if it makes a difference:

 

WarshipClass=AIRCRAFT_CARRIER

CarrierBaseSize=MEDIUM
CarrierNumSquadrons=6

[Wrench]

It's not the vehicle --- have you looked at (or into) the terrain you're using??? Does it have NavalMap=TRUE in it's ini? Does it have the correct _water.bmp with the properly colored "CV Zones"?? Otherwise, single missions with carriers ain't gonna happen.

[TheStig]

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

Edited Friday at 03:01 PM by TheStig

[TheStig]

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.

[DoctorQuest]

Thanks for the update. What specific INI did you update?

[TheStig]

4 hours ago, DoctorQuest said:

Thanks for the update. What specific INI did you update?

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)

[Wrench]

I did that for the CVEs that have been here at CA in 2012. I know it's not for RS, but you MIGHT want to check our downloads section for things you can use. I should know . . . 

[DoctorQuest]

I[GroundObjectData]
ObjectName=Colossus
ObjectFullName=Colossus Class CVL
ObjectDataFile=Colossus_data.ini
Names=Colossus_Names.ini                   <========= is this what you guys are referring to?

Edited yesterday at 03:46 AM by DoctorQuest

[TheStig]

11 hours ago, DoctorQuest said:

1 hour ago, DoctorQuest said:

I[GroundObjectData]
ObjectName=Colossus
ObjectFullName=Colossus Class CVL
ObjectDataFile=Colossus_data.ini
Names=Colossus_Names.ini                   <========= is this what you guys are referring to?

Yep

 

[DoctorQuest]

Thanks! It is good to learn something new every day. This could be useful for a campaign I'm playing around with.