rmk80

This does not work, you need to set MSAA in game

Yes, that's it! All working now. Can't wait to try it out this evening. Thanks for all your efforts, really appreciated :thumbup: Will you be making PG and NTTR versions as well?

Yes, it is in DCE folder, see the screenshot.

Hi Miguel, see attached my file structure. I feel like I'm maybe missing some files, that define the entry in the list under campaigns? Just guessing

No, I’m not seeing that (was expecting this as you explained in the manual). I’m sure I’m on 2.5.5 Stable. Wondering if anyone else is having issues having the mod show up?

Nice man, I'm going to try it right away, thx! EDIT: The manual says: You will find the campaign you installed in the DCS Campaigns part looking for a DCE folder (not the plane folder you will fly) after reading the general then the mission briefing you will fly ! (See the How to play section below if you never played a DCE campaign before ) However I'm not seeing the the DCE folder or any of the campaigns. The only way to start the mission is to navigate to the right folder in the missions section and choose the first mission. Am I doing something wrong? Also I noticed the TF-74-Hornet.cmp file has 2 absolute paths that are different from mine. Do they not require to be edited?

I believe tools like OTT actually make use of the same interface or API to set different modes. I made a voiceattack profile to be able to switch modes during a game with a simple voice command. This works in all other games as well, not only DCS. Using the CLI you can also show the performance overlay showing you framerate graph etc. I can even set the pixel density using a voice command, however this not work for DCS during a game. In other games this does work. If you’re interrsted I’d be happy to share the profile.

I’m on a 2070 RTX and run MSAA x2 and PD 1.2. Setting PD to 1.4 results in too many drops below 40 fps and losing the the MSAA is too much degrading in image quality. Nota that I almost exclusively fly in SP.

You can set different ASW modes using the OculusDebugToolCLI.exe in your Oculus\Support\oculus-diagnostics folder. The following additional modes are available: asw.Auto - Enables auto ASW operation // This is actually the default mode asw.Clock18 - Simulates an extrapolated 18 Hz display asw.Clock30 - Simulates an extrapolated 30 Hz display asw.Clock45 - Simulates an extrapolated 45 Hz display (Clock45) asw.Off - Disables any ASW operation asw.Phase45 - Simulates an extrapolated broken 45 Hz display (Phase45) asw.Sim45 - Simulates app 45 Hz rendering (Force45fps) Especially the asw.Clock30 (ASW On 30 fps) mode might be useful for systems that are not able to maintain 45 fps (40 fps for Rift S) but need smooth gameplay (e.g. flight sims). Only downside is you will get ghosting on cockpit edges with fast head movements, so YMMV. Modes can be switched by entering 'server:asw.clock30' in the command line interface. I actually made a Voiceattack profile allowing me to switch models on the fly. Note that these values are for the Rift. On the Rift S setting ASW to clock30 effectively results in a 27 fps frame limit.

Hey man, thanks for your great feedback. I'm not using DCS beta myself, so I currently can not test it. I'm using MOOSE functions to spawn all aircraft, so maybe there is a incompatibility with the latest beta update. I think I'll wait for the next stable update to see if this is indeed still a problem

Posted new versions. See the first post for changes. Thank you for your feedback :thumbup:. Latest version registers a player death as a loss of aircraft. Adding helo's sounds cool. I need to see how I could add these. Glad to hear it works in COOP as well. I actually tried to change the thread title but it doesn't change :(

1) Not yet. You can select the SEAD flight on the F10 map and enable 'show waypoint' option. It will show you the route and waypoints the SEAD flight is flying. I need to think how I could build such a request in the menu structure. 2) Great idea! This I can implement quite easy. Will put this on the ToDo list. 3) No. The mission is designed to be very flexible. There are 2 things you can adjust in the mission editor to customize the battlefield. First you can assign airports to RED or BLUE in the mission editor to your liking. Second you need to adjust the two (hidden) helicopter groups that define the CAP zones for RED and BLUE. Simply dragging/adding/removing waypoints to the 2 helicopter groups will define the CAP zones in which CAP flights will patrol. Note that you do need to reset the mission (remove save files from DCS root) to make this work. Otherwise BLUE flights will spawn at airbases that might have RED defense units.

Great, let me know if you notice anything unusual. Also added a Nevada version

Ok, you can now try the Georgian Power version. It is based on latest version. Note that I haven't play/tested it myself yet.

Posted the new version with updated MOOSE version.

Yes, I read something about it. Thanks for pointing this out. Explains why I have been flying like an ace :megalol: Will swap the MOOSE version in the new version!

Obviously the scripts are loaded otherwise you would not see the intro messages and the tanker/awacs take off. You should always see a AI flight being dispatched within 30 seonds to 5 minutes from mission start. I have no clue what could cause this problem, I have not seen this behaviour yet. Do you have the same problem if you load the mission through single player without editing anything? Could you run the mission for 5 minutes, shutdown and post your log file?

It is actually pretty easy to do. I already did a quick port to Nevada which is working fine. I'm almost done optimizing some of the Persian Power scripts, which I will release soon. After that I will port it to Caucasus. I'll try to do it this week. Maybe you can come up with some fancy name already :megalol:

Thank you all for your feedback. I added the Viggen as well as the Harrier.

Glad you sorted it out. I hope you enjoy the mission! New version is up!

This hints you did not correctly comment out the lines in missionscripting.lua as explained on the first post. Could you verify this step?

Are you 100% sure you edited the MissionScripting.lua file in your DCS World\Scripts folder? Otherwise the script hangs at looking for a save file, which it can't find because it doesn't have permission to read files.

Thanks for the feedback. I'm currently testing a version that has rearm vehicles for all anti-air units

No not yet, its on the todo list

Uploaded a new version. See the first post for the changes. Yes, custom cleanup script has been added. You can set the time cleanup interval in mission settings. Also added a despawnType option (for immersion)