backspace340

There isn't an update due this week (other than Stable being updated to the same level as the Open Beta patch we got last week) - the next new Open Beta patch is due on the 24th. You can expect to see a video from Wags showing us how to use the JHMCS and Mavericks before we get them.

I assume they're going to remove the new profiles they added (and which we've all deleted). If they didn't remove them, then the next patch would just add them back in for all of us that deleted them.

The servers aren't run by ED and the server owners choose to run the best MP experience - often that's the Beta because it has the newest module releases in it and gets bug fixes first. When the F14 releases, do you think people will be happy to wait a month before playing it in multiplayer?

That would be great logic, except Mavericks weren't even in the poll. Anyway, my point is that the only thing stopping them putting GBUs on is implementing some way to change the laser code, but with laser Mavs they have to do that AND make a whole other DDI page. It's not that it's little effort, it's that it's the *same* effort. Anyway I'm sure there's some other reason it's complicated or maybe they'll just surprise us with them at the same time - it was just a throwaway comment.

Yep but for the Mavs you need at least two whole new DDI screens (one for the laser seeker, one for the IR seeker) - and you still need a way to change the laser code like you would on GBUs. Obviously I've got no idea on exactly what's involved but just seems like Mavs would be a much more complex job and we've had GBUs mentioned as on the way for 3 months or so now. Just a bit puzzling.

You need to install SteamVR *and* the Windows Mixed Reality for SteamVR for the Odyssey to work correctly with DCS. You can still use a standalone install, but you need those two things installed.

GBUs don't need a dedicated TGP - you can drop them from the Mirage or F-5 for example and neither of those have one. It just uses a buddy lase. You don't even need a LST - just aim at the coordinates and drop and the bomb tracks the laser.

Yep should be able to carry as many GBUs as the dumb bombs (so 5 big ones or 10 medium ones) but only four Mavericks. There was a bit of back and forth in an old armament thread over whether the GBUs (laser versions) could be double racked and they seem to have settled on yes - but JDAMs will definitely only be single racked (so five total assuming the centre station can be used).

I am a bit confused how we're getting Mavs before GBUs (especially given one is a laser Mav) - you'dve thought it'd be easier to put GBUs on, especially if you've already sorted out a way to change the laser code.

The Es are laser guided (as on the Harrier) - so a buddy lase from a JTAC (or A10/Harrier) will work for that. For the Fs yeah I guess we'll either use the seeker displayed on a DDI or perhaps the HUD/JHMCS to target them.

It's not true - you can hit the stated max ranges in the right parameters. For example, you can hit the stated max ranges from Wikipedia on the AIM-7M (longest I've hit with is 50nm) and R-27R (I've hit from the max range of 80km in-game). They haven't been artificially reduced - it's just those ranges are in perfect conditions (going Mach 2+, at 40kft+, at a closing target) and people don't understand why their '50nm range' missiles only go 10-15nm when fired at sea level at Mach 0.4.

I think the closest I've seen so far is in the product description here (and I guess the same on HB's site): https://www.digitalcombatsimulator.com/en/shop/modules/tomcat/ This bit lists most of the sensors and weapons: The only thing we're missing I guess is a break-out of specifically which variants of the AA missiles, bombs, rockets and extras (like the TALD) we can expect.

I'm by no means the expert but it seems like what they've tried to do conflicts with any previous configs in saved games, which is why some of the controls can't be bound at all. The solution ED recommended is to delete the configs from Saved Games, and then the next time you start the game you'll be able to edit your controls. So you can rebind, but first you have to delete your old bindings (or you can delete their new bindings, but that might not work forever). They might not have done one for the F-5 - I went through deleting fairly quickly so might've missed that, but it did seem to be most ED/Belsimtek modules - there weren't any profiles added for the Viggen/Harrier/Mirage for example.

In the latest Open Beta, ED added new default configs for the most common controllers for ED/Belsimtek's modules - these are incompatible with custom bindings anyone's previously made for those controllers. In order to resolve the conflict, users will need to delete their custom bindings and re-bind ED/Belsimtek's modules back to their liking (or use the new defaults). For me that's 11 modules that I regularly fly that'll need completely re-doing (Hornet, A-10C, Huey, Mi-8, Ka-50, Su-25T, F-15C, Su-27, Su-33, J-11, Mig-29). They were looking into making it easier/avoiding the pain for users, but it seems like they're not going to do anything now judging by NineLine's comments - so it's likely this change will go to Stable next week. Right now there's a workaround by deleting these new default configs that have been added - which leaves everything as it was last patch. But that will need doing every time the game is updated and who knows how long it'll last.

Sorry my mistake - his results don't make sense to be honest with that last run - compared to the earlier run with the Rift (with a different mobo & CPU), the 1080ti got more frames and the 2080ti got significantly less. You'd expect a shift in one direction not opposite directions.

Non-VR players have a much more powerful zoom.

So this change is going to stable next week, with just an explanation to re-do all your bindings? Surely the devs can just write a migration to handle this neatly? I can't believe the only solution to this is for every single one of your customers using any of the most popular joysticks/throttles to spend hours rebinding.

Those numbers advertised aren't real range, they're advertising numbers - the missile will never fly 100nm in reality. What it means is that if you're at, for example, 60,000ft and travelling Mach 2.5 and you fire a missile at someone travelling straight at you at 60,000ft and travelling Mach 2.5, then at the point you fire your range to them will be 100nm (for example - the range of the 120 we've got seems closer to the 55nm). You can see it fairly easily in game - put a Hornet at 60kft and 800kts ingame, clean except for two 120s in the fuselage stations with an enemy going the same speed at the same altitude 80nm away from you. You'll get a shoot cue at around 50-60nm probably. On the deck, the same missile will probably only show you 15-20nm.

All of my bindings are just changed by editing whatever the default was for all the modules (i.e. just editing them via the ingame GUI). If there's another way of doing it which is the 'correct' way then it's not clearly explained by the game at all - I'd imagine most of your users edit their bindings the same way I did, judging by the howls of pain on MP servers all day since the OB patch this week.

Those are non-VR benchmarks - the VR benchmarks are here: Rift = 48.7% increase: https://forums.eagle.ru/showpost.php?p=3643539&postcount=36 Vive Pro = 53.7% increase: https://forums.eagle.ru/showpost.php?p=3644614&postcount=61

Fairly sure this has been partly moved in error - the air spike *is* specific to the Hornet, but the mud spike isn't. I'll see if I can knock up a track next time I'm on showing other modules not getting an air spike in the same situation the Hornet will.

It's not 34% in VR though - you're getting 50% better frames?

This is the best bang for your buck, solid controller for a great price: https://www.amazon.com/Thrustmaster-T-16000M-HOTAS-Controller-2960778/dp/B01KCHPRXA/

It affects anyone using the equipment they made default profiles for - e.g. TM Warthog, Hotas X, 16000 among others.

They're looking into fixing it in some form or fashion (I'm assuming as a hotfix): https://forums.eagle.ru/showpost.php?p=3652107&postcount=51