Jump to content

Selecting GUN on cyclic WAS was reverting MANRNG > value to default value


Moxica

Recommended Posts

Supposed to have been fixed, but I for one can not see any change in behaviour.

ASUS ROG Strix B550-E GAMING - PNY GeForce RTX 4090 Gaming VERTO EPIC-X  - AMD Ryzen 9 5900X - 64Gb RAM - 2x2Tb M2 - Win11 - HP Reverb g2 - Oculus Quest 2 - Thrustmaster Warthog HOTAS - Thrustmaster Pendular Rudder - 2X Thrustmaster MFD Cougar

Link to comment
Share on other sites

Works oh for me.  If I set ManRng to 1000 it stays there when re-WASing the gun.

i7-10700K @ 5Ghz | Asus Z490 Tuf Pro Gaming | RTX 3090 | 64 Gb RAM @3.6Ghz | 1TB Samsung 970 EVO+ SSD | 1TB addlink S70 M.2 SSD | 1TB Samsung 850 EVO | 4TB HDD | Reverb G2 | Thrustmaster Warthog HOTAS | Thrustmaster TPR rudder pedals | Thrustmaster Cougar MFDs

Link to comment
Share on other sites

4 hours ago, FalcoGer said:

I haven't noticed that. Did you update? What's your DCS version? Can you upload a track?

Good point. Yes I've updated. But I test a little back and forth between Beta and stable. I might have had a little brainfart. 😄 
Will doublecheck.

ASUS ROG Strix B550-E GAMING - PNY GeForce RTX 4090 Gaming VERTO EPIC-X  - AMD Ryzen 9 5900X - 64Gb RAM - 2x2Tb M2 - Win11 - HP Reverb g2 - Oculus Quest 2 - Thrustmaster Warthog HOTAS - Thrustmaster Pendular Rudder - 2X Thrustmaster MFD Cougar

Link to comment
Share on other sites

Works for me now again since latest OB Patch.

DCS MT 2.9.4.53707
Modules: UH-1H - SA342 - KA-50 BS3 - MI-24P - MI-8MTV2 - AH-64D - CH-47F(Preorder) - UH-60L(Mod) - A-10CII - F-16C - F/A-18C - FC3 -Combined Arms
 - Supercarrier - NTTR - Normandy2.0 - Persian Gulf - Syria - SA - Sinai - Afghanistan(Preorder) — Waiting for: OH-58D - BO-105 - AH-1G/F(Mod) - OH-6(Mod) - Kola  - Australia - Iraq

DCS-Client: 10900K, 64GB 3600, RTX3090, 500GB M2 NVMe(win10), 2TB M2 NVMe(DCS), VR VivePro2, PointCTRL, VaicomPro, Wacom Intuos S with VRK v2Beta

DCS-DServer: 11600KF, 32GB 3600, GTX1080, 1TB M2 NVMe(win10), 2TB M2 NVMe(DCSDServer), DCS Olympus

Simpit: NLR Flightsim Pro, TM Warthog Grip with 30cm Extension + Throttle, VPforce Rhino FFB, Komodo Pedals with Dampers, VPC Rotorplus+CBkit+AH-64D Grip, NLR HF8, Buttkicker (3*MiniConcert), TotalControls AH64D MPD‘s, TM 2*MFD‘s, Streamdecks (1*32,3*15,1*6), VPC CP#1

Link to comment
Share on other sites

  • ED Team

Hi, 

we are unable to reproduce but if you do see any further issues please attach the track replay 

thanks

smallCATPILOT.PNG.04bbece1b27ff1b2c193b174ec410fc0.PNG

Forum rules - DCS Crashing? Try this first - Cleanup and Repair - Discord BIGNEWY#8703 - Youtube - Patch Status

Windows 11, NVIDIA MSI RTX 3090, Intel® i9-10900K 3.70GHz, 5.30GHz Turbo, Corsair Hydro Series H150i Pro, 64GB DDR @3200, ASUS ROG Strix Z490-F Gaming, HP Reverb G2

Link to comment
Share on other sites

I'm not sure if this is the same issue, but I have had some issues in multicrew only (2 humans). In the CPG seat I had man range set to 800m.

  • Switching to gun either with HMD or TADS as selected sight, man range wouldn't be set but instead the last laser range would stick. I was under the impression that selecting gun would instantly select man range.
  • Switching to the other sight would set man range at either 1200m or 2400m and I don't know where those numbers are coming from.

When flying alone and switching to the front seat it behaves differently. I'll try to get a track.

  • Like 2
Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

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