Jump to content

Patch notes discussion 10th March - 12th April 2023


Recommended Posts

Posted

No changelog yet for Todays patch! Why, tell me why? 😉 

Webmaster of http://www.yoyosims.pl

Yoyosimsbanner.gif

Win 10 64, i9-13900 KF, RTX  5090 32Gb OC, RAM 64Gb Corsair Vengeance LED OC@3600MHz,, 3xSSD+3xSSD M.2 NVMe, Predator XB271HU res.2560x1440 27'' G-sync, Sound Blaster Z + 5.1, TiR5, [MSFS, P3Dv5, DCS, RoF, Condor2, IL-2 CoD/BoX] VR fly only: Meta Quest Pro

Posted
6 минут назад, YoYo сказал:

No changelog yet for Todays patch! Why, tell me why?

Patience my friend) Keep relaxing, don't get distracted😅

  • Like 1

i7-11700K 5GHz, 64GB DDR4@3200, ZOTAC RTX4090, iiyama 34 Red Eagle  || Quest 3  || Thrustmaster TQS,  Tianhang M-FSSB PRO base, VPC Interceptor rudder pedals  || Simshaker Jetpad || F-16 cockpit

 

 

Posted

First! 😄

 

 

DCS World

  • MT. Created a special MT mission uploading mode decreases mission opening time
  • MT Export viewports corrupted - fixed
  • MT. VR, Aircraft are missing cockpit tooltips - fixed
  • MP. Crash when trying to control static via command panel - fixed
  • MP. Crash when 052B Destroyer use target lock - fixed
  • MT.Random stretched cockpit/resolution - fixed
  • МТ. Hypoxia effect visual is broken - fixed
  • Fixed: Smoke and craters from explosions flicker and lag in TV Mode of Targeting Pod
  • Like 1
Posted

MT with OpenVR still crashing...

null

image.png

  • Like 1
  • Thanks 1

i7-11700K 5GHz, 64GB DDR4@3200, ZOTAC RTX4090, iiyama 34 Red Eagle  || Quest 3  || Thrustmaster TQS,  Tianhang M-FSSB PRO base, VPC Interceptor rudder pedals  || Simshaker Jetpad || F-16 cockpit

 

 

Posted (edited)

So I guess no fix then for Varjo headsets being able to run natively with Open XR. Not surprised. Will just have to keep using Mbucchia's wrapper in order to get it to run correctly.

Edited by dburne

Don B

EVGA Z390 Dark MB | i9 9900k CPU @ 5.1 GHz | Gigabyte 4090 OC | 64 GB Corsair Vengeance 3200 MHz CL16 | Corsair H150i Pro Cooler |Virpil CM3 Stick w/ Alpha Prime Grip 200mm ext| Virpil CM3 Throttle | VPC Rotor TCS Base w/ Alpha-L Grip| Point Control V2|Varjo Aero|

Posted
21 minutes ago, dburne said:

So I guess no fix then for Varjo headsets being able to run natively with Open XR. Not surprised. Will just have to keep using Mbucchia's wrapper in order to get it to run correctly.

 

ah, I was about to say - I'm running fine on my aero, but I am using the mbucchia wrapper as well

Posted
6 hours ago, unlikely_spider said:

PM me your cell phone number. When the patch is released I will call you, and you can pretend it's your wife saying a pipe busted in your house.

 

gigachad_1068x.jpg

  • Like 2

i7 13700k @5.2ghz, GTX 5090 OC, 128Gig ram 4800mhz DDR5, M2 drive.

Posted

Experience in VR / 2D with the newest MT (SP, F-16 take off Nevada instant action staying on the runway and just looking around):

  • 42 fps CPU bound (main thread) !!! - what does that mean? I thought that in VR with high res headsets like the G2 the GPU will be over stressed in MT, but it's not the case, not even the rendering thread is the bottleneck?! Is this right?
  • with the same settings in 2D I got 120 fps GPU bound in the cockpit

VR / Marianas / SP / F/A-18 free flight: how can I say in poline way... well, unusable. Tried to switch off MSAA / forest / scenery details to minimum. Still CPU bound (main thread).

It seems that for the current EDGE VR is just became terrible, a stutteting mess. I really hope DLSS and most importantly Vulkan will be close, because right now I'm very dissapointed.

  • PC: 14700K | Gigabyte Z790 | Palit 3090 GamingPro | 32GB | Win10 Pro
  • HMD: HP Reverb G2 | OpenXR @ 150% |  DCS 2.9: PD: 1.0, DLSS 4 Profile "K" / "Performance" with Sharpening 1
  • Controllers: VKB Gunfighter MkIII base & 200 mm curved extension center mounted + TM F16 Grip / MCG Pro Grip | TM TFRP
Posted

Pardon if this is a silly question, In Stand alone open beta, use the original Non MT .exe to update or add the patch? The MT .exe doesn't check for updates if I understand correctly? Thanks in advance. 🙂

Rig Specs, i5-12600K, Asus Tuf Gaming Z690 Plus MB, 64 GB Kingston Vengeance Beast ram, Asus RTX 4070 OC, Samsung 980 Pro M.2 1 TB NVme SSD Drive, EVGA 750 Watt PS. Windows 11 Pro 22H2, Vizio 43 inch G-Sync Compatible TV, Oculus Quest 3, CH Hotas,( Fighterstick, Pro Throttle, All axis analog pots converted to sensors), MFG Crosswind Rudder Pedals, V3.

Posted
1 minute ago, 13sq*Axe said:

Pardon if this is a silly question, In Stand alone open beta, use the original Non MT .exe to update or add the patch? The MT .exe doesn't check for updates if I understand correctly? Thanks in advance. 🙂

exactly

SYS: II Asus X670E-F || Ryzen 9800X3D || Gainward RTX4090 || 2x48 GB Kingston Fury Renegade 6000Mhz || XPG Core Reactor 850 Watt PSU || Kingston Fury 2 TB NVME SSD || WD SN850 1TB NVME SSD || 1 x 500 GB Crucial MX300 SATA SSD || 2 x HDD 3TB ||

INPUT: II Thrustmaster F-16 & F-18 Stick on Virpil War BRD Bases || WinWing Orion2 F-16EX Viper Throttle Combo || WinWing Orion2 F/A-18 Hornet Throttle Combo (With Finger Lift) || WinWing Takeoff Panel II MFG Crosswind Pedals w. Damper || 3 x Thrustmaster Cougar MFD || Multipurpose UFC || II Wheel Stand Pro II

 VR: HP Reverb G2

Posted
10 minutes ago, 13sq*Axe said:

Pardon if this is a silly question, In Stand alone open beta, use the original Non MT .exe to update or add the patch? The MT .exe doesn't check for updates if I understand correctly? Thanks in advance. 🙂

use /bin/dcs_updater.exe

  • Like 1

🖥️ Win10  i7-10700KF  32GB  RTX4070S   🥽 Quest 3   🕹️ T16000M  VPC CDT-VMAX  TFRP   ✈️ FC3  F-14A/B  F-15E   ⚙️ CA   🚢 SC   🌐 NTTR  PG  Syria

Posted

Many thanks again folks. 🙂

 

Rig Specs, i5-12600K, Asus Tuf Gaming Z690 Plus MB, 64 GB Kingston Vengeance Beast ram, Asus RTX 4070 OC, Samsung 980 Pro M.2 1 TB NVme SSD Drive, EVGA 750 Watt PS. Windows 11 Pro 22H2, Vizio 43 inch G-Sync Compatible TV, Oculus Quest 3, CH Hotas,( Fighterstick, Pro Throttle, All axis analog pots converted to sensors), MFG Crosswind Rudder Pedals, V3.

Posted
34 minutes ago, St4rgun said:

Experience in VR / 2D with the newest MT (SP, F-16 take off Nevada instant action staying on the runway and just looking around):

  • 42 fps CPU bound (main thread) !!! - what does that mean? I thought that in VR with high res headsets like the G2 the GPU will be over stressed in MT, but it's not the case, not even the rendering thread is the bottleneck?! Is this right?
  • with the same settings in 2D I got 120 fps GPU bound in the cockpit

VR / Marianas / SP / F/A-18 free flight: how can I say in poline way... well, unusable. Tried to switch off MSAA / forest / scenery details to minimum. Still CPU bound (main thread).

It seems that for the current EDGE VR is just became terrible, a stutteting mess. I really hope DLSS and most importantly Vulkan will be close, because right now I'm very dissapointed.

Same for me - weird.

Posted (edited)
3 hours ago, Roosterfeet said:

Anyone know how severe this is in today's patch?

Known Issues:

FPS hit with many bullet impacts over time

I don't believe anything has changed with today's update in regards to this other than that it's now a known issue because it was figured out and reported in the forum a couple of days ago.  If you're already on the MT beta you might as well update because it's not going to change whether you see this or not (it was already and issue in MT beta and they haven't fixed it).  At least that's how I read it.

Edited by rob10
Posted
1 minute ago, ColinM9991 said:

What does this mean?

I would imagine using MT mission loading times are less than using ST, thats how I would read that line

  • Like 1
Posted

The second TM patch and correct settings in open xr toolkit have given me the smoothest VR experience to date.

  • Like 1

i7 13700k @5.2ghz, GTX 5090 OC, 128Gig ram 4800mhz DDR5, M2 drive.

Posted (edited)
13 hours ago, St4rgun said:

Experience in VR / 2D with the newest MT (SP, F-16 take off Nevada instant action staying on the runway and just looking around):

  • 42 fps CPU bound (main thread) !!! - what does that mean? I thought that in VR with high res headsets like the G2 the GPU will be over stressed in MT, but it's not the case, not even the rendering thread is the bottleneck?! Is this right?
  • with the same settings in 2D I got 120 fps GPU bound in the cockpit

VR / Marianas / SP / F/A-18 free flight: how can I say in poline way... well, unusable. Tried to switch off MSAA / forest / scenery details to minimum. Still CPU bound (main thread).

It seems that for the current EDGE VR is just became terrible, a stutteting mess. I really hope DLSS and most importantly Vulkan will be close, because right now I'm very dissapointed.

I did some testing, tried a full repair, installed the latest nVidia drivers, ... Still the same for me. VR performance keeps as bad as it got after the dynamic weather update. Perhaps the graphs are wrong and it is not really CPU bound? Why should it, especially in a free flight situation with no units. If you decrease the render resolution you will see a performance increase, too. So the GPU seems to be the limiting factor.

I will stay on pancake and try again with DLSS and Vulkan. For 2D I could see a performance boost which is great.

Edited by Hive
Posted
46 minutes ago, Hive said:

I did some testing, tried a full repair, installed the latest nVidia drivers, ... Still the same for me. VR performance keeps as bad as it got after the dynamic weather update. Perhaps the graphs are wrong and it is not really CPU bound? Why should it, especially in a free flight situation with no units. If you decrease the render resolution you will see a performance increase, too. So the GPU seems to be the limiting factor.

I will stay on pancake and try again with DLSS and Vulkan. For 2D I could see a performance boost which is great.

 

I also did a full repair before my test. Nominately the fps numbers are a bit better in MT than the ST version (5-10%), but the stuttering is much worse. It's even horrendous when looking sideways. I only tried quick take offs and free flights with the built in instant action missions on Caucasus, Nevada, Marianas maps.

Interestingly the F-5E Caucasus winter take off mission with the snow became even much worse az the buildings of newar Batumi airport despite the fps counter says 25-30 fps but it is so stuttered that it's a max of 3-4 fps in reality. If I only look straight then it's much better.

Even the menu produces 60-75 fps maximum (!!! with a 3090 NO WAY), while in ST version it's locked at 90 fps. Something is really bad with this build for VR...

  • Thanks 1
  • PC: 14700K | Gigabyte Z790 | Palit 3090 GamingPro | 32GB | Win10 Pro
  • HMD: HP Reverb G2 | OpenXR @ 150% |  DCS 2.9: PD: 1.0, DLSS 4 Profile "K" / "Performance" with Sharpening 1
  • Controllers: VKB Gunfighter MkIII base & 200 mm curved extension center mounted + TM F16 Grip / MCG Pro Grip | TM TFRP
Posted

In my case very positive performance increase in VR. I was able to up my resolution and anisotropic filtering a bit and had very smooth gameplay on the Wolfpack server, Normandy map, WWII. I had a time on the 4YA WWII server where it turned into a stuttering mess. Not sure if it was me or the server. Thumbs up from me for MT so far.

Rig Specs, i5-12600K, Asus Tuf Gaming Z690 Plus MB, 64 GB Kingston Vengeance Beast ram, Asus RTX 4070 OC, Samsung 980 Pro M.2 1 TB NVme SSD Drive, EVGA 750 Watt PS. Windows 11 Pro 22H2, Vizio 43 inch G-Sync Compatible TV, Oculus Quest 3, CH Hotas,( Fighterstick, Pro Throttle, All axis analog pots converted to sensors), MFG Crosswind Rudder Pedals, V3.

Posted

Not sure if I have a poor set of setting however in vr the stuttering is frequent and makes it quite unpleasant. Which is a shame since in between the stutters it's greatly improved. 

RTX 2080ti, I7 9700k, 32gb ram, SSD, Samsung Odyssey VR, MSFFB2, T-50 Throttle, Thrustmaster Rudder Pedals

Guest
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...