derodo

I’m at 1080p...I just cant imagine how it would be on a 4K monitor then. After playing a few more times, I think the OP has a point; it seems spotting is harder after the last update (but again, maybe nothing changes and its just us).

Didn’t really noticed, but mostly because spotting in DCS is soooo fricking hard, I basically gave up. I enjoy DCS very very much, but I simply hate the fact that its almost impossible to pick anything up visually. I know there are countless threads about this subject; its been worked on since time inmemorial...and yer its still broken somehow. Maybe a little bit more with this latest update; I honestly don’t know. I just had to enable the labels as “DOT ONLY” because I’m just unable to pick up bandits once merged (SP) and I’m shot down 90% of the times. I can pick up the missile launch that kills me, but thats too late. Enabling the “dot labels” makes me GOD (again, SP) so it kind of ruins it too. Maybe going MP evens things out...dont’t know. There must be a sweet spot between the two, come on ED! I loved the “impostor” approach back in the 1.5 days; it really worked for me. It had its problems, specially in MP as it was resolution dependent; maybe it could be brought back just for SP? Don’t know again...just thinking aloud. Sorry about this mini-rant and not providing any useful hint to the OP...its just that its so frustrating... :_(

If it has to be just one, I’d go for the F18

Same here. Most of the times I order my flight to engage bandits they just say “unable”. The bandits have already shown on the RWR and on my radar, and the wingman has AA weapons. Maybe the wingmen cant see the contacts? Maybe they dont’t have their radar enabled...but the “radar on” command is missing from the comms list... Once we get in the thick of it, and merged, the “engage bandits” seems to work (not every time though). There’s definitely something wrong, or we are missing a key step at some point...(I’ve made countless silly mistakes before, so this might just be one of those times)

I just came across this same behavior today, as I started practicing A/G. When using the Warthog throttle's mini stick button to designate the target on the HUD, the axis are so sensitive that it's almost impossible to designate anything; as soon as you depress, the designation point moves around incontrollably. I tried fine tunning my curves/dead-zones, but I just couln't find the sweet spot; I went up to a dead zone of 40 with a pretty steep curve, and it was almost usable like that; but I just decided to use a different button on my HOTAS to designate. Don't know if the developers are reading this, but wouln't it be reasonable to just ignore any TDC axis input while the depress button is being held? That would solve the issue without any side effects wouln't it? And it would also solve this same issue with the TDC axis for the radar, which is easier to manage via curves/dead-zone but it's also there. Just my two cents.

As most people already said, it’s just PRACTICE. Nothing else. Of course you will need to set your shit up; curves, learn formation flying, etc. But you will fail misserably the first time you try. And the next one, and the next...and a few more; and at one point it would seem you almost can can connect for 5 full seconds...and then you will fail misserably again...you will want to throw the joystick against the monitor. But you will succeed eventually. I can’t say how it happened to me; it was just like that. I thought I will never be able to do it. It seemed simply impossible. But now I can. How? Don’t know...honestly...just countless tries until it just worked. So for alll of you guys that are still strugling, just keep at it. Don’t give up. It will come. Just keep at it; if you get stuck or too frustated, just let it go for a while. Then try again a few days; you’ll see the difference; and at some point you will simply be ale to do it naturally, without that much effort. I’m not an expert at it, not even close; in fact I kind of suck at it, but I can really see the difference between my AAR now and back then; and it just keeps getting better. So... TL;DR PRACTICE :)

Yup. That dit it. Thanks!

Hey there, Is it me or is the radar altimeter not working after a cold & dark startup? I must confess I didn't read the NATOPS, so it might just be me not flicking a switch or something. I tried following all the intructions in the cold & dark training mission and it's the same. I'm able to start it up, taxi & take off. Everything seems to be fine, but the radar altimeter. Once airborne, switching from BARO to RADAR simply makes the blinking B to appear next to the altitude reading on the HUD, but no matter how low I go, it keeps blinking. When I start a mission already in the air, the radar altimeter simply works; once I get below 4000ft, the blinking B dissapears and the R shows up. Any hints? Am I missing something?

The quick link to the encyclopedia would be nice. +1 to both things :P

+1

You might want to check out some of Baltic Dragon’s campaigns. I only played the stock one that comes with the Mirage, and it’s just amazing. I know there are some other great campaign developers out there; I only played (and loved) Baltic’s though. As others have said, I suggest you take a look at the reviews on youtube so you can make yourself an idea of what to expect.

Ok...my fault of course. Turns out it starts working as soon as you're airborne. I think it didn't in my previous try but...seems to be working now. Nevermind :P

Hi there, Is it me or after some of the updates the countermeasures system doesn't work after a cold & dark start? When I'm starting in the air, it just works. But I can't manage to get it going when starting up the aircraft on my own; even following the steps from the training mission. Everything seems to be up un running, including the EWS. But the ALE-47 in the middle of the top row of the EW display is dashed out. I flicked the countermeasures switch up & down just to make sure it's ON, but no joy. Tried looking up in the forums but saw nothing about it; I'd swear it just worked right away in previous updates. But maybe something changed and I'm missing an additional step. Any hints?

I think it happens if you disengage the parking brake WHILE it’s still aligning. That has always been the case for me. So now I just keep it on until the alignment finishes, and then, I disengage the PB. That’s my procedure now...don’t know if it’s real though, it just works. I assume it will work the same if you start with the parking brake off, as long as you don’t mess with it while the alignment is in progress. By the way, when that happens...is there a way to reset the INS so it can start from the beginning? It’s not a problem for me anymore, but I’m just curious...I tried shutting down and restarting the hornet, but the INS alignment stays blinking at 99.9

Nice explanation. That stabilization thing makes a lot of sense as to what I might be experiencing. It only can get better then. Cool :) Enviado desde mi iPhone utilizando Tapatalk

Well....yeah I kind of expect that, or can understand that might happen. The point is I'm not making hard maneuvers. I said crank, yes. but after seeing what happened I tried the same just turing gently to one side. Same effect. EDIT: mmm...after messing around a bit more, it might be just me. Seems radar beaming is *real* in the Hornet; or so it seems. It's way way more sensible and prone to loose lock depending on how you "crank" in relation with the bandit; it certainly didn't happened with the FC3 aircraft.

I thought about posting a new thread, but this seems to already address my concerns. I'm too finding the F18 radar way "different". I'm used to the Mirage and SU-27; and apart from the radar taking longer to lock-on and being harder to master, which is perfectly fine, I'm having a few more issues with it. The biggest one being...it's almost impossible to crank left/right while maintaining lock. Once I have a lock, if I (slowly) maneuver the aircraft to either side, as soon as the target box gets out of the HUD and starts flashing, the lock is lost within a few seconds; even if the beam is way far from it's maximum azimut and I try to roll back to get the box inside the HUD. This behavior seems to be more pronounced against head-on BVR enemies; i.e. it does not happen when locking a cold friendly aircraft, you can crank left/right and keep it locked near the azimut limit, then roll back in and still get the target box back in the HUD. Maybe it's 100% real and that's the way it is...or maybe it's just WIP (which I hope is the case, because technically, it IS WIP :). Anyone else experiencing this same cranking/lost-lock thing? Maybe it's just me...

Hey, it’s early access. These are the things we are supposed to be reporting...aren’t they? We (I) knew what it was going to be at this stage. I’m pretty sure the devs will find their way around all of these glitches. So far it’s been just great and I’m loving it. Glad to be part of it somehow. Cheers! Enviado desde mi iPhone utilizando Tapatalk

You’re right. There’s a “Special for Joystick” section with quite a lot of switches for warthog-like mappings that are working just fine (like the “Probe Control Switch - EXTEND/RETRACT” or the “Speed Brake Switch - EXTEND/RETRACT”). But unfortunately, the “Master Arm Switch - ARM/SAFE” it’s not there. I think it will eventually be as ED continues with the development; it seems it’s just been misplaced and is still not working correctly. I hope that is the case... Enviado desde mi iPhone utilizando Tapatalk

Yup. Same thing here. Going from “up (auto)” to “down (full)” doesn’t work. It leaves the flaps switch in the “middle (half)” position. Enviado desde mi iPhone utilizando Tapatalk

Ok. In that case, the only thing I noticed is the auto-acquisition modes might take longer to track than what we are used to in other modules (FC3, mirage). Never tried the wide-acquisition, but vertical scan takes around one second to lock-on once you place the bandit inside de vertical bars. Boresight mode is almost instantaneous tough. By the way, it’s not the cage/uncage button I was referring to in the previous post, but “Throttle Designator Controller - Depress” (that’s the exact name). That’s what you press to lock-on whatever is inside de TDC box on the radar screen. Enviado desde mi iPhone utilizando Tapatalk

I played these two days on the Caucasus and everything was fine regarding target lock/STT. Just in case, the binding for locking an enemy is “Throttle designator - depress” (can’t remember the exact name though, I’m at the office). Every time I pressed it within lock-on parameters it worked. Enviado desde mi iPhone utilizando Tapatalk

3 way switches? I know; that’s why I assumed those bindingd would work (the speed brake does). I’m refereing to the bindingd that specifically mention 2 states, like “Master Arm Switch - ARM/SAFE”. There are other simple bindings like “Master Arm Switch - ARM”. So I assumed the first one was meant to be used with warthog-like switches (ARM/SAFE would set master arm on as long as the button is pressed).

Hi there, Don't know if this might be a bug or not, so I'm asking here just in case it's me being dumb (as it happened a few times before). Are the "3 way switches" working as they should? I mean, there are a couple bindings that I think are supposed to work with the warthog throttle, like: Speed Brake switch - RETRACT/OFF: this one works as expected; I mapped it to the fwd position of the warthog speek brake. So as long as the button is "pressed" the aibrake retracts, and if I return the speed brake to the middle position (no button pressed) the airbrake simply stops wherever it is. Exterior Lights Switch - ON/OFF: this one I assumed was the same, and mapped it to the warthog exterior lights switch fwd. But it simply works as a regular button; meaning it will toggle exterior lights every time I move it fwd, instead of keeping the lights on until I return it to the middle position. It's not a big deal, since I ended up binding the lights on and lights off to fwd/aft...but it sounds like it's not right: Master Arm Switch - ARM/SAFE: this one is the same; I tried to bind it to any of the warthog's switches, asuming I'd go ARM when the switch is fwd (button pressed) and back to SAFE when siwtching it aft (no button press). But again, it just works as a regular toggle, so I need to flick the switch twice if I want to go from ARM to SAFE or vice-versa. Any hints?

Oh...jeeez...did I read the whole changelog I didn't see THAT?!!? Well...yes. That's exactly what happened. Looked up and search the forums in case it was already answered...but dind't have the brains to double check the changelog...shame on me.