A2597

I'm in the "Want a headset to replace my CV1" boat. But classic "Pick 2 of 3" conundrum. Affordable Resolution FOV Somewhat leaning towards Index, just because of the FOV and then I'll have the base stations and Controllers for a future headset upgrade...but the resolution over the CV1 is minimal from all accounts, which makes me sad.

I'm basically in the same boat as Elunnia. Better FPS, but no matter what combination of MSAA (off to Max), Pixel Density (tried between 1 and 1.5) , cloud detail, etc, very low quality clouds in VR. I've deleted shader cache too, just to be sure. (Dunno if any of this helps narrow down the issue, but figure I'd share it anyway)

Got to spend a couple more hours in it this evening. Not near enough comments on the new sounds! Carrier takeoffs and landings are awesome, the sound of another jet passing by, just loads of little things that make it sooo much better! And yes, new smoke and fire effects are awesome! And in VR, the new spotting / dot settings.... AMAZING! And water / wake effects...and how clear the water can be when you are directly over it, or when the sun hits it right... just love it all!

I consider this a bug thread. In a bug thread, we talk about the bugs, we share our settings / criticism, because that's the point of this thread. There are other threads for praising the clouds / other updates (because on a whole, this was an AMAZING update across the board!). But the devs also need to know what issues people are having to make a better product. So long as the criticism is constructive, and kept to the appropriate threads / forums, there's no issues IMHO.

Pretty much the above. ULTRA clouds in VR look like LOW clouds on flat panel. PD doesn't seem to be a factor.

Agreed, this patch is amazing. Lots of additions, settings, visual improvements, and it actually runs BETTER than before for me!

ditto, even set to ultra, VR clouds are low quality. (But still way better than the old head-spinning puffs!)

Been googling and reading this thread for awhile, but have no fix for a .Net Unhandled Exception, related to JIT Debugging. Have yet to find a solution. Uninstalled everything, re-installed everything (SSA and Jetseat control panel) And still getting the error as soon as I try to open SSA. See the end of this message for details on invoking just-in-time (JIT) debugging instead of this dialog box. ************** Exception Text ************** System.Net.Sockets.SocketException (0x80004005): An attempt was made to access a socket in a way forbidden by its access permissions at System.Net.Sockets.Socket.DoBind(EndPoint endPointSnapshot, SocketAddress socketAddress) at System.Net.Sockets.Socket.Bind(EndPoint localEP) at System.Net.Sockets.UdpClient..ctor(Int32 port, AddressFamily family) at SimShaker.Core.DataProvider.XPlaneDataProvider..ctor(CallBackOnAircraftChange callBackOnAircraftChange, Action callbackPlayEffects, Action callbackStopEffects) at SimShaker.Core.MasterManager..ctor(MainForm link) at SimShaker.UI.MainForm..ctor() at SimShaker.UI.AutoStarterForm.startSimShakerForDCSWorldToolStripMenuItem_Click(Object sender, EventArgs e) at System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e) at System.Windows.Forms.ToolStripMenuItem.OnClick(EventArgs e) at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e) at System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e) at System.Windows.Forms.ToolStripItem.FireEventInteractive(EventArgs e, ToolStripItemEventType met) at System.Windows.Forms.ToolStripItem.FireEvent(EventArgs e, ToolStripItemEventType met) at System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea) at System.Windows.Forms.ToolStripDropDown.OnMouseUp(MouseEventArgs mea) at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks) at System.Windows.Forms.Control.WndProc(Message& m) at System.Windows.Forms.ScrollableControl.WndProc(Message& m) at System.Windows.Forms.ToolStrip.WndProc(Message& m) at System.Windows.Forms.ToolStripDropDown.WndProc(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m) at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam) ************** Loaded Assemblies ************** mscorlib Assembly Version: 4.0.0.0 Win32 Version: 4.8.4300.0 built by: NET48REL1LAST_C CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll ---------------------------------------- SimShaker for Aviators beta Assembly Version: 2.2.2.0 Win32 Version: 2.2.2.0 CodeBase: file:///C:/Program%20Files%20(x86)/SimShaker/SimShaker%20for%20Aviators%20Beta/SimShaker%20for%20Aviators%20beta.exe ---------------------------------------- System.Windows.Forms Assembly Version: 4.0.0.0 Win32 Version: 4.8.4270.0 built by: NET48REL1LAST_C CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll ---------------------------------------- System Assembly Version: 4.0.0.0 Win32 Version: 4.8.4300.0 built by: NET48REL1LAST_C CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll ---------------------------------------- System.Drawing Assembly Version: 4.0.0.0 Win32 Version: 4.8.4084.0 built by: NET48REL1 CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll ---------------------------------------- NLog Assembly Version: 4.0.0.0 Win32 Version: 4.7.8.12686 CodeBase: file:///C:/Program%20Files%20(x86)/SimShaker/SimShaker%20for%20Aviators%20Beta/NLog.DLL ---------------------------------------- System.Configuration Assembly Version: 4.0.0.0 Win32 Version: 4.8.4190.0 built by: NET48REL1LAST_B CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll ---------------------------------------- System.Core Assembly Version: 4.0.0.0 Win32 Version: 4.8.4320.0 built by: NET48REL1LAST_C CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll ---------------------------------------- System.Xml Assembly Version: 4.0.0.0 Win32 Version: 4.8.4084.0 built by: NET48REL1 CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll ---------------------------------------- System.Data Assembly Version: 4.0.0.0 Win32 Version: 4.8.4270.0 built by: NET48REL1LAST_C CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_32/System.Data/v4.0_4.0.0.0__b77a5c561934e089/System.Data.dll ---------------------------------------- System.ServiceModel Assembly Version: 4.0.0.0 Win32 Version: 4.8.4250.0 built by: NET48REL1LAST_C CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.ServiceModel/v4.0_4.0.0.0__b77a5c561934e089/System.ServiceModel.dll ---------------------------------------- System.Runtime.Serialization Assembly Version: 4.0.0.0 Win32 Version: 4.8.4250.0 built by: NET48REL1LAST_C CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Runtime.Serialization/v4.0_4.0.0.0__b77a5c561934e089/System.Runtime.Serialization.dll ---------------------------------------- Accessibility Assembly Version: 4.0.0.0 Win32 Version: 4.8.4084.0 built by: NET48REL1 CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/Accessibility/v4.0_4.0.0.0__b03f5f7f11d50a3a/Accessibility.dll ---------------------------------------- ************** JIT Debugging ************** To enable just-in-time (JIT) debugging, the .config file for this application or computer (machine.config) must have the jitDebugging value set in the system.windows.forms section. The application must also be compiled with debugging enabled. For example: <configuration> <system.windows.forms jitDebugging="true" /> </configuration> When JIT debugging is enabled, any unhandled exception will be sent to the JIT debugger registered on the computer rather than be handled by this dialog box. Any ideas how to fix? Windows 10, everything up to date, no crazy antivirus installed.

looks like the change log addresses the clouds issue in campaigns. Most campaigns have a ```All missions. Updated to 2.7, added new clouds.``` line in the update notes. https://www.digitalcombatsimulator.com/en/news/changelog/openbeta/2.7.0.4625/

I'm really curious how the new clouds will effect existing missions and campaigns. I'm currently playing the Raven One campaign, one mission a week...should get new clouds tomorrow...will be fun since it's mission 3, which has some pod work in it.

VR (And I'm still in an old CV1!) with DCS has let me semi-fulfill a life long dream of flying a modern fighter. So many wonderful memories in the headset, and yes...nailing an ICLS landing after a successful mission is truly a great moment. (I love to end the flight by parking my plane, shutting it down, raising the canopy and watching some other jets land while listening to the waves and jet engines).

also, clouds rotating when tilting your head... hoping that is gone with the new clouds.

I want Reverb graphics with higher FOV...at less than 1k.

Re: FS2020, The reason it doesn't work (yet!) is because FS2020 basically maps the mouse to a sphere around the player, rather than to the current viewpoint. Miles said he may be able to do something for it, but is currently focused on getting production up and running before he can really dig into it. (And no promises, this is intended for DCS currently)

Sounds like Rising Squall is a good one to get for me right now. I'm only able to fly about 2 hours a week, just can't keep all these skills fresh doing that. (Hop on and try to use the TGP only to find it's changed a lot since last time I used it...no muscle memory for the controls, etc). Would love to do Raven 1, but the systems knowledge would be a stress point right now.

I feel the sme way, can't fly without VR. Now that I have a good HOTAS, id say PointCTRL was the 3rd best purchase for DCS. It lets you actually reach out and use the controls in cockpit!

AWESOME! Going to play with this as soon as I can.

I'm itching to try these in FS2020, Xplane is a big miss on them because of their mouse, but the FS2020 VR dev update gives me hope it will work there. Will know in a few days. If it works, 99% positive I'll have another sale so my dad can enjoy these.

I can once I get back home in a few days. this was on the F18 Hornet.

So managed to snag a RTX 3070, and had been tempering my expectations coming from a htx 1080(non ti), paired with R5 3600 and 16gb ram. I fly 100% vr on a oculus CV1. before: flat shadows, max trees and grass, 1.3pd, 2x msaa, no ssaa, etc. Usually FPS in the 30s on ground. Dubai is always challenging, again 30s it common. Now? same as above but 1.5pd, and added ssaa, and im locked at 45fps. Turning off the smoothing and I have fps in the 50s to 60s flying through Dubai! Did not expect that big of a difference!

ATI now has their AI upscaling, hopefully it's similar enough they could enable for both?

What is the CPU you will be playing with? the 3070 is far faster than a 1080ti, and the 3080 even more so, but DCS is a CPU hog as well...

for VR I have Comm Forward / Back as both zoom levels on my warthog throttle. There is no axis zoom in VR.

So click able cockpit question... are the screens touchscreens we click on? Or just display only?

Ohhh... looking forward to this!