unknown

VR. Controllers are not working correctly in open beta - fixed. Thank you very much ED to bring back the laser pointer in VR, so much appreciated!

Thank you very much

If you set up an ai ground unit with the "go to waypoint" advanced waypoint setting the ai unit is not moving like expected. I was hoping that you can set up units to patrol a street with this instead of using dozens of waypoints but the ai unit ignores the setting "road" and is using the shortes path back. ai_ground_unit_go_to_waypoint.trk

Thanks, flying in VR is a game changer for Helicopter flying and AirAirRefueling in Jets, it makes all these things so much easier.

+1 After the 2.7 update the Syria map became my number 1 map. Thanks Ugra Media!

The lights at Gaziantep AF are floating in the air. Screenshot and mission for quick reference attached. Gaziantep_lights.miz

Ok thanks. Any idea why these files are not deleted with an DCS update or atleast after running an repair? Or marked after running the repair as additional files with the option to delete them like my audio files for the JF-17 MP3 player?

I'm running that driver with my 1080ti and VR and had no problems so far(2.5h mission and couple other flights over und under 1h)

I checked the weather settings of most of the quickstart missions for the F-14 today by opening them in the MissionEditor. I encountered a problem trying to open the following two missions: - F-14B_IA_Caucasus_Dance_of_the_Vampires - F-14B_IA_PG_tour If i try to open them DCS shows me the loading screen, loading bar moves but stops at some point and nothing is happening. If i "alt+tab" to windows and right click the DCS icon in my task bar -> click on close DCS opens a window asking me if i'm sure to exit -> clicking yes but nothing happens. I have to close DCS via the taskmanager. I tried this a couple of times, also waited for minutes but the mission was never loaded in the ME. Attached are both missions copyed from the C:\DCS World OpenBeta\Mods\aircraft\F14\Missions\QuickStart filepath + the log files(6 total). Only the Log "dcs - Kopie (4)" has additional entries at the end "DCS Device unplugged" -> i didn't unplug anything nor did i here a windows sound played. I don't use any mods, did delete fxo/metashader2 folder and run a DCS repair for file checking after updating to 2.7 dcs - Kopie (2).log dcs - Kopie (3).log dcs - Kopie (4).log dcs - Kopie (5).log dcs - Kopie (6).log dcs - Kopie (7).log F-14B_IA_Caucasus_Dance_of_the_Vampires.miz F-14B_IA_PG_tour.miz

Do you have some quick start example missions for that? I checked most of them and "noon, june, no wind" is set to maybe a handfull(NTTR + flanker 1vs1 on caucasus) missions of the 84 quick start missions for the F-14A and B. Most of the missions have different time(morning/afternoon/evening), month and wind setting.

I used the mission you posted in your first post to run a test again. 1. mission load - start circle above the ground unit battle zone(AP+altitude hold) - fps at start 90+ - after couple minutes fps 80-100fps - at first battles 70-90fps - at "heyvy-part"(~13-16minutes into the mission) 60-70fps up to 90 if nose of JF-17 is looking away from combat - but some dips to 55fps for a very short(explosions, AAA, flares) time with jumps back to 70+ - at ~17min+ into the mission fps go back to 80-90+ - esc -> quit -> exit DCS via main menu 2. mission load(essentially the same as 1. mission load) - start circle above the ground unit battle zone(AP+altitude hold) - fps at start 90+ - after couple minutes fps 80-100fps - at first battles 70-90fps - at "heyvy-part"(~13-16minutes into the mission) 60-70fps up to 90 if nose of JF-17 is looking away from combat - but some dips to 55fps for a very short time with jumps back to 70+ - esc -> quit to desktop(not via main menu) 3. mission load(looks like average fps is a little lower ~2-5fps) - start circle above the ground unit battle zone(AP+altitude hold) - fps at start 85+ - after couple minutes fps 70-90fps - at first battles 70-80fps - at "heyvy-part"(~13-16minutes into the mission) 60-70fps up to 90 if nose of JF-17 is looking away from combat - but some dips to 50fps for a very short time with jumps back to 60-80+ - end test I can see very short dips below 60fps at the same time in the mission(between 13-16minutes) while the ground battle is at it's peak but most of the time the fps is around 80fps +/- and no drastic noticeable performance problems like you see(below 20). Did you try to run the mission without your monitoring tool running(also not in the background)? and only use the in game fps counter? Sorry, i hope this problem will solve itself for you asap.

Yeah but they said back then that they do the AI A-6 with the FF module in mind, granted that will only help with the 3D model i guess but atleast....

@J20Stronk Do you use the "performance" or the "visiual quality" version of the cockpit under the special options tab for the JF-17? I use the "performance" version because i only fly in VR and there the "quality" version is killing performance as soon as the canopy is closed and is much more prone to stuttering(at low level flying) compared to the "performance" version, maybe that makes a difference in 2d too(now)? Maybe worth a try if you use the "quality" version.

Quick question, is that correct that the openings left/right face in different directiosn? One has the opening to the front and the other side has the opening to the aft, i noticed that already in 2.5.x but forgot to ask.

Sorry for my OT post but every time i read this(EDIT: as response to the cargo compartment discussion), me -> The Mi-24 was designed for a european war and not for the hot/high environment of Afghanistan, thats why you had that limitation of the Mi-24 because nobody thought "let's design a cool helicopter that can fight in hot/high altitude conditions because WW3 will take place in afghanistan". No they designed it to fight in europe, you don't have that limitations in europe....

You can contact the ship via the ATC menu and call inbound, they will lower the railing(fence) like they would in RL during flight operations. Edit: Quick and dirty example, sorry for the shaky view i was flying in VR(there you can't see the shaky view) and recorded the trackfile so there isn't only the small left eye view recorded. (video should be 1440p after YT processing)

I used my "master arm" switch from my HOTAS to toggle the master arm on/off function of the KA-50 in the past. But if i want to use it after the 2.7 update it doesn't work anymore for the KA-50. - if the master arm switch is on safe and i use the switch on my HOTAS the switch in the cockpit toggles to armed and back to safe after not pressing the HOTAS switch anymore - if the master arm switch is on armed and i use the switch on my HOTAS the switch in the cockpit toggles to safe and back to armed after not pressing the HOTAS switch anymore - using the mouse to toggle the cockpit switch works should be 1440p after YT processing

There is something wrong with the S-80 rocket pods LoD. If it changes from the detailed version to the lower detail version the "case" is hanging half in the rockets vertically moved down. Picture and short video to explain it better: should be 1440p after YT processing

For every serious F-14 module owner i guess this is a major problem. So not for me, i prefere helicopter and AG/SEAD missions, i only bought the F-14 to support HB because of the A-6AI with the intent for a FF module thing mentioned, but i like to take the F-14 for a ride from time to time. I hope they(HB/ED) get it sorted out so every AIM-7F/M capable plane behaves the same(if there is no aircraft limitation) and not like it is now.

Hi @104th_Money thank you for the screenshots. I tried to reproduce(using metric not imperial) and it looks the (biggest) problem is the "thunderstorm" setting. With that setting it looks like visibility is drastically reduced, shortly after takeoff you can't see the ground anymore. If you alter that setting to "rain" the visibility is improved, you can still see the ground at ~8000-8500ft but at ~10kft you're in the clouds. So the clouds base setting is working but the "thunderstorm" setting is reducing visibility(adding fog? new effect?). This is probably not helping you if you want the thunderstorm feeling/setting.

I did only test once with the -7MH against one Mig-29S but that test worked. I will test against the Su-24m now(part of my CAP training mission). But it still is strange why the AIM-7M is missing against ECM capable targets in the F-14 but if the missile is fired from an F-15C or F-18 it will hit the ECM capable target. EDIT: The AIM-7MH also worked against Su-24M and TU-95 but unfortunately DCS crashed again on my second try to test(same mission). Considering this only happend with the F-14 and funny way only with the -7MH so far, earlier tests with the -7M went without crash, but could be coincidence. dcs2.log

For everyone having trouble with the AIM-7F and -7M, try to replace them with -7MH, that one worked in one quick test against a Mig-29S while the -7M missed every time. Btw, i didn't test the AIM-7M earlier because there was no default loadout(atleast i saw none) for the F-14B with that missile, would have tested that missile earlier if i didn't missed that.

It works against the Mig-29A because that plane has no ECM, if you replace the 29A with a Mig-29S all my AIM-7M missed(20nm, 15nm, 10nm, 5nm tested). I had to copy and change the loadout(ME) to replace the AIM-7M with AIM-7MH, hitting start(ME) resulted in my first DCS crash after updating to 2.7 (last one was a couple months ago because of a F-18/Harpoon bug). But after restarting DCS setting everything up again in the ME that missile(AIM-7MH) was tracking and killing the Mig-29S. Attached the DCS.log from the crash, this happend only once so far, it looks like DCS had some problems loading F-14 rio asset stuff. I use no mods, did delete my fxo/metashader2 folder and run Repair of DCS after updating to 2.7(precaution to verify files). dcs.log

Is this at mission start(after selecting the JF-17 and hit play) or later in the mission? I get: - F-18 ~94fps - F-14 and JF-17 ~91fps at mission start. HW and settings in the sig, i'm using the 466.11 nvidia driver.

After update(and repair) and before starting 2.7 for the first time i had still the old files and manually deleted them before starting 2.7 for the first time.