Sandman1330

I’d love to see those boundaries to the map, but that would be huge. It’s 1200km from Kabul to the gulf, by comparison the PG map is 800km from the eastern portion of the detailed area (tip of Oman) to Kuwait, and Kuwait is not even included in the detailed area. There’s only about 500km of detail in PG, and that’s the largest map so far. I do think it’s possible, and would hope to see, a detailed area from the Kabul area (maybe up to the Hindu Kush) to Kandahar, ending maybe at the Registan desert in the south. It could then be a low detail area down to the coast to allow for those missions off the boat. Better be proficient with AAR though, that’ll be a long flight!

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.

Serious about what? We’ve already identified I was wrong and that’s an FW190.

It’ll come

Possibly, but all I’m trying to say is the teaser video is just that - a teaser. They’ll release a much more detailed roadmap in a couple weeks that will provide much more info on the things teased today, and cover things that weren’t (like performance improvements). I am waiting for those improvements as eagerly as anyone else! For reference, here is last year’s news, released in early January: https://forums.eagle.ru/topic/254461-official-news-2021/?do=findComment&comment=4532354

From todays video, it looks like Bagram will likely be the focal point of the map, likely as Far East as Jalalabad and maybe Peshawar. I do hope it goes far enough south to include Kandahar. Whether you play out 80s scenarios or modern scenarios, Kandahar was pivotal in both conflicts. The corridor between Bagram and Kandahar for a couple hundred kilometres either side will make an excellent area for ops. If they want to go as far as the Hindu Kush though, this will make for a huge map. It would be nice to see Helmand province included as well, but that may be too big…

It’s hard to showcase that kind of stuff in a trailer video. They usually release a new text roadmap a week or two after this video, so watch that space for updates I think.

I thought the cockpit looked a little wrong. Thanks for point that out, too bad.

Mitsubishi Zero. AI I assume, probably linked to the WWII version of the Marianas.

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.

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).