Eldur

Sweet Celestia.. if that's all just your bonus, it's massive. I have that amount for fun things in a time frame of like 2-3 years... but before getting into 1.7 here, go ahead and get into VR with a sweet G2 and a 3080 or 6800/6900XT and do yourself some other favour of choice with the rest of it.

My English must really suck after seeing the comments here. What I was going to say is that literally all of VR sucks because you can't zoom as in DCS, simply because it's utterly hard to read things in CV1 and I keep pressing the A button which is for zooming in DCS also in other games or just environments like Steam VR, just to find out rpeatedly that I can't zoom there. So basically DCS is what's normal for me... same for the grip button. You have to hold it in order to be able to click things in DCS and I keep pressing it in Steam VR or Oculus Dash all the time when I want to click something

It's probably exactly that. It's under View Extended and called "Toggle tracking fire weapon". This will immediately switch to Ctrl + F6 view when you shoot something and with that switched on, you can even use it to follow your gun rounds with the F6 views can't do. Pretty sick feature for videos if you ask me and it's been there since Lock On at least, but it's everything else than widely known. Check the info bar in outside views to see if it's on ATM, shown by a "+" just preceding the F# label there. It "fixes itself" by simply loading another mission as such things reset on every load if you didn't know how to switch it and accidently turned it on.

That happens on every F coming from F10 already. And well, I knew the OP's thesis already when 2.5 was new and it literally obliterated the 3.5G of my 970 even at the very lowest possible settings (looking almost like Flanker 2.5) on an empty Caucasus miz back then. That card was hopelessly deprecated from one day to the other. And TBH, since the 3090 with a price tag in excess of 2000 (yes, in Europe that is, nVidia geopricing politics just suck) is simply too much for my wallet. I'll be looking for 3080ti/S probably with 16+ GB, hopefully. Or maybe switch sides to REDFOR and get a 6900XT or maybe just a 6800XT. But I'll be getting rid of that 3rd gen bottleneck first.

It's simple: I don't like - or shall I even say the h-word? - that you can't zoom in with the A or any other button outside of DCS. I constantly try to in other VR titles, and it smacks me hard everytime especially since it's very much needed more than often in the CV1. Another thing is I keep holding the right grip if I want to click something...

Dark Cockpit Simulator evolved into Digital Cow Simulator I'm also happy with the overall patch quality. I was a bit sceptical in the beginning, but it really seems to work out well.

I've seen timeout messages not just once. I'd be glad about 10 seconds actually now. Could hardly be worse. As for the changes, I've set up phpBB boards from a clean install, installed a custom style, changed a ton of CSS things on that including changes that weren't possible via the interface, set up all the permissions, made custom graphics without even knowing how to (total GIMP noob here) and even installed feature addons like file uploads within like 3-5 days. Noone can tell me this takes weeks or even months. And that was me knowing literally nothing about php back then, so I even had to skim s-loads of badly written documentation to just remotely understand what I ought to do. Whoever does this with the pace that we can attest here, isn't actually working on the thing period. I mean, we've been witnessing like one obvious change a week now. If that would have been my job at any company, I'd have been fired within the week the update was done without getting paid for any work I'd have done in that week. Of course, if noone is exclusively dedicated to that, and it's not a priority task, it can easily take what feels like ages, but then it's an issue of distributing resources, but you can't blame the programmer. In the end, we'll just have to be patient.

I did that, no change though. But after quite some testing, I kinda found some "killers". It clearly doesn't like something about Mustang's shader mod, but I ran 1.03 quite long without problems, so it's something that he added with the newer versions, but I jumped to 1.10 directly from that one. And it still works with the older one and that one still seems to fix the foggy haze for me. So I'll just use that one for the time being and ask him if he could do something about the issue. I've been playing around with the labels themselves recently. When nothing else kills the masking, not having just a dot (as in period, the thing you end a sentence with) will break the masking. I tried some other ones like ° just to have a bigger do(nu)t or even just letters like v to point at things I struggle to see (Rift CV1 is very tough on visibility). All those don't get masked. Don't know about the default ones with range, type, name etc though. BTW Global Cockpit illumination on/off = absolutely not affecting the label masking at all. Might kill some other features though, but I haven't noticed anything not working because of that, I just use the mod for masking the labels and getting rid of baked reflections.

Thanks for asking. I will try again with the new DCS version, and yes, I had the menus appear. I still have to see if Mustang's shader mod might cause problems even with the Tonemap.fx removed from it. I should also try to switch label masking off and on probably. And play around with the labels setting in DCS. IIRC I had it set to full for most of the time, but edited them to be dots only anyway shortly before ED implemented the dot only option that I switched over to a while ago. Maybe that's causing the issue. And thanks for fixing the reflections there, it's really weird especially in the Ka-50.

Now you got me interested... still having the Mustang shader mod in there because of that, I guess I'll have to try without now as this was a major game breaker since the Channel map release. Now if ED would add the "remove baked in reflections" option for all their modules (16 and 18 have it already) and make the labels invisible behind your canopy frame / airframe, I could fly without any mods except for my own control changes.

Am I dreaming? This is one of the very small things that have so much impact actually. Was very frustrating when it rearranged your cautiously placed setup just because you grabbed the wrong thing by accident without being able to Ctrl-Z. Thanks a lot!

Right, did a flight with the Hornet already and it has the same sound. Well, they always had the exact same gun sound as the A-10, also regardless of rpm set which I always doubted to be realistic by any means. And I guess you're right with that -7° assumption. Didn't try that. That and simply hours not being recorded at all happened so often to me already that I actually stopped caring. Probably still in Early Access. An yes, my pilot is invincible. And I do have some backups that I could try to merge, but I simply have no idea how to do this. Those files don't look too well organized to me.

I'm sorry to say this, but I have to drop a very serious rant here: You shouldn't have taken an even smaller font than the default one. It's such a chore to read as for some strange reason it doesn't scale with the zoom setting (at least on my end though)... and yes, I actually stopped in the second paragraph because of that. While I'm at it, I might also want to greet and thank ED for their choice of board software again. And yeah, I know, it's still in Early Access. I just wished for this was legible. By the length of it and the images though, I can only imagine you did a fairly good job there. Thanks for that!

That new gun sound in the Viper though. Haven't tried the Hornet yet, guess it's there as well, Speaking of which, I do have a hard time understanding this:

Realistic would be the ADV- line not showing at all if empty as per GB. But either ED refuses to change that or they simply have it so far down the prio list that it seems to take forever until it gets fixed, simply because literally everything else is more important.

With such an update, I can wait for another two weeks™ (I see what you did there!), no problem. But maybe you could lend that guy who fixed the sdefs to RAZBAM for a day or two to fix the Harrier being audible over literally everything even from like 20 miles regardless of its power setting...

The main page is so much better now, thanks!

Noticed the same with the Hornet and it's there in the Viper. Also was thinking it was me or my stick, but I checked the overlay and it clearly takes right roll input on both airframes (clean, fuels balanced) to do an Immelmann or Split S. Same for pulling up to ~60-70°, then turning around and pulling back down through -90° to revers the flight direction. Takes a considerable amount of right stick in both planes, especially at the lower speeds.

I love those strip gauges... And I've seen that sortie video already. That channel has lots of Jeff Guinn stuff. Worth watching every single minute of those.

Well, I'm still waiting for the corrected Belouga since the BK M-90 have been done correctly. Should work like in the video that's been linked here: https://forums.eagle.ru/forum/english/licensed-third-party-projects/razbam/m-2000/240606-operation-of-the-blg-66

I've never seen more than 2.15 on the gauge in the cockpit (neither on my rig nor in footage on the Tube), unless in a dive and that was just by a very small margin. But as you posted a TacView image, I never checked that TBH, but I've also heard you shouldn't take the perf data from TV too seriously more than just once. Either way, I guess I should see if it's just a speed gauge thing. Always tried on a clean airframe (tunnel racks removed) from a shallow <5° descent beginning at high speed reached on 42kish, checking especially around 35-38k.

Laughs in ALDI Equator They don't make such ads here though...

I do have Cockpit Global Illumination on and it never was a problem, but I'll try that out. Thanks, not a biggie that you did't react immediately.

Well given the fact the B tops out at M 2.15 in DCS and it's never been changed, can I expect to hit 2.34 with the A finally? The B has noticably more thrust without AB than the B, but the TF30 build up nice ram thrust with speed. I also remember seeing SFC numbers that suggested a much lower AB fuel usage than we do see in the B in DCS, so that must be attributed to the TF30s as well, so I kinda expect longer AB duration, at the expense of thrust which will be less. The B really is starving in no time, but so is the F-16 that also has the 110. And their AB FF is quite comparable in DCS. You don't since you're not even supposed to have tabs in the first place anymore. Well, I just did. Wrote the first quote post, Ctrl-A-Xed it out and pasted into N++, MiG28ed the page to even be able to select a second post for quoting, Ctrl-Ved the other back in and went on. Certainly was easier before, by just middle clicking the relevant Quote buttons while reading and then just pulling the things from the quote tabs together into one box and do the writing then. But well, they killed the middle click by making everything js. Must be like running the gauntlet for anyone who uses NoScript now...

I was wanting for this for a long time since the radar range settings appeared in the Jester menu as I controlled that like the LANTIRN myself before that... but yesterday I noticed there's the GS mode added, I think it's the lower left thing in the BVR menu. But no option to recenter it. BTW: What I'd really consider necessary to be done by HB is when Jester switches to GS, he should up the range one notch if it's not already maxed out, so the radius of the GS mode will be the same as the range was before in AC stab. Same he should crank it one down when going back to the normal radar mode.