Jump to content

Recommended Posts

Posted

Firstly - great patch guys, I love seeing the Viper come together!

 

I'm not sure if I've found a bug, I want to do more testing but this is what I've found so far.

I can set the markpoint using HMCS the first time around. Once I've employed ordnance (Maverick in PRE mode in this case, haven't tested much else yet), I cannot get it to switch to HMCS to set a second mark point.

 

Steps to reproduce:

Set a markpoint normally using HMCS (works the first time)

Select that mark as your stpt, slew the pod onto the target

Fire a maverick in PRE mode using the TGP.

Now, pressing 7 (mkpt), then using TMS up long will not switch to the HCMS for mark point creation (no circle in the HMCS). I've tried switching out of A-G, switching mavs out of pre, TMS down, etc - nothing I can figure out yet will allow me to set a second markpoint using HMCS once I've fired a mav in PRE mode.

HCMS Markpt.trk

Ryzen 7 5800X3D / Asus Crosshair VI Hero X370 / Corsair H110i / Sapphire Nitro+ 6800XT / 32Gb G.Skill TridentZ 3200 / Samsung 980 Pro M.2 / Virpil Warbrd base + VFX and TM grips / Virpil CM3 Throttle / Saitek Pro Combat pedals / Reverb G2

Posted
1 minute ago, verana_ss said:

u sure you had HUD as SOI?

Affirm. 

Ryzen 7 5800X3D / Asus Crosshair VI Hero X370 / Corsair H110i / Sapphire Nitro+ 6800XT / 32Gb G.Skill TridentZ 3200 / Samsung 980 Pro M.2 / Virpil Warbrd base + VFX and TM grips / Virpil CM3 Throttle / Saitek Pro Combat pedals / Reverb G2

Posted (edited)

Ok, so a workaround: the second time creating the mark point, use the dobber seq to cycle through HUD, TGP, and the other sources, back to HUD. Then you’ll be able to create a second markpoint.

It seems to be related to the (not a) bug in this video, where I got the workaround from.

 

 

Edited by Sandman1330

Ryzen 7 5800X3D / Asus Crosshair VI Hero X370 / Corsair H110i / Sapphire Nitro+ 6800XT / 32Gb G.Skill TridentZ 3200 / Samsung 980 Pro M.2 / Virpil Warbrd base + VFX and TM grips / Virpil CM3 Throttle / Saitek Pro Combat pedals / Reverb G2

Posted (edited)

[Latest Open Beta]  I find to create a 2nd (or next) HMCS markpoint, I have to undesignate (TMS Aft) twice to return the small circle to the HUD (FPM) first. Then TMS Fwd long again (Markpoint to HMCS), TMS Fwd to ground stablilize, then TMS Fwd again to designate the 2nd (or next) markpoint. Basically restarting the process. This is not so in the case of HUD markpoints where you can continue designating a 2nd, 3rd, etc, markpoint without having to undesignate first.

Edited by GrEaSeLiTeNiN

AMD Ryzen 5 5600X | Gigabyte RTX 3070 Gaming OC 8GB | 64GB G.SKILL TRIDENT Z4 neo DDR4 3600Mhz | Asus B550 TUF Plus Gaming | 2TB Aorus Gen4
TM Warthog HOTAS | TrackIR 5 | Windows 10 Home x64 | 
My HOTAS Profiles

Posted
10 hours ago, GrEaSeLiTeNiN said:

[Latest Open Beta]  I find to create a 2nd (or next) HMCS markpoint, I have to undesignate (TMS Aft) twice to return the small circle to the HUD (FPM) first. Then TMS Fwd long again (Markpoint to HMCS), TMS Fwd to ground stablilize, then TMS Fwd again to designate the 2nd (or next) markpoint. Basically restarting the process. This is not so in the case of HUD markpoints where you can continue designating a 2nd, 3rd, etc, markpoint without having to undesignate first.

 

This only seems to work if you come out of PRE mode first (switch mavs to VIS mode). If you stay in PRE mode, you can't get the HMCS to "activate" for markpoints.

Ryzen 7 5800X3D / Asus Crosshair VI Hero X370 / Corsair H110i / Sapphire Nitro+ 6800XT / 32Gb G.Skill TridentZ 3200 / Samsung 980 Pro M.2 / Virpil Warbrd base + VFX and TM grips / Virpil CM3 Throttle / Saitek Pro Combat pedals / Reverb G2

  • Recently Browsing   0 members

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