danielwwm

Hi Ammo and team have put up a solution on their Helios 1.6 Support Discord server. Here is the link to the announcement that guides you on how to resolve this. https://discord.gg/kZquuD Worked fine after I did what Ammo said.

I would jump on the Helios 1.6 support Discord at https://discord.gg/qtvdVWc Ammo & team are great and usually on hand to assist. They were very helpful when I had a few issues installing 1.6. Good Luck!

Thanks for your reply. I will jump on Discord now

Firstly many thanks for your great work. The new Helios virtual cockpit has aligned the F18 much better than my numerous attempts by pixel calculating in version 1.4. Also apologies if my ineptitude with Helios has caused my confusion. I followed the quickstart video for fresh install with Capt Zeen 1.6 profiles and it kinda worked. MFDs we’re correctly displayed but i could not click on any of the cockpit buttons. To resolve the issue, i restarted and followed the video for the upgrade of 1.4 profile to Helios 1.6 and that worked. So if wanted to use Capt Zeen’s new 1.6 F18 profile from where I am, what should I do? i am unsure what to do, especially if Capt Zeen releases a new F18 profile with new features. Thanks for your efforts guys.

I upgraded to the Reverb from the Rift CV1. Sorry I don’t have any experience with Odyssey. When I was using the rift I had to move my sitting position fairly close in to be able to see and read the Mfds on the A10c, especially DSMS profiles and CDU. Sometimes I even had to lean forward. But when I moved to the Reverb I could easily read everything from the default sitting position so easily. It’s amazing for that but there’s a central sweet spot to the reverb. I can live with this as I am not looking at Mfds or gauges from my peripheral vision. SDE are nearly gone. I mean sometimes I forget it’s there but sometimes in a plain background, if you look for it, you will see it. But yeah miles ahead of the CV1. I saw the Reverb G2 reveal on Mixed Reality TV and it looks great.

Thanks for the great tips. I will run MSI afterburner with TGP and MAV on. Your comments also made me realise my RAM is also a choke point. Since I am on Sandy bridge, my RAM is only DDR3.:cry: Well not long now as Pre-orders for Comet Lake has already popped here in Melbourne and shipping May the 21st. Now the agonising decision whether to wait for the Ryzen, which is rumoured to be October or move ahead.

Thanks for the great advice Dis80786. I am not too fussed about the max fps but just making sure the min fps drops are reduced. From what I have found it is usually the TGP and MAV cameras on the A10c that slows it down. I also noticed when I played mission 1 of the Eastern Friendship campaign by Sedlo, when JTAC directs you for CAS on enemy units, my FPS really crawls down to mid 30s. I am unsure if its the units or the JTAC comms but something is slowing it down. Well I have to wait for 4 to 5 months anyway for either the new Intel/Ryzen and/or the 3080ti. The Ampere reveal at GTC will be on in a few hours! Can’t wait!

Thanks Taintid

I am looking forward to getting an AMD chip that would take the best gaming CPU mantle since the FX-51. Thanks for the tip on Michael Brown’s video, Hoirtel. Vulkan made a huge difference for me on Xplane 11. Hopefully will see the same for DCS.

Thanks guys. CPU it is. Hopefully the Ryzen 4xxx series will have a core clock on par with intel and the additional cores will take care of Vulkan when that comes online. I’ve been trying to look for an ultra wide 2080ti with a relatively new CPU benchmark video with TGP or Mav on MFD to see what I should expect in terms of the FPS with a CPU upgrade but its surprisingly hard to find. Most out there are flying around with DSMS/HSI and non-TGP/Mav Mfds.I just wanted to see what the minimum FPS were. To really kill the FPS in an A10C have the TGP in left MFD and MAV on right MFD.:(

Hi, Just after a bit of advice. I have a 2080ti with a 2600k clocked @ 4.5 Ghz running at 3440 x 1440 resolution. The main issue I have been facing is with A10C and F18C when I enable the TGP and especially the Mav cameras. FPS just tanks from 80s to low 50s and the stutter is noticeable, even with G-Sync. So much so if I am coming round for a second pass on ground targets in a A10c, i exit the Mav Cam back to TGP and go back to Mav cam when i am straight and level at the target. My question is would a CPU upgrade to the upcoming 10XXX intel/4XXX Ryzen or 3080ti be better suited to overcome this problem. I know Vulkan will address this issue somewhat with multi-core support, but what do you guys think? Just making plans for my next upgrade. I have already dropped the MFD to 512 res. Thanks

Firstly apologies as I did not notice this post. It sounds like the same issue though the original post read like he fired 2 x AGM65Es. I kept trying with a MavF and a MavE so I could fire 2 Mavs in a single pass. I will try with multiple AGM65Es, though Gripes has already tested this.

AGM65E issues with TGP I have been having issues with locking up and firing the AGM65E when self designating with TGP, especially after firing a AGM65F. I think i have the procedure down right:- 1) go to A/G mode 2) Enable laser 3) set laser code with UFC - 1688 2) Go to FLIR and lock up with TGP. make sure Trigger on and then arm laser LTD/R 3) sensor left to Mav 4) uncage 5)wait for LKD and fire I don't have this issue if I am firing the AGM65E first. I have posted a track below. Is this a bug or am I doing something wrong? Thanks for your help in advance! AGM65E-2.trk

Been trying to capture a track all night but as luck would have it, it worked every single time! Been through the mission like 6 times and worked every time, I will have to keep trying over the next few nights to get a track that captures the bug.

Thanks, I feel much better now knowing it’s not just me. I will try changing the laser code and hope it’s addressed in the next update. I usually don”t have a mix when I do missions but this is a self created mission with the Hornet fully loaded so I can practise if I am away from Hornet for too long.