derodo

I understand each aircraft has its own limits, but I still find it weird that I can't lean my head forward past the stick on the Albatros (and I think I could do that before). Anyway, your guide on how to alter those settings looks promising. I'll give it a try. Thanks!

Yeeehaa! Nice! Thanks for the heads-up

Hi there, I noticed a while back, that I can't move my "virtual head" past the stick. Not with TrackIR nor using CTRL+SHIFT+*. I'd swear I could before; as in many other aircrafts, I could move the view point way forward, almost until it hits the front dash; but that's no longer the case. It's not a big deal, but it kind of makes it harder to reach the flip switches that are just behind the stick. Is this a bug or is it meant to be like it is now?

That's not what I meant. I was referring to the UI slider named "Curvature", whose value normally goes from -100 (left) to +100 (right) regardless of "slider" mode. When I assigned my HOTAS axis and went into the Axis Tune window, that UI slider only went from 0 (left) to 100 (right). Anyway, after restarting DCS, everything went back to normal and I was able to set the Curvature to -18 on my axis in "slider" mode so...everything is OK and I'm happy again :)

Hi there! Any news yet? Hope it's almost done by now. I'm really eager to try it out!

Ok...I checked again after restarting and guess what...it works :/ Now the curvature slider UI reads 0 at its center. But I swear last time I played it read 0 at its leftmost position, so I could only go positive to the right, but neger get below 0. Well...case closed then. Weird! :)

I'm copy-pasting this from an old thread I started on the 1.5 Open Beta forum as it's about a weird behaviour I'm still oberving (maybe it would be better to just move that one over here, but I guess that can only be done by the admins). Ok so here is the thing: Sometimes, don't know exactly when, the UI gets irresponsive. I mean, every click I do "outiside of pure gameplay" takes a long time, and somtimes the "rotating windows circle" appears to signofy the app is kind of busy. "Outside of pure gameplay" means that clicking on the 3D cockpit elements is just fine, and flying around is also fine. No FPS drops. But when hitting ESC, once the menu appears, anything I click takes way too long to complete. Going to "customize controls" and clicking on any of the controls for example, takes several seconds until it gets highlighted. Writing anything in the new "search box" is the same; takes a few seconds for each characer to appear. Once this behavior starts, it can also be observed in the mission editor. Anything you click takes much much longer than usual. Even saving the mission. Or clickin "fly". I'm pretty sure it's related to the FC3 module (or some of its aircraft), as it only happens when I fly the F15 or the SU-27 (which are the ones I usually fly with). This only applies for sure on 1.5.x (and it always happened to me since 1.2.x); it might also be the case on 2.x, but I can't tell for sure because I don't usually play 2.x. Is anyone experiencing anything like this? It's no big deal, but its quite annoying, to the point that I often rather restart the game when it happens, because three clicks usually take more time than exiting and starting DCS again :(

I usually fly the 1.5.x, but every now and then I check out the 2.x to see how things are prgressing; so yesterday I tried the last update, and it seems you can't tune an axis as a slider with NEGATIVE curvature. Is that the way it's going to be? Or is it just a bug? It seems you can only set positive curvature now. I just recently started assigning the view zoom axis to one of my thumb sliders, and I like to set it up like that, so the neutral position applies a comfortable standard view. I tried playing with the "custom" tuning, and kind of got it but it's...well...a bit weird.

Happened to me las time with the Hawk module. It felt weird so I just canceled the activation process, let DCS finish launching (the module was not working) and restarted again. Everything just worked fine...seems DCS just got mad on the first launch and the second was the charm :)

Just in casy anyone is reading this, it keeps happening...I've made some more tests, and I'm fairly sure it only happens when flying FC3 aircrafts. Maybe it's only related with custom created missions; but it's quite easy to reproduce. Just create one mission to fly an F15 or SU27 (those are the only ones I've checked). Start it up, fly for a while, and then quit or finish the mission and get back to the mission editor. Once you're back, this "thing" just happens; it's quite annoying. No big deal, but really annoying I usually quit DCS and restart, as it takes roughly the same time as clicking 3 o 4 times on any almost button on the UI. So in the end, I save time just quitting and launching again. Never happened when flying non-FC3 aircrafts.

So isn't there any workaround? Or at least something I can check to prove it's actually that? By the way, It never happend while playing X-Plane... Though in that Sim, I can enable/disable the TrackIR at will with a key-press; the blue light comes off and on again each time. And I do it quite regularly while flying as I switch views. Could there be a way for doing that same thing in DCS? Something like a "TrackIR reset"?

I'm aware about Windows 10 and USB devices. That was the first thing I checked; I followed someone else's guidelines and changed a setting in the OS to avoid unused USB devices being "put to sleep". But I'm still having the issue. I can't really tell when it happens exactly; mostly everytime I launch DCS for the first time. I have the TrackIR app launched; upon DCS startup, the TrackIR light goes blue, and once DCS comes to live (it takes quite a while), the blue light just goes off. I think I never saw it going off; as I always fail to keep an eye on it all the time. I think it's a little while after DCS starts; I check the light is still blue, then go to the mission editor, load a file, click "Fly" and when I look again as the mission loads, the light is already off. Everything happens quite quickly, but it's not always the case. I don't know what it depends on... I'm using Windows 10 + Intel i7 + 8GB RAM + AMD HD 7800 2GB + X55 + with TrackIR 3 Pro with vector expansion. Can't really tell when it started happening either, but it certainly worked OK before. Maybe it's just Windows 10...as lately I've also seen "device unplugged" with my X55. But in that caseeverything gets back to normal automtically once the "device plugged" shows (and that is almost inmediately after the "unplugged" one)

Something has changed indeed. But there are still issues. Most of the times, when I load DCS for the first time, it takes quite a lot; and while it's loading, the TrackIR "blue light" siwtches off; meaning it's no longer connected to DCS. That also happens if I stay too long in the mission editor for example. Once that happens, the only thing I can do is exit and restart DCS (the second time it takes way less to load, presumably because of windows file cache). Some other times, rarely, I experience the same behaviour while playing a mission. I can see the "TrackIR device unplugged/plugged" messages, but the TrackIR "blue light" doesn't light up again... It's quite annonying, and I'd like it to be fixed (as it didn't happen before). But I can live with it...

I noticed this same thing a little while after v1.5 was released and posted about it, but the topic didn't get momentum :P I find it quite annoying. Not a big deal; can live with it, but it would be cool if it went away.

Hi! Same problem here. I started having this issue a few days ago. Don't know if it's due to an OS or a DCS update. I'm sure it didn't happen before. It's quite annoying. I think it has to do with power saving as Coug4r suggests. I'm trying changing that setting now; for me it always happens whenever I stop doing "things with the head tracking" (spend some time in the mission editor not warning the track-clip, stop for a while and go to the bathroom, etc).

None for me either

Sorry for the necromancy, but I just started doing some night flying and I also found this thing about runway lights quite annoying. I guess t's some kind of a bug or work in progress; as it makes no sense to me that I can clearly spot the city/village lights but I can barely see the runway when I'm even below 2000m (above 4000m it's freaking imposible to spot the runway). Not to mention when the HDR kicks in...even if the sun is already below the horizon, there are certain orientations that make the sight literally turn black. I'm attaching a few screenshots just in case (believe it or not, in the first one there's a runway outside the window :))

Just guessing, but I think the visibilty range is more directly related with rendering. You can have a lot of things preloaded (in memory) to save load-time hickups during gameplay, and have a low visibility range so things far away in the distance do not get rendered to save some GPU and prevent frame-rate from dropping too low.

I think it stands for Target Designator Cue...or something along those lines. So TDC slew are simply the set of commands that you use to slew the target designator around (usually up/down/left/right). Depending on the aircraft, it might be a tiny box in the HUD, or a cross in the MFD...basically a visual cue somewhere indicating what/where you are pointing at.

Mmmm @Hadwell ... you know what? Actually that thing you mention might be worth it in the end. Being able to lock a hostile when a friendly is too close in the HUD and makes it almost impossible to lock the bad guy manually. Haven't tried that before...I'll make a quick test when I get home. ¿Does it automatically snap to the bad guy? Or do you still need to move it around until it ends up snapping on the bandit?

Sorry to revive this old topic, but I've flying the SU-27 recently (and enjoying it quite a lot!), and it also seems to me that TWS is kind of useless. It provides the exact same information as the regular scan mode; you can see all targets aspect, altitude and speed hints on the MFD. The only difference is that the target designator box sticks automatically to the target once you move it close to it, and follows it without locking. But...it doesn't provide you with any more info. I was expecting altitude and speed readings for the target the box is over on top of the hud (like in STT), and aspect on bottom left. And it auto locks-on once the target it's tracking gets into launch parameters, which might be OK, but considering it's just a click away, it's not worth it most of the times; as you will reveal your intentions too soon... Don't know...I was just curious to know if that's the intended behavior or not.

Same here. Thought it was my fault (I played a bit with the tree visibility range) but it seems it was tha latest patch. It only happens on some trees though...most of them, but not all of them (I'm attaching a scrennshot just in case). With the F2 view everything is just fine (gorgeus I'd say :)

+1 Yup. Same here.

By the way, since it's somehow related...when are the lights of the airports turned on? Aren't they supposed to be always on (I don't really know, just guessing)? Maybe it's me, but there are a lot of situations near dusk, when it's pretty dark outside, but the runway lights are off (or so they seem). It's not night, and the runway is visible of course, but it looks like the lights should be on anyway...

Hi, Is it possible to hide the training texts? Now it's just the opposite of 1.2, where they dissapeared quite fast; now they stay way too long :) If anything, I'd prefer it like this; but it would be nice if there was a key to hide/show them at will. I searched the controls in-game, and the forums, but couldn't find anything (looked for "hide", "text" and/or "training").