KJakker

Sorry I am a bit later than planed in replying. Yes the it works fine in the Anatolia v2 Terrain, see the screenshot below. However I am having an issue with getting and updated to SF2:NA standards MM38 Exocet working the way it should. Once that is solved I will put the necessary components to update the "ARA Intrepida modernizada con MM-38 Exocet". I might even consider making the update package my first submitted download file. Will have to look up how to properly build a "Readme" file and give credit first.

Acesfakia, I have the "ARA Intrepid modernized with MM-38 Exocet" running in SF2:NA. However I still need to do some fine-tuning. Here are some screenshots while you wait.

If you want I can convert the ship over to SF2:NA format. Just give me a day for some testing.

Glad to here that. You might need to go in and adjust the "GunTypeName=" of [Gun1] and [Gun1] for them to work. I have them set to use "127MM_Mk45_C" which is a contact fused version of the Long Beach's stock "127MM_Mk45" the I created.

I have attached the version of the CGN-9 data ini file that I use. It does have some edits in it. CGN-9_DATA.7z

I have attached the RIM-8 that I use with SF2:NA. The USS Long Beach I have launches it without issue. RIM-8.7z

Go to your profile and look in "My Settings", then select "Manage Attachments". That should show you how much space you have for attachments and how it is allocated.

Snailman, you might want to try changing [AvionicsData] to [RadarData] and see what happens. I have noticed that some aircraft are set up that way in their Avionics.ini files. For example the Tornado F3 from NF5. See how the first part of the Tornado_F3_AVIONICS.ini file appears below. I do not know if it will have any effect but it might not hurt to try. [TextureData] RadarTexture=cockpit\Radar\F3_radar.bmp RWRTexture=cockpit\rwr.bmp RadarTextureSize=256 [RadarData] AvailableModes=SEARCH,TWS,STT,ACM RangeUnit=NM RangeSetting[1]=10 RangeSetting[2]=20 RangeSetting[3]=40 RangeSetting[4]=80 RangeSetting[5]=160 RadarPosition= MaxElevationAngle=60 MinElevationAngle=-60 MaxAzimuthAngle=120 MinAltitude=40.0 BoresightElevation=-2.0 BoresightAzimuth=0.0 MinReturn=0.01 MinimumSpeed=25.41 SearchRange=160 SearchStrength=200 TrackRange=160 TrackStrength=150 TWSUpdateTime=0.5 AcquisitionSymbolSpeed=1.0 AcquisitionresetPosX=0.5 AcquisitionresetPosY=0.20 AcquisitionresetTime=5.0 DisplayLimitLeft=29 DisplayLimitRight=226 DisplayLimitTop=29 DisplayLimitBottom=226

Wrench I have a question. The Gunval Sabers were, as I understand it, modified F-86F's. So why did you decide not to use the new cockpit used by the F-86F from the KAW F-86 Sabre Pack for the GunVal Sabers?

Snailman, do you have the CVN Ulyanovsk 1.0 or the CVN Ulyanovsk 2.0? The 1.0 version had an issue that caused CTD upon mission loading. Try this, start the game, go to Options, select Graphics, change the graphics option to Custom, then set Object Detail to Low. Once that is done try running a mission with the Ulyanovsk in and see if there is a difference.

I read about this in, I think it was Air & Space magazine, a few years ago.

Did I hear the voice of GLaDOS from Portal in that trailer?

I wanted to say that the new Sabers are wonderful. The new cockpit is a beautiful update over the old SF-1 based A-4 mod and the alignment of the guns to the gun sight is the best I can recall ever seeing in all my playing of SF2. If you have the Saber steady the bullets go right through the center of your piper.

All of those vehicles look great. I just had an image in my mind of the MLRS counter battery firing on your Type 053H1S frigates.

It was my understanding that their was no Mobile_SAM role and that mobile SAMs had to use the Mobile_AAA role.

I did not realize that WoV was different from SF1 & WoE with regard to Intercept missions. Something new to remember.

Odd, I thought it would. Take a look at this. http://combatace.com/index.php/topic/12103-basic-ini-editing-mission-data/ Also it looks like you overwrote the [WeatherChance] lines in the file. You might want to delete that file and re-extract it.

Copy and past the entry below into the the VietnamSEA.ini file. [AllowedMissionTypes] FriendlyMissionTypes=SWEEP,ESCORT,STRIKE,SEAD,ARMED_RECON,RECON,ANTI_SHIP EnemyMissionTypes=SWEEP,CAP,ESCORT,RECON,ANTI_SHIP Then add INTERCEPT to the "FriendlyMissionTypes" line followed by, as specified above, to the aircraft you want to fly intercept in and then see if it works.

In the data.ini file for each aircraft under [MissionData] is the entry called "PrimaryRoles=" just add the word "INTERCEPT" to the roles listed and you should be fly intercept missions.

Is it just me or does the launch of that J-15 in the video just look wrong due to the lack of sudden catapult acceleration?

What aircraft are you trying to get this to work for? Also take a look at the stock TW Lightning's rocket packs.

The what-if Screenshot thread is located here. http://combatace.com.../page__st__1140

I just did a test and found that if I gave the time fused guns 1000 times the busting charge of their contact fused counterparts they became effective. I am going to do some more testing and then put together a new ships gun pack.

Eric, that is interesting. In testing I have had flights of A-4's fly over formations of up to 12 of the General Belgrano for a total of 288 40MM_L60's, 96 5inch 5IN_MK12, and for test purposes, 180 6inch guns all set up as though they were the 6in Mk16's like the Worcester Class used, all time fused. Despite all that I found that after flying through a veritable wall of flak burst not one of the A-4's had even a scratch visible on it let alone got shot down. Would you be interested in helping me in figuring out what went wrong?

I would recommend that you try and use only contact fused guns as the shell burst from the time fused guns as far as I am aware do not model fragmentation from the shell burst.