Eldur

Spudknocker did a video on that topic a while ago... And it's not just a DCS thing apparently

Sadly, I can't help, but that instantly reminded me of hitting "choose slot" when I actually wanted to either see the briefing to check frequencies or check/adjust some control mappings, and I've had that happen often enough already. Once you hit it, you're out. Sucks big time, and there are no other appropriate civil words. Those are the things that I'd really like to be fixed somehow. Asking "are you sure?" or having an option to get back and stay in the thing would be rather simple to implement I guess...

Well, flying a 117 is a bit like playing Thief: The Dark Project instead of Skyrim. Well, most players want to have at least 3 dragon boss fights on their way out of a dungeon while being encumbered 150% buffed up with magic potions carrying a truckload of loot while even one of those tries to attack your Quest NPCs. I hate that (and the fact the game doesn't have a questlog and you literally have to play it with Quest-GPS on) and want to have room for thinking, plan my ingress and egress and do my job effectively and thoughtfully. I don't need a bomb truck to brute force myself though anything that they might throw at me if I can hit the most vital assets right within a heavily defended danger zone. You have to get in unseen, get your job done and get out unseen, that's the thrill. Of course this doesn't appeal to the ordinary MP airquaker. But I'd guess it would be a very welcome addition to SP pilots who just want to do something else you probably just could do otherwise with the Fat Amy or a Raptor, but then again I guess that ones have a slightly bigger RCS nevertheless. As for the modeling of the RCS: Another well known survey sim over 2 decades ago (so not the most realistic out there) already had RCS varying dependant on roll and pitch angles as well as gear, airbrakes and bomb bay state. You could either be almost completely invisible and <5nm or easily be locked up and getting shot at at 30+nm depending on all that. Back in 1996. I'd be surprised if ED wouldn't have at least that somehow modeled in their sim. The single values from a lua file are probably just constants to make the planes differ from each other. Magnitude 3 entered the chat. Oh, yeah. I've seen that movie. To be fair... Nobody: Absolutely nobody: Not a single soul: https://forums.eagle.ru/forum/news/o...80#post6027280 Because the forum software sucks though, it won't take you to the actual post since it will load up a plethora of images for 'bout haaf an owa. Let me tell you it's the post made on "02-07-2020, 05:37 AM" about the 2020 And Beyond Trailer. There'd be a very easy long term solution actually. It's just that the input manufacturers finally would need to get their ship together and begin building actual input devices that come with FFB (which in itself also needs a massive overhaul since it's technically limited to X and Y axes). If every device had that, it would be piece of cake to transfer the device positions over to each other. The tech has been there for over two decades, but TM, VKB, Virpil and co. simply couldn't care less, which is a bloody shame. I just wonder if I will live to see that happen some time...

Wasn't even aware of this being an actual issue with the FM. I just push the nose down like 2.5-5° when trying to get through transsonic which anyway is a good idea to pass that extra drag quickly. Then at 1.2, just pull up as desired. I'll be that guy now: You must be new here

You clearly left your gun rate at low, that botches up everything. As for the FF, I'm confident this is OK. The A also needs less to taxi (somewhere around 1.4 instead of 2.8 in the B) and it stays at higher speeds down low if you set it at, let's say 3.2sih. With increasing altitude, that advantage diminishes however and I'd attest that to the low alt optimized TF-30 - remember those come from the F-111 that's literally made for flying low and possibly fast. As soon as you need more thrust though, the F110s of the B will be more effective. So basically at FF rates like 3-5 on the gauge you're better of in the A, but at higher rates like 7+ you clearly see the advantage of the B as you get more bang for the buck there.

I think 17GB isn't too bad when you have 32GB installed. As long as DCS doesn't crash from that I'd say it does what it should - make use of our hardware. The real thing is that it should communicate with Windows so it won't get crashed due to running OOM. But I don't want to have 32GB installed and only like 5-8GB being used with the thing constantly loading up content producing stutters. BTW totally didn't expect the update at all, even yesterday the Patch thread was saying TBA before it dropped, which I only saw now for the first time.

You can simply copy your current install over to the new drive, no need to do a reinstall unless you want to do it for cleaning it up. DCS will work from any directory path, you just have to adjust your links on the desktop and within the start menu (if you do use those at all). If you plan on running the OB next to another Stable install, go check this out: https://forums.eagle.ru/forum/english/dcs-world-topics/mods-and-apps/dcs-mods/159902-the-dcs-updater-gui-utility?t=160053 You can use that tool to switch from Stable to OB and back comfortably, saving you lots of disk space.

Finally! I've been eagerly awaiting this module. Now that it is only half a year to EA release (I know EISTC), you get me really excited. Cold war 80s stuff, steam gauges and iron switches, Mach 2.5 and a good looking Dassault Design... So it is the Hairdryer of Doom confirmed

Now if only we had actual Zeroes...

After the Hornet Roadmap and RAZBAM's waterglass, we're ready for everything. That would be very minor however. And while we're at it, I'd rather (what a language which lets you have a full sentence without an actual verb) the Tornado than all those wishlist items.

That (BTW 500ft/min for jets) and maximum continuous power. So it's highly unlikely that this includes the usage of afterburners which isn't exactly continuous given the fact it runs you dry in like 5-10 minutes unless you're very high (50k+). I've seen numbers as low as just 45k for the Tomcat which is where I got the B to - barely. You can trick out more of the thing by manually bringing the wings back forward though. Or by going supersonic so you don't end up at like 200 canots indicated with the wings swept back (much less dense air should allow for that unless you go supersonic where the shock waves probably won't be too great for your wings, the CADC isn't programmed for that however). I mean, just try flying with that geometry down low. It's literally a drag fest. Well, it's a general DCS issue. I mean, just ask the other Eagle driver who went up through 100k in some occasions in DCS... and yes, the pressurization works only so far, the pressure altitude should raise as you climb beginning at some point and when it reaches a level that you'd get hypoxia at without, it should give you that up there as well.

Eeyup. And it's always been like that. Fly the thing at 500m, Pitch down, when it does and as you close in on the RWY, you're always slightly coming in from the right, crossing the "extended runway" where you'll have to turn into it while staying on the glideslope.

Just heard him call out Bingo in the B. Never got anything in the A though. I do suspect something now. I was conducting some speed tests and set the thing to 10% fuel and unlimited on because I just wanted to see the limits. Had a runway take off set up so I can get right into it and Jester called out Bingo there. But that didn't work in the A though. Now comes the thing. On my training map everything is at 20% fuel initially, which still is less than 4000 in the Tomcat. On a cold and dark, the callout might be triggered by that already, but he won't say anything and might not say anything later on. Just a thought.

Just checked what could cause this. In DCS World OpenBeta\Config\Input\UiLayer there's a folder mouse with a default.lua in it, which, basically, is empty: return { keyCommands = { }, axisCommands = { }, } Checked backups of older versions (one from April and one from December) and the whole mouse folder simply didn't exist there, the file is dated September in my current build. Suggestion so you have it fixed on your end while waiting for ED: Either remove that mouse folder or copy the default.lua from keyboard over to mouse, which makes it possible to map the same things that you can map on keyboard. Each update will revert this though, so you could make this a JSMGE/OvGME mod. To make it with removing the file in JSGME, just create a mod that has the folder structure Config\Input\UiLayer\mouse, add an empty text file in there and rename it to default.lua-remove. Alternatively, copy the file from the keyboard folder in there. Dunno how that works for OvGME though, but probably it's the same, except for maybe rhe removal of files.

Mom, can we have Hornet? But we do have Hornet at home! Hornet at home: Awesome!

I mean, JOKER and BINGO, as mentioned on the patch notes. I don't get them, et al. I've just heard one on one video so far, but it's impossible for me to reproduce. What gives? Cold and dark only here. And I've been setting non-default values to the gauge.

Actually I've been wondering if I somehow forgot to turn it on...

The throttles in the whole module have been asymmetric (Left more than right) ever since, which can be seen clearly by the FF and other gauges. It's about time to be fixed finally! As a side note, I also see this in the Hornet, but not by as far as much.

You must have missed ED's understanding of "backup ADI"s in most of their modules, particularly the Ka-50 and A-10. Those are useless after just like 3 minutes in. The Tomcat HUD is a wealth of information compared to that even after the IMU getting slightly cracked. As for the video, I'm just wondering what "devices" are. Heard phrased like "devices are in" several times and have no clue what they're referring to. Could those be the spoilers? I mean, they could just have called them "things" right away...

I was just thinking of hacking the stores drag to massive negative values just to see if it comes off at M3+. If it does, I wouldn't be too satisfied with the duct tape being undermodelled however...

And then just a patch of duct tape on top of that, et voila!

I bet the discussions will stop immediately once they'd be added as an option in the ME... Probably the only thing that's being asked for more often on these forums is VR performance. Compared to getting that it would probably be piece of cake to do And as far as I can remember, someone from HB, probably was Cobra, said they could actually consider modeling them at least visually. Changing the FM accordingly would probably involve more work that it's worth it, but actually I can't tell. Adding it visually only should be rather easy though. And as long as we have other airplanes from the main devs whose FMs don't care if I take the racks off or not, this probably would be good enough™. Maybe not for the high standard setting Heatblur though

Heard it in a video now... but there might be an issue with the thing. I turned the bingo down to 2400. Maybe changing the value kills the callout.

IKR? I always do expect things to be worse when it says that - just to be positively surprised when it's gotten better and not to be disappointed when things get worse. At least our SME does have an idea already and it's probably going to be addressed soon™.

I wish it would be affected by gravity. Shouldn't point up straight to the canopy when the whole thing stands still on the ground with no wind. Also, wind should be able to blow it into any direction (like wind coming from the back making it point to the nose), but I haven't checked that yet. Apart from that, it's a great little addition that probably is lots for some people, especially those who fly gliders IRL.