Eldur

Well, it's still there on the dark theme, but I don't see the Like anywhere One thing that could be better though: When trying to link images, there's an option called "Retrieve remote file and reference locally" which is ticked by default, everytime. That makes the forum get the image and upload it on their webspace instead of hotlinking them. Might bloat up the thing after a short while. I'd set that to off by default if I could. Another thing that is bothering me is that we can't open up reply tabs to specific posts anymore, somehow the thing is kept in a single tab with middle clicking links not working anymore, probably because it's triggering javascript trash instead of being actual links. Absolutely not great in wholesome conversations when you want to reply to multiple things with a single post. Well, I guess it's the times where everything has to work on a cell phone nowadays. Only real advantage of that is that the letters are big enough for me to read because their sheer size. Still the contrasts, allegiant to the absolutely horrible Metro Design that Microsoft (Google and others alike) force upon us, consisting exclusively of 50 shades of light grey. Kinda funny how one of the big players pushes a new design scheme and literally everyone else is "parroting" that time and again...

I do have an e-mail address that I solely use at the broo and for job applications, nothing else. That one has the most breaches on sites I never even visited even once in my life. That exact e-mail address also was the first one I've ever gotten spam to and I had another one for a few years before that that was spam free even a few years later. Tells it all. And I'll stop writing about mankind and economy now before it might get too political, but that's the closest hint I can share And nowadays people complain about "the Zucc" selling their data...

I preferred the old one as well, and the new one lacks contrasts a lot, it's literally hurting in the eyes to read. The only upside is that there is a dark mode which makes it better at that point, but the overall layout still lacks for the reasons given already by others. If the design is being worked on (=customized), it might get better though. Anyone noticed the reputation thing is back in some form? Oh, and the vertical alignment of smileys (= images) is weird, they're not aligned to the bottomline of the text properly Edit: That's just in the editor frame apparently.

Thanks, wasn't aware of this. I'm a centerline guy. I can imagine, especially with gun runs that it happens when you have the thing on the left side, do a gun pass, where the TGP is aligned slightly to the right, then pull up steep enough that it begins ro roll up on the right sight until it hits the limit. Now if you happen to do a left hand turn, it will be locked up there trying to get to the other side. So basically, a GIMBAL ROLL> message means, you've got to turn right, not just roll. You need to get the target into the right hemisphere of your airframe so the TGP head can unwind there. And yes, the arrow is definately there, I've seen it after the beginning of this discussion.

Any reason for just taking one? I mean you still carry the whole dual rack... My favourite loadout, when applicable is: 1. - 11.: Fuel: max. 50%, if at all I mean, why carry all those draggy stores when you have the party cannon? They're all just nice-to-have addons, but certainly not needed Just too bad the thing tops out at meh-ish 345 canots on the deck. Published numbers are about 10% above that... (381 is the one I've seen most) even more so a reason to keep it as clean as possible. But if the mission requires, I mostly take APKWS, TGP + white smoke rockets as counter weight (they might come in handy at times), 65D or H (for FC), CBU-97/105 or just GBU-12. I try to avoid multi racks whereever possible as they drag up the thing excessively (that's a general DCS issue, just try out the Tomcat with 4 TALDS and 2x2 Zuni, it will be outrun by a clean A-10 even after shooting off everything, unless you kick in the burners, or try single rack Sparrows or AMRAAMs on the Hornet's wing pylons... literally becomes a bus with those) and you can't even get rid of them on the Hog.

Looks like the label masking stopped working, at least with the A-10C II, when that got released... is this something that needs work for each module by chance? Have yet to check with other modules though. Only other graphics mod is Mustang's shaders with Tonemap.fx removed in order to make this one work at all.

My attempt to get a better angle for checking six would be to have something like a snap view that turns your virtual head by let's say 60° in either direction (2 separate keybinds). When that happens instantly or with a very short fade-out-fade-in effect (as in HL:A blink teleport locomotion), it wouldn't cause motion sickness. From there on you could naturally turn around enough to see everything within reasonable limits. It's kinda like taking a snap turn with the right thumbstick and actually turning as well in a VR game, which does work quite well if you want to have a quick peek at something behind you. Haven't tried the DCS snapviews for that yet, as I'm not sure if they work at all in VR. But we should never mess with that 1:1 head turn rate.

Don't do it. It has the same problem the Gazelle has. Hard coded deadzone. Just that it is 5 times bigger, 50% instead of just 8%. I've heard that it ain't fun at all with that issue. As for the OP: If you had a graphics card (pun intended) and upped your CPU clock, you should be fine, but I wouldn't recommend anything above 1600px vertical res at all, and even those with that res might struggle a lot already. And do yourself a favour: Do. Not. Enter. Multiplayer.

Well the old menu was hardly visible in VR and it had massive problems with ASW artifacting. In that regard the new one is better... just waiting for the performance fix here and I'd really love to see other dialogue boxes being addressed after that as well. For instance, chat and scoreboard in MP are borderline useless in VR thanks to the light background and heavy transparency that we can't regulate at all.

To be frank, your system is way too overpowered to make this happen. EDIT: Didn't see the specs of the OP in the first place. Seems not to be directly hardware related, but my take on this is it happens way easier on lesser hardware. I get these VR crashes (HMD screen freezing up, going black, DCS instaclose, no crash log, no crash message whatsoever, sometimes the Oculusware crashing up at the same time) a lot and I always thought it was just the other random DCS crash that we always had occasionally. I even set up a pagefile to make sure my rig doesn't run out of mem, but it still happens. And it does happen a lot on my stone age rig. And since I always thought it was my limited hardware, I never cared to investigate or report, just tried not to load up too much within a session to some success. Going through F2/6/7/etc and F10, but especially chaning the airframe and even more so exiting the session and loading up another map without exiting DCS is a warranty for this to happen eventually. I always had that since 2.0 Alpha, but it literally went away completely when upping to 32GB, only to come back a lot harder than in ever was when going into the CV1.

The problem simply is that it doesn't "regenerate" by cooling down. If you fly all day long with the same airframe and rearm at times, you'll definately run into this limit and have to replace the pod or the plane (/repair if it received actual combat damage, otherwise the ground crew simply won't do it). Exactly the same as with the Ka-50 which's laser dies exactly after 30 Vikhr shots, even if you let it rest for 5 minutes everytime in between shots and an owa, owa an'a haaf in between the sorties while flying home, reload, fly back to target area. This has been tested by so many people extensively back then. It's just weird.

It clearly is a thing. When I tone it down until I can see the HUD well enough, the outside lighting seems to be decent as well, but I'm playing Dark Cockpit Simulator again, with pitch black consoles while the sun is shining into it from directly above at 12 pm. If I try to fix that, until I can barely make out the switches and knobs, and read the labels next to them, the outside is rather radiant and the HUDs are totally washed out, especially in the Hog. F-16 isn't great either, only the Hornet is kinda good still. TL;DR a long standing issue that got worse with 2.5.6 and never got fixed. It's especially apparent in VR HMDs that have OLEDs which can, as opposed to LCDs, actually display black. I simply guess the devs use LCD screens and calibrate the vibrance and colouring by what they see on those that aren't made for that job at all. But OTOH, well, most users do have LCD as well, so it adds up anyway. Noticed that happening a lot to all types of software when the first LCDs emerged into everyone's living room and I still ran a CRT even in 2011. I literally could see nothing on it since everything more recent was just pitch black. But when I nowadays play old games in DOSBox on my SIPS, they do shine like a nuclear explosion. It's a matter of hardware, and the software being accustomed to that. In short: When it comes to colours and especially blacks, LCD sucked in the past, it still sucks today and it will always suck in the future, period. It's not ED's fault every Tom, Dick and Harry bought those (I mean, even I did that eventually, but I was extremely late to the party for the reasons given, and my Eizo does have rather good blacks for an LCD, but still being miles away from CRT or OLED), they just had to accomodate for it to make the majority happy enough. And in instances where the HUD starts to wash out, I do have a lot more of an issue with that in the Rift compared to pancake. When it's rather well-visible, they almost match up.

The real fun thing is: Windows 95 was rather easy to set up. But I'm still crying in Windows 10 after almost a year + years I had it on secondary machines since its release. Learning ALL the modules of DCS completely without manuals, without tutorials and without YouTube or equivalents is easier than configuring Win 10 Early Access to personal needs. You don't have to google things for just to get the obvious "have you tried turning it off and on again?", "I don't have that problem", "why do you even want to do that? It's not meant to do that anyway" and "that has been answered a thousand of times, go use the search" answers without actually solving the problem eventually. It was so much easier back in the day... That's it. And do play around with the stuff if needed. Do make the mistakes, it's a sim after all. You still can try to be nothing else but absolutely perfect IRL, where you literally have to unless you want to end up being unemployed and crying in an empty wallet.

Nice to see a stable upgrade, wasn't expecting it actually. Just as a matter of fact, that'd me the 20th September of 2006 in Japan... or if you choose your file and folder names wisely to have them ordered correctly by date as well when they're ordered alphanumerically. Hello from the future, now present. TBA is 120% clear I guess you went with the way of writing out the month in some way.

Thank you. I'm aware of the fps steps... numbers I usually see are 45, 30, 22, 15, egardless of ASW on or off. Switching off won't work most times anyway, still have to find out what does the trick. I usually leave it on anyway as it makes feel the low rates smoother, although that comes at the cost of ASW artifacts. And at least I presume, having lots of units (especially active ones) just hits hard on my system since it's an old 3570k. I need to replace it, but that's still half a year before I can do that.

Your post literally has the highly probable answer in it. Multi Crew. Just see how far ED is with that today and it's easy to pin it down to that. Also 2007: http://www.simhq.com/_commentary/all_037e.html Easy. They implement all the switches, hats, rockers etc funtions as usual and it's the player's problem to get all that mapped. They just might want to have a default mapping for that, but that's certainly not the reason for a delay of the module at all. As as happened with the Tomcat, I'm 120% certain that someone will come up with a 3D printed selfmade unit shortly after an announcement, followed by either VKB or Virpil. Absolutely the least thing to worry about, really.

Crazy stuff. I actually have problems reading a single book already. This box I'm typing to approximately looks like this for me: Tried to simulate it with a glass bottleneck (for guitar playing) and some unsharpen filters. Think away the bottleneck ring and the refraction and it's pretty close, at least for one eye only. With both together, it's actually not as bad as they help each other out. But still a massive chore. And yes, I'm really flying DCS with that vision, even in VR, which actually is a lot easier than in pancake. I'm glad we have to option to put the Hammicks on both eyes in the Hornet an Viper and I hope that comes here as well, so we can either have the real deal or a decent substitute for the ones who're simply not allowed to fly IRL.

I guess we all have seen this movie. It simply takes time. Lots of it. Do the training with just parts of it, don't try to master it all at once. Concentrate on one, maybe two or three small things and get proficient with those. I haven't been flying the Hog that much back then because ED introduced some smoke effects back in 2012 that literally totally killed my fps (they were sub-1 when something went up) and I wasn't able to sim it at all for like 3 years and even then the performance was extremely subpar until the advent of EDGE for not just the NTTR in early 2018 with the first 2.5 OB. And I just do have one single hat here, having to do all the things with modifier keys. That's the true chore, but even that works, even though not as well as with a full HOTAS. I even got the TMWH, but I simply can't fly at all with that utterly sticky and grainy stick gimbal which literally prevents any approach of precise control surface movement (for every little movement I try to make, it kinda sticks in position and then jumps a bit, but more than I need until it sticks at the new position) which is a bloody shame for a piece of kit that sells now for a grand or even more... I wish I had a Virpil or VKB base for it at least, but I really want to have something FFB with actual FFB support that even the very expensive Brunner base doesn't come with. I once tried the full HOTAS though by throwing some force correlated Mavs from an orbit and it felt rather intuitive even with having it done before with a single hat and modifiers.

Just got the same problem... I don't get that circle which looks like a pipper with the min and max range triangles at all. Weapon GBU-38 selected, in CCRP mode, SPI on target, can see the wedding cake in HMCS and on TAD. There shouldn't be more to it, or I'm just a bellend here... And yes, Master Arm is on, having fired Mavs before in that very flight, sitting in pause ATM trying to figure what I'm doing wrong... Edit: Disregard, I just couldn't see the new LAR symbology on the left side of the HUD against the horizon at all in early daytime from different direction (there's a reason I opened up that HUD brightness thread, it just striked up on me again in IA-A10CII-Caucasus-Easy Russian Foothills.miz), the pipper style thing is obsolete now, at least in the II. After watching portions of Wagses LJDAM video, I noticed the change and went ahead to drop from a shallow dive so I could see the LAR and range data, bomb just came off fine and hit.

Well, there's only one way to improve it. Throw it away and write a completely new one. I still dont get why this happens: I join an empty server that runs TTI Caucasus, I get 11-15 fps in VR, 20 in pancake. If I go ahead and run that very same mission locally, I get 45 in VR and 130 in pancake. It's just utterly ridiculous. MP is literally unplayable for me because of that. I mean, wouldn't the real difference be that when hosting locally, my very own rig would have to calculate all those AI units while in MP that would be offloaded to the server? Clearly not the case when looking at how well or rather not so well it performs...

It's literally like looking to the 3/4 o'clock position and up with a VR headset and then having the friggen cable getting struck by the chair's wheel preventing you from turning your head back forward. I really do hate that, and it happens a lot. There's a reason I bought a Quest... but DCS' framerate literally is down the drink with that res on my stone age rig. As for that happening in the A-10C, I usually get that when doing sharp turns at higher bank angles or even the thing which is called an Immelmann (which he never did since the E.III totally was not capable to pull that off, it literally was a hammerhead) after an attack run or a Split S to defeat some SAM. When sticking to 30° AoB orbits, it happens very rarely, but it did happen to me in the past while doing so. In that case I usually just STBY the thing and switch to A-G again and it comes back to life. What I'm really wondering now though is: Why does that never ever happen in the Hornet or Viper or even the Harrier (I guess in that very case, some of you "know" the answer) with the exact same pod?

Exactly. Still a narrower FOV than 95% of the YouTubers use in ultrawide pancake though, just not 4k Well, I turn that up by holding the right face of that rocker for a few seconds on each startup while configuring the HUD. And IIRC it's maxed or at least nearly maxed anyway when you don't do that. Here's a shot I made in the A-10C II quick free flight in pancake as comparison, where it is much, much clearer. I do use mods, which are the 3dmigoto and Mustang's shader mod (albeit removed the Tonemap.fx so the first one works), and actually it's even noticably worse in VR without these mods thanks to the thick foggy haze that's been introduced some updates ago. Edit: Weird, tried the same mission now in VR (screenshot done with VR zoom this time) and it's OK there. So I probably messed something up myself or it was different lighting conditions or season that caused it (I did a 360 there with no big differences). I'll just see how it goes on subsequent flights for now.

I found the HUD extremely hard to distinguish against the horizon/sky, literally reminiscent of Channel Map update. Same for the old A-10C BTW. It's so dim it's literally useless. Compared to that, Hornet and Viper for example are night and day difference from the Hogs... Has this ever been touched since the issues with the Channel map update or is it just still WIP? I've also noticed still having lots of problems here with FC3 planes (especially Su-25 non-T), but that'd be another topic.

Found what did that. Mustang's shader mod has got a Tonemap.fx in it since v 1.04 and removing it does the trick. That's why I didn't encounter problems with it before. Same probably goes for Kegetys mod... might also work without that file, but in that case it contains most of the performance improvements I guess.

Title sais it all, I guess that goes without track. Regardless of which audio device is selected for headphones, everything comes from the main device.