ralch

I decided to wait until the first 2.9 patch. I tried it yesterday and started to suffer these horrible freezes. I was going crazy. I noticed that when the freeze was active, task manager showed no activity in any of the cpus. I have a 12700k. I found this thread, and used this to set ValueMax to zero (ValueMin already was in zero), which is the way to tell windows not to park any core (this is confirmed here and in one of the comments in the video). Before making the change, I verified that windows regularly parked cores when not in use, just as expected in any normal system. After the change, and a restart, windows no longer parked any cores. I realize this is different from what some members are saying here but it works. Windows no longer parks any core after this change. I've been playing in VR all day without any freezing issues, thank you! and I hope the developers are able to identify this issue and fix it as soon as possible since I don't want to disable this parking forever because of DCS.

I've tried group.SetSpeed() before Activate() and after, with true and false for Keep but SetSpeed() doesn't make any change. I've tried waypoints[1].speed = 450 and waypoints.points[1].speed = 450 but those two lines always fail. The error message says they are nil. The documentation for GetWayPoints() says nil could be returned but that there are waypoints. Obviously that group has waypoints defined in my mission editor. Any other ideas how I can obtain the non-nil waypoints for my 'Aerial-1' group?

Hi all, this is my first MOOSE script, can you please assist on how to fix it? I just need to modify the speed of the initial waypoint right before spawning a new group for the first time, but the script fails in line 3 Apparently, I have my documentation wrong about the waypoints table. What would be the correct line 3? 1: local group = GROUP:FindByName('Aerial-1') 2: local waypoints = group:GetWayPoints() 3: waypoints[1].speed = 450 4: local task = group:TaskRoute(waypoints) 5: group:Activate() If I delete line 3, all works well so MOOSE is working just fine. Thank you, P.S. If you are wondering why I need to do this is because I am tired of fixing the initial speed of that group manually every time I want to play with a different aircraft in the mission editor. The speed is critical for my formation flying stuff and the mission editor changes that speed when I select a different aircraft in the ME. Obviously once I got this script right, I am going to use it with many other Groups in my mission.

Thank you @kira_mikamy Unfortunately, it doesn't work because the aircraft is not flying in line #3. If I place it in line #5 then is too late, because the difference might be too big so we wont start in a good position for the initial formation task. Any other suggestion? Remember, I just need to change the speed of the first waypoint before spawning a group. kind regards

Hi, This is my fist script, can you please assist on how to fix it? I just need to modify the speed of the initial waypoint right before spawning a new group for the first time, but the script fails in line 3 specifying that points is a nil value. (attempting to index field 'points' (a nil value). Apparently, I have my documentation wrong about the route table. What would be the correct line 3? 1: local groupName = 'Aerial-1' 2: local groupData = mist.getGroupData(groupName, true) 3: groupData.route.points[1].speed = 436 4: mist.dynAdd(groupData) If I delete line 3, all works well so MIST is working just fine. Thank you, P.S. If you are wondering why I need to do this is because I am tired of fixing the initial speed of that group manually every time I want to play with a different aircraft in the mission editor. The speed is critical for my formation flying stuff and the mission editor changes that speed when I select a different aircraft in the ME. Obviously once I got this script right, I am going to use it with many other Groups in my mission.

Hi, With my settings I can run the Quest 2 at 1.5x resolution in the Quest App which means 5408x2736 (14.7Million Pixels) at 72Hhz without ASW in a 1v1 mission I love to do in the Nevada map. Can you advise if I am going to experience improved graphic details if I switch to the HP Reverb G2 at it's maximum resolution 4320x2160 (9.3Million Pixels) ? (I am thinking about the Reverb because of the black friday sale) Thank you in advance! Intel 12700K OC @5.2Ghz, 32GB DDR 5 RAM, RTX 3090 OC

Just in case someone else lands here, I can report that my Quest 2 is working nicely with DCS and the OpenXR toolkit with upscaling and foveated reendering. Originally, I was happy with vrperfkit but I needed VR Neck Saver which is only compatible with the OpenXR. Perhaps vrperfkit is a bit faster, but I am ok sacrificing that for the neck saver. You might find this video quite useful: And because I use a Quest2, I didn't have to install the OpenXR app from the microsoft store. You only need opencomposite and the OpenXR Toolkit (and VR Neck Saver if you also need that)

ok, at this point I think I need to know what do you mean by the switcher? sorry

Thank you @edmuss! Reading skatezillas, the step below seems simple enough: "... and force DCS to run issuing the steamvr runtimes, I think it's normally done using command line switches or possibly using skatezillas launcher" I believe to use open composite, I simply have to replace some binaries in the DCS bin folder... But, how do I set DCS to openxr in the switcher?

So I have the latest Quest 2 with their V46 Oculus Software and DCS OpenBeta 2.8.0.32235.1 I can play in VR with my Quest 2 with the usual performance/quality issues that everyone knows already. I don't use SteamVR and I didn't have to do anything special to make DCS work with my Quest 2. I want to try the Upscaling and Foveated Reendering of the OpenXR toolkit. I installed it but when starting DCS in VR nothing happens when hitting CTRL-F2. Can you please help me with the steps I am missing? (I found tons of guides in the internet, but must of them for the HP G2 and/or 1yr old, asking to enable public betas, and stuff that I think are outdated) Thank you!

Thank you Antix70, but I have never used SteamVR with DCS and my "home" in the quest2 dashboard is empty. That should be good for my RTX 3080 with 12GB of RAM.

Yes, I have been like this from day one on the Quest 2 and it happens the same in Rift S. I tried to open a support ticket with Oculus and they said they couldn't help with DCS. I posted a similar topic in the MSFS forum (same behavior) and I got this: Why 36FPS with ASW=Disabled gives less headroom than 72FPS with ASW=Disabled - Virtual Reality (VR) / Hardware & Performance - Microsoft Flight Simulator Forums However in my DCS VR settings, VSync is disabled... so that didn't help. ASW=ON fixes the stutter but I already explained why I don't like it. My only ideas now are: 1. People haven't noticed or don't care because when looking straight the problem is not so big. This issue is most noticeable when looking left/right during baking at low level. 2. The problem cannot be fixed changing settings because the LCD panel wants 72FPS. Well maybe I could but my graphics settings are already at the minimum compromise for me. 3. Buy the RTX 4090

What happens if you set 45fps and ASW=OFF? That way you get rid rid of the reprojection issues (props/rotos/etc)?

Hi everyone, I hope someone can help my to understand/fix this weird problem, because if I ask half the performance I obtain much worse results always, no matter if using Rift S or Quest2 with Win10 or Win11: I have configured my settings in such a way that 75%-80% of the time the game can run in 72FPS without AWS. It's almost perfect in every way for me. Sometimes, the scene is too complex so the game cannot support 72FPS. The FPS becomes very instable, it ruins my gameplay when I am trying to gun down my enemy for example, so the solution would seem obvious: Use the oculus debug tool and set AWS to 45FPS and ASW=Disabled. (I cannot use AWS=Auto/ON because when there are other planes flying at my left or right, they seem too ghostly or blurry due to inaccuracies when AWS=Auto/ON) The problem: When I configure 45FPS and AWS=Disabled or Enabled, the game plays much worse 100% of the time, there is always stutter, blurriness and ghosted images quite noticeable when looking left or right. What am I doing wrong? How can I fix this? Thank you very much! My specs: Intel 12700K, 32GB RAM DDR5, RTX 3080 12GB, Quest 2, DCS World Open Beta latest update, not using SteamVR. in the Quest software, I have configured a refresh rate of 72Hz and resolution of 4864x2448 that Quest classifies as 1.3X, Windows 11

hi everyone, Can somebody else please verify this? It happens in VR (Quest 2) and also in non-VR environment. Please see the screenshots. The counter shows 0 Video Memory used. Thanks in advance

When I press the FPS Counter key in DCS it shows the FPS as normal. Problem: When I press again, DCS shows more information, but the GPU Video Memory shows zero? Is there a way to fix this? Thank you in advance My specs: Win11, 12700K, RTX3080, 32GB RAM, Quest 2 (not using Steam VR but DCS directly),

Hi everyone, I believe the JF-17 needs some love with additional skins: How about these ones? 1: Wizard Livery from Ace combat 7: Skies Unknown - Full Size Image Link 2: C4 Blue orange fuselage with white nose and lower half from Ace Combat: Joint Assault - Full Size Image Link I realize in Ace Combat, they were for the F-16XL, but I think they would look pretty good in the JF-17. Any chance the talented artists in this forum could make these happen? Thank you!

Thank you!, I will take a look at that

Hi, I am writing a fun mission with several waypoints and triggers and all is working fine without LUA scripting. However when I change AI planes to try versus different enemies, the speeds of the waypoints automatically change and that causes problems with my mission. How can I add a simple startup LUA script (direct SDK without frameworks) to modify all waypoints for all planes at to have them all with the same speed, lets say 795Km/h ? Thank you!

Thank you so much!

any feedback on this one? should I post this question some where else? TIA

Hi Since more than 8+ years ago I have been using a 75'' Sony TV at 1080p for DCS World with track IR. My PC is a 2700K overclocked to 4.6Ghz with a RTX 2080 and 32GB of RAM. I have no issues running DCS World at 60fps on most conditions and the new clouds at normal definition. My TV was back in the day the most recommended TV for gaming and I have no issues with it. I like the big TV with DCS to be able to see the cockpit instruments roughly at the same physical size of the thing in real life. However, somebody is selling me an almost new (6 months old) 75'' Sony Bravia XR75X90J 4H UDH at a very fair price. Excluding other applications (4K HDR movies or other games) can you advise if switching to 4K and HDR is going to give me a better experience with DCS World (2D with trackir)? I have heard that in fact, switching to 4K actually makes things harder with the pixels 4 times smaller affecting visual enemy detection... thank you for your feedback

Thank you, I'll give it a try!

This sounds very useful, can you post a screenshot to show how this can be seen? TIA

It's hard to max perform the F-16 currently in DCS World, probably because it is too sensitive to the angle of attack. Real pilots can feel the jet and react accordingly but in DCS we need mostly to rely on the instruments. Please Consider adding the angle of attack in the HUD in the same way than the F-18C, at least as an special option for the F-16. That would help a lot in DCS world. Having to look down to see when you are exceeding the 15o yellow/green/red stripes is very distracting. The angle of attack lights in the left of the HUD are just fine for landing but they don't help you in a dogfight because you don't know exactly when you are going to exceed the limit.