Sandman1330

Affirm.

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

Still having this issue. It seems to happen more frequently if you forget to change to pre mode before boresighting. If I've forgotten to change to pre mode before boresighting, nothing I do can get it out of vis mode. Wpn page TMS aft short doesn't work in this case. Edit: And I just tried to reproduce it to create a track.... and couldn't reproduce it. At least this time wpn page TMS aft short worked, but it most definitely didn't last time. I'll keep trying.... Edit 2: Now I can't reproduce it, of course. The original mission was a complex mission with much scripting so a track file from that isn't ideal...

Unfortunately you’re interpreting Doppler filter incorrectly. Right idea, slightly off on the application. The Doppler filter exists to prevent ground clutter from showing on the radar. Therefore, it filters out anything with 0 relative speed to the ground, not to the aircraft. For example, if I’m travelling 300kts ground speed, anything with 300kts closure to me will be filtered out, not something with 0 relative closure to me. The big mountain in front of me will be coming towards me at 300kts, that’s what gets filtered out. The aircraft in front going the same speed as me will have a different Doppler shift from that mountain, and will be seen. If I want to hide in the Doppler filter, I “notch” the other guy’s radar by putting him at 90 degrees, not flying towards or away from him, creating 0 relative speed in reference to the ground. It’s as if he’s approaching a large ridge line perpendicular to his path. That ridge line is filtered out by the Doppler filter. If I fly along the length of that ridgeline, I’m creating the same Doppler shift as that ridgeline and I’ll be filtered out. It is a bit more complex then that when you start talking about look up vs look down, etc - but that’s the gist.

I disagree, I prefer hot starts since I do cold starts for a living - but hey, it’s a game and we all enjoy how we want! As for your HOTAS, I used to have that problem. While you are in the select role page, give your throttle a bump forward then back to idle, this input should sync your HOTAS to its actual position. If it doesn’t work, try changing the setting in options “sync HOTAS at mission start” and try it again. If neither of these work feel free to PM me, I’ll dig into my actual settings and see if I can figure out how I rectified it.

Just ran into this myself. I don't have a track but I can confirm - used JDAM, then gun landed way high in reference to the pipper.

Holy thread necro! Thanks for the reply and the PM, the issue is long solved. Cheers!

I noticed this was missing too. I did a battlefield tour in 2006 and visited many of these places, and it struck me that many were not included in the map (see my post on Vimy)

Are there any plans to include the massive Vimy Ridge memorial near Arras and Lens? It was completed in 1936, and is large enough to be seen for many miles. As a Canadian, I’d love to see it included in the map. Plus it would be a very good navigational reference!

Is anyone else still having issues with this? I am, though I'm admittedly a bit out of practice, it seems I can't get a solid pass (according to the LSO anyway). If I'm reducing power in close, it's to keep the ball from going high, not to land... *Edit - So I decided to take some video with the control indicator up so I could self debrief, and perhaps post it on here for other's opinions on whether there's an issue with the grading... I did about 4 passes while recording, and nailed all of them. 3/4 wires, all _OK_, even one where I'm pretty sure I DID EGTL! Maybe I'm just rusty.

Phoenixes work OK at longer ranges, but if you engage at shorter range (30NM-ish), they don’t even seem to guide, even with valid tracks held throughout.

Awesome tip! I just tried that and it worked great. Still only got 1/6 phoenix hits though...

Oh yeah, I understand it’s not controllable on your end. I think Heatblur is well aware of the Phoenix issues, but it’s actually DCS core that controls the missile API. There’s supposed to be a fix in the works. It’s not a big deal that the mission showed fail, I still got all the “win” dialog and was able to just hit skip mission to progress. One missile did get super duper close, the CIWS got it, but maybe the ship took a tiny bit of damage from the close by explosion of the missile, and perhaps that’s all it took to trigger

Check out this track - 6 pheonixes, not a single one guided. Something is definitely not right there. Useless pheonixes tacview Did the mission again, fired from farther away, got 6 kills. All backfires were destroyed (got the voiceover for that). However, I got the "ship hit, mission failed," but no enemy missiles hit. A few were fired before the backfires were destroyed, but none hit the ship, the point defence got them all. That tacview is also attached. Ship wasn't hit tacview Finally, it's a bit annoying to not be able to prioritize targets in TWS. The MIGs are always "stealing" your priority 1 and 2 slots, so you have to "waste" 2 phoenixes on them before you can start engaging the bombers. Again, it's a Heatblur / DCS problem, but still...

Same. It worked once out of 10 or 20 tries, but consistently will not work (pressing backspace, which is what I have bound in controls for this).

Cool, as good an answer as any, thanks!

So I spent some time scratching my head, wondering why my phoenixs never tracked anything on those missions where we were given one of them. I would fire it in TWS at 25-30 miles. Then I realized, it's the ACM cover of course. With the cover up, the missile is pitbull off the rail, and too far away at 25-30 miles to acquire a target. So my question: Why do ACM cover up on the FENCE in (per Jester's checklist), when you know you'll likely be starting the engagement BVR? I can understand flicking it up then down again, as it's an expedient way to set gun rate high, SW Cool and Missile prep. But to leave it up seems counter productive. Is there a reason I'm missing, or is it contextual based on the type of engagement expected, where maybe that one checklist item should be left out in certain missions?

I concur, I enjoyed this campaign as well. Although I never did manage to spot a wildcard without using labels or peeking at the F10 map, despite having my head on a swivel so much I thought it would twist off! They just appear too quickly for me, but I'll choose to blame it on limited VR resolution The last "mission" was super cool too, what an imaginative way to end the campaign. And kudos to you guys for using the actual Nellis club as the venue! Now on to Fear the Bones.

This made a huge difference on my 6800XT as well. Without that set, I had terrible stutters, even at low settings and high frame rates.

Some of us do much prefer the controllers. I hate the mouse, the pointer moves with your head so you have to hold your noggin perfectly still while using it, and it’s one hand only. I have a controller beside each hand so whichever one is free at that time I can use. Increases immersion for me, but everyone has their own personal preferences. As this thread indicates, controllers have their downsides too.

I've found you just need to be very careful before hitting that Windows button (my sig may show Rift S, but I'm on a G2 now). I try to keep my controllers awake by moving them every few minutes, but sometimes one does go to sleep. I give it a few seconds to make sure it's gone to sleep, then press and hold, ONLY ONCE, the windows button. The controller usually comes back online without going to cliff house. If you hit the windows button again, it'll take you to cliff house, so just press and hold once to wake up the controller. So far it's worked OK for me. Try as I might, I haven't been able to find a setting to stop the controllers from going to sleep, it's a PITA. It's about the only thing I liked better about Oculus.

That’s probably it then. Cheers!

Huh, ya know what? I may have released the parking brake early. Was short on play time and might have been trying to multitask (letting the auto start work while I did other things) Does releasing the brake automatically stop the align, or does the aircraft have to move?

Hey team, I'm having an issue with the INS align getting stuck. Using auto-start and time compression, the align just gets stuck at some point before completion. It doesn't happen all the time, but happened 3 tries in a row on this one campaign mission. Track attached (too large for forums): https://1drv.ms/u/s!Ascm8Kmu7NR0g_5QsJ17H8XNVg3PYA?e=mbCJhn

Well I’m learning plenty of lessons!