Tried block 50 this morning but could not replicate my results from before which was weird. The only thing I have changed is my controller mapping so maybe the issue lies there (using a x55 hotas). I tried several times to replicate what I had with the dropping to hud first time every time and just has not happened today. To be quite honest this has annoyed the living hell out of me as it was a genuine issue. Why it would not work for the first selection but would work thereafter tells me it was not something I was doing wrong in any way but a conflict or bug. Since the only thing to change is my controller setup, I will say probably conflict. Dont know… Just cant replicate it today.
Latest posts made by madmcphil
-
RE: Snowplow markpoint nightmare
-
RE: Snowplow markpoint nightmare
I will get an answer to that in a bit. Been flying the BLOCK 40 recently with zero issues of Mark Points. I need to get back in the 50 to know exactly if I just made SOI or if I tracked. I think on both it still fails to HUD but like I said…… it does this the first time you make a mark point. Thereafter it works correctly even if you perform other tasks and come back to the Mark system it behaves correctly. Just the first use of each flight!
-
RE: Snowplow markpoint nightmare
I will try to get to the bottom of this as when flying combat missions it is easy to “muscle memory” many of your inputs. I will take to the skies in a block 50 & 40 and map the differences in this. Although Leeches answer is correct it is not what we are facing here. I have been SEAD striking using TGP and FCR SP for a long time without this issue of being thrown to HUD on MARK points and loosing the very hard searched for SAM targets.
I flew in the Block 40 last night on a 3 hours SEAD mission (2 tanker fills, got to get better at those burnt almost 3000 lbs of fuel on reconnects ;P) and everything was working perfectly. I will mark down on paper exactly what is different in the 50 and any findings will be updated here. Like I mentioned before with the Block 50, it seems to be the first time I use the MARK point regardless of TMS up to SOI the FCR in SP mode, once you click that MARK button (after SOI and slew availability) it chucks you to HUD and drops your target! Even if you move the SOI to TGP the result is the same. Ater that forst annoying fail, all works fine thereafter. I always use SP mode. So for me its pretty critical to my missions as a SEAD specialist who refuses to use HARMS
Not sure if this is correct but in a real F-16 I think if no SOI is selected it actually defaults to a 0fly making it easy to mark current positions to handoff info to AWACS. Might be wrong on that. Not an F-16 pilot. Dammit!
-
RE: Snowplow markpoint nightmare
Interesting stuff…. Moved to a BLOCK 40 and everything seems to behave exactly as it should. Is that possible? Have not tried any other bocks than the 50 and 40 though. The 50 causes me the issues. Hope it helps!
-
RE: Snowplow markpoint nightmare
Even when the TGP is SOI I am afraid but like I said… it only happens the first time I select it…thereafter it behaves correctly
Also want to add I use TGP in my R-MFD not L-MFD. Haven’t tested it in the left!
-
RE: Snowplow markpoint nightmare
Your a genius…. CZ worked perfectly
The first time every time I use the Mark point it always sets itself to HUD… but from that moment on whenever I go back to Mark it remains on my SOI. Then once I have my markpoint clicking CZ brings me right back to target and doesnt slew miles off. Thanks again. I am back to being happy!
-
RE: Snowplow markpoint nightmare
I am too struggling now with Marking targets. In SP mode it is not doing as the manual says and instantly outs you to HUD mark. Okay I just cycle through to TGP mark and also put my SOI back to TGP… my issue is that the saved mark points are not saving the right coordinates. Often when inputting the new steerpoint I will see my marker on my FCR jump several miles off my target which I marked! Anyone else experiencing this. I am just about to do another flight tomorrow morning so I will test again but on both previous flights this has been the case. Making my SEAD missions next to impossible as it is.
-
RE: Windows 10
I have moved to Windows 10 with very little impact. I strongly suggest anyone who does move to Windows 10 to check that their hardware (mainly chipsets and motherboards and sound/graphics drivers have a Windows 10 supported driver). I noticed that everything works very well in Windows 10 but did have to update my motherboard and sound drivers to win10 drivers to make my Blue SNowball (microphone) work correctly. I also noticed my Saitek X55 Rhino needed reconfiguration as it was conflicting with my EDtracker and inputs were going a little haywire. Other than that I have had no other issues. Once drivers were updated it has been plain sailing. Below is a list of my hardware if it is relevant to anyone else…
Intel i7 4790k Devils Canyon
Asus Maximus Hero 7 Motherboard
Realtek 5.1 surround digital sound
AMD R9 390x Tri-x 8GB DDR5All of the above had new Windows 10 drivers ready to install.
Hope it helps.
-
RE: SEAD/DEAD Options for AAA and SAM
I had similar questions to you…… https://www.benchmarksims.org/forum/showthread.php?22341-Tactics-for-dealing-with-a-SAM-nest and this was the thread I started which has great info in it. Like others have said many ways to skin this cat……
I choose not to use HARMS and prefer the old fasioned Weasel way…Tobias did a YouTube video of the very tactic which I use… I am still perfecting this way and it relies on very quiet skies… but it does allow for a great and pre-planned (in-flight) attack.
If you are SEAD escort then this method takes too long to clear a target area so Harms maybe your best option then. But I choose to FRAG my own packages and create interdiction flights where I can take my time and choose my targets… I let AI do structural targets… I just clear the SAM nests in my own time. Search and destroy without any package time limitations.
-
RE: New X55 owner, some issues and questions…
I mapped my pinky slider on the rear of the throttle to open and down to close air brakes. The front slider on the throttle I used as a fast switch to dogfight mode but for DF slider I did use the software….