Polo

Hi all, I'm currently using a stock Vive Pro (other than a replaced face cushion) almost exclusively for DCS. Is there any noticeable benefit in upgrading to a newer headset (Vive Pro 2, G2 etc.) or is it worth having a go at the Gear VR lens mod instead and waiting sitting on this headset for now? Open to anyone's experiences...good, bad or ugly on this. Thanks!

Weird, I did a similar update last week (watercooled 2080Ti to 6900XT) and found I did get a noticeable bump in performance. Plus now running terrain textures on high due to the additional VRAM. Did a full uninstall of the NVidia drivers, changed card over (bled the loop etc.) and installed the latest AMD drivers and it was up and running. Also might have cleared out the DCS shader folders, but can't remember for certain. As for HAGS, I don't remember seeing this option either.

Umm...the Patriot site is usually a bit of a mess by the end of the scenario with this tactic, but by the strikers are as well...

Have completed this Instant Action mission once or twice. My tactic has been to take off ASAP and accelerate/climb while keeping the incoming aircraft on my 3 o'clock. Once the main body have passed and/or been engaged by the F16s turn in and start lobbing AIM120s at the trailing SU34s. You have to watch out for the escorts turning in on you, but normally I find the enemy flights degenerate into a bunch of individual aircraft that can be picked off. Your wingmen are good missile absorbers while doing this.

Don't get into motorbikes or cars then...

Just to add my very short 'test' on fpsVR reported GPU VRAM usage... 2080ti 11GB, Instant Action F14A take off Turkey (on the Syria map) - with terrain textures on high I'm seeing 10.7GB GPU VRAM usage, getting 30fps with about 60-65% GPU usage and noticeable stuttering - with terrain textures on low (only change) I'm seeing 10.5GB usage GPU VRAM usage, getting 45fps at about 80-85% GPU usage and stutter-free Flying around for about 10 minutes with the Terrain textures on low and the intermittent stutter every 30 seconds or so is totally gone as well. Not saying it is definitive and will still keep running on low terrain textures, but seems to have helped here.

Synchronization with multicore processors is relatively easy, however it is also very easy to get into a situation where you have every other core waiting on one to finish processing something before they can begin their task(s). End result is you may end up actually slower, as the tasks are being run in sequence plus you have synchronization code adding extra overhead. Loading up multiple cores consistently and efficiently at the same time is extremely complicated, and probably requires you to design that way in the beginning. Here is an old article coding for multicores on the XBox360, but it does cover alot of the issues and what is involved: https://docs.microsoft.com/en-us/windows/win32/dxtecharts/coding-for-multiple-cores

Agreed, great to hear Deltaalphalima1! I'm up for one as soon as it's ready to go!

Hi all, Is anyone aware of a supplier for the Cougar Throttle microstick double pot (part no 252A104B60NB on CougarWorld's warranty part list)? My microstick is failing on the Y-axis, move it downwards and it spikes left/right randomly. Thrustmaster are reporting that they don't have any in stock and they don't know if they will get more in, and I haven't been able to find an active email address for RedDog. Also other suppliers for this part don't seem to have stock, being discontinued in 2015. Also happy to pay to take one off someone's hands if they have a spare. Thanks Formski

Thanks - it was similar to this. I'd setup a symbolic link (i.e. mklink) for the tech folder under Saved Games, and that was what was causing the issue. Removed the link and reset the lua code in VAICOMPro and all good now. Funnily enough it had worked a few weeks ago before a reformat. Must have been changes in the OB versus Stable of late.

VAICOMPro and OB 2.5.6.45317 Issues Hi all, Am I the only person having issues with the latest Open Beta 2.5.6.45317 released on the 20th of March? What I'm seeing is the comms menu (i.e. COMM1 in the F/A-18 ) appearing randomly; Commands being recognized in VoiceAttack, but not executing in DCS; the VAICOMPro configuration window showing 'Easy Communication'; and getting the 'AIRIO Commands are not Available' message whenever trying them All was working correctly with the previous OB, and also fine in stable. I'm open to suggestions...

I've had this happen quite a few times in the past on 2.5.5, what I found works is to throttle down then go to full power again and salute. Am at work now so will check out tonight to see whether 2.5.6 is any different or not.

Yes using the later drivers you can swap them by changing MFD 1 to 2 and MFD 2 to 1. DCS World handles this without issue, left becomes right and right becomes left - no need to make any controller assignment changes in DCS. Sent from my SM-N950F using Tapatalk

Hi all, The usual question around here - trying to work out what (if anything) is worth to do to upgrade my PC to increase DCS World performance. Am currently running a the following: 4930K at 4.6Ghz under water (custom loop) on an X79 motherboard 32GB DDR3-RAM at 2133Mhz (Quad-channel is working) nVidia 2080Ti video card under water HTC Vive Pro VR Goggles and a bunch of SSDs, on which DCS and my Profile are all residing. General performance is good, but it does bog down at times, especially with certain types of aircraft on the screen (looking at you DCS F/A-18C 3D model) Admittedly running with PD at 1.3 on top of SteamVR at 150% resolution, but the video card is often sitting at 65-70% use, while the CPU is pushing into the 30-45ms frametime range according to fpsVR. Also running at PD 1.0 has similar performance issues. Is there any benefit to DCS World at this stage looking at either an Intel 9700k or 9900k CPU upgrade (and all the associated motherboard, RAM etc. bits) or an AMD Ryzen 3800 or 3900 (any new processor will be running under water) compared to what I'm running currently?

Two things with the Vive Pro: The headset works with glasses (you can physically 'push' or 'pull' the HMD screens away from your eyes to accommodate them); and The 'Lightboxes' don't require USB, just power. No argument on the $$$ though :shocking:

I'm getting this on my AMD Vega 64 card (8GB Video RAM) and 32GB System RAM, so it's not just a Nvidia specific issue. As said earlier, it started with the new 'memory manager' which (for me at least) has not provided any observable advantages on my system.

First off, make sure you're in MAN (i.e. manual) mode on the top of the MFD (centre button I think) but using the MODE button on the bottom left. FWD on the throttle always runs program 5 and can't be changed. To change the AFT program use the 'STEP' button on the EW MFD to select programs 1 through 5. (I think, all the above is off top of my head as at work)

There is an issue with the Instant Action Caucasas 4v4 ACM mission (4 F/A18s vs 4 MiG29s) where you cannot shoot the AIM9Ms that are loaded under the wings anymore. I think this is because they're on single rails which are apparently not realistic and have been removed. Maybe this is what you've run into? One way to test is to select the wingtip AIM9Ms and see if they shoot - cycle the missiles by hitting the AIM9 select button until the wingtips missiles selected.

My Slew upgrade rocked up yesterday and installed last night. This fixes up my biggest gripe on the Warthog - the trackball cursor. Radar control on the Hornet and M2000C are so much easier, as is controlling the TGP and Maverick seekers on the A10C. This upgrade is a game changer.

I don't find this one too bad - I just send the AI in 'Engage Bandits' right at the start and they almost always now fire first. I'll usually lob an AIM7M in LOFT mode then crank out right. Invariably misses but then ACM with AIM7s I can often get one, maybe even two before the merge. Whether all my AI wingmen survive is simply dependant on luck.

Not that it's helpful, but I only started experiencing this once the new video card 'memory manager' was introduced a few months ago. Before that I never saw this effect. Installed on a SSD and I only see this randomly when changing views for about 1-2 seconds.

I managed to get rid of the 'bubble' fog(less) effect in the atmosphere2 file, changing the multiplier for the non-weather application to almost 0.0. I wonder whether this is causing the grass colour to be too dark? At work right now but will check tonight where in the file it was and see if the grass looks right or not.

Possible Fog/Weather Issue This mod works well overall, however have run into an issue with (I think) the weather not being applied near the player's aircraft. See attached which are from the Caucausas AJS37 Instant Action Cold Start scenario. With the modified shaders there is a clear 'bubble' around the aircraft when it is foggy, whereas when the default DCS shaders are being used the fog fills the entire area. Happy to check further scenarios or situations if of any help.

I've been running one since late last year. For DCS it does pretty well, FPS lower than some of the numbers quoted for the 1080ti but that's with everything turned up. Running on a FreeSync monitor was pretty sweet. On the HTC Vive in VR with Kegetys' VR Shader mod in the F/A-18 I'm on 45fps most of the time with a few drops to 30-35fps. This is with most items turned up to High, visual range on High, 4xMSAA. It easily handles everything else I throw it at 3440x1440 res. Mine's water cooled so I can't comment on fan noise as I haven't run it on air ever.

I've got the same issue upon startup: Shader "bazar/shaders/deferred/ResolveDepth.fx" failed to compile. Reason: warning X4717: Effects deprecated for D3DCompiler_47 D:\...\bazar\shaders\deferred\ResolveDepth.fx{89,17-33}:Unrecognized token disableAlphaBlend Am running an AMD Vega 64 on the current 18.6.1 drivers version if that is any help?