Hawkeye_UK Posted September 30, 2020 Share Posted September 30, 2020 Track files to follow from a MP test - however early feedback in VR after the first mark point there is issues with them not being placed at the point you are looking at. Always offset to the previous mark point by some distance. --------------------------------------------------------------------------------------------------------------------------- DCS & BMS F14B | AV-8B | F15E | F18C | F16C | F5 | F86 | A10C | JF17 | Viggen |Mirage 2000 | F1 | L-39 | C101 | Mig15 | Mig21 | Mig29 | SU27 | SU33 | F15C | AH64 | MI8 | Mi24 | Huey | KA50 | Gazelle | P47 | P51 | BF109 | FW190A/D | Spitfire | Mossie | CA | Persian Gulf | Nevada | Normandy | Channel | Syria | South Atlantic | Sinai Liquid Cooled ROG 690 13700K @ 5.9Ghz | RTX3090 FTW Ultra | 64GB DDR4 3600 MHz | 2x2TB SSD m2 Samsung 980/990 | Pimax Crystal/Reverb G2 | MFG Crosswinds | Virpil T50/CM3 | Winwing & Cougar MFD's | Buddyfox UFC | Winwing TOP & CP | Jetseat Link to comment Share on other sites More sharing options...
Hawkeye_UK Posted September 30, 2020 Author Share Posted September 30, 2020 Just to follow up in SP on my own test mission was working fine. @Bignewy another server member quickly hosted the into the inferno blank template purely for ease. It will be going on the main server tonight re A10 2 slots so will get track files then. Also despite the potential bugs its excellent seeing the HMCS on for SA. --------------------------------------------------------------------------------------------------------------------------- DCS & BMS F14B | AV-8B | F15E | F18C | F16C | F5 | F86 | A10C | JF17 | Viggen |Mirage 2000 | F1 | L-39 | C101 | Mig15 | Mig21 | Mig29 | SU27 | SU33 | F15C | AH64 | MI8 | Mi24 | Huey | KA50 | Gazelle | P47 | P51 | BF109 | FW190A/D | Spitfire | Mossie | CA | Persian Gulf | Nevada | Normandy | Channel | Syria | South Atlantic | Sinai Liquid Cooled ROG 690 13700K @ 5.9Ghz | RTX3090 FTW Ultra | 64GB DDR4 3600 MHz | 2x2TB SSD m2 Samsung 980/990 | Pimax Crystal/Reverb G2 | MFG Crosswinds | Virpil T50/CM3 | Winwing & Cougar MFD's | Buddyfox UFC | Winwing TOP & CP | Jetseat Link to comment Share on other sites More sharing options...
Stuka Posted September 30, 2020 Share Posted September 30, 2020 (edited) I can reproduce this in the freeflight instant action mission. Was that where you had it also? All other tests I did, were fine. Edited September 30, 2020 by Stuka Windows 11 | i9 12900KF | 64GB DDR4 | RTX 3090 | TM Warthog HOTAS | Saitek Combat Rudder Pedals | TM MFDs + Lilliput 8" | TIR5 Pro Link to comment Share on other sites More sharing options...
Mule Posted September 30, 2020 Share Posted September 30, 2020 If you slew the designate axis while in HMCS view it will drag a box away from the cross much like you can do in the hud. This will then be where your mark points go, away from the cross. You need to china hat aft quick to reset it to the cross. Fighter Pilot Podcast. Link to comment Share on other sites More sharing options...
HawgDawg4Life Posted October 2, 2020 Share Posted October 2, 2020 If you slew the designate axis while in HMCS view it will drag a box away from the cross much like you can do in the hud. This will then be where your mark points go, away from the cross. You need to china hat aft quick to reset it to the cross. This was the mistake I made when I thought the same thing posted in this thread. The issue for me was that I wasn't used to making the HMCS SOI separate from the hud, so I was looking forward and pressing the U key, but it was making my hud SOI not the HMCS, then when I moved the cursor, it was moving the hud cursor. Just had to train myself with the new stuff. lol HawgDawg4life of MSFlights.net [sIGPIC][/sIGPIC] Link to comment Share on other sites More sharing options...
Recommended Posts