Biggus

Also doesn't fit the elevators.

I don't even bother looking for the slats, I look for the slime lights for an S. Took a bit of time for the early S birds to receive their slats, but every S will have formation lights as part of the rebuild. You won't see them on Js. The S birds that hadn't yet received the slats were referred to as J/S and aren't to be confused with the Super J, which was an update to around 28 Js where they received the AWG-10A and a few other goodies in 1975. These ones are harder to differentiate. The giveaway is that the port side ECS scoop has a splitter. And before these birds, you have the Js that received the DECM gear between 1972 and around 1975. I don't recall the name of this mod though! Hope this helps.

It's interesting. You see 200 in the server list. You join and in the lobby you are still on 200. The moment you select a slot, it's 400.

I'm hoping this is fixed soon.

Apologies, I misunderstood that you were talking about devices and not inputs.

Plug device in, go to options and start binding your controls. There's columns for each device. If I want to assign a function to my button box, I find that function with the search element of the category drop-down menu and enter the function name. Then when I've found it, I double click in the box that is at the intersection of the functions row and devices column and a new menu will pop up. I then press the button on my device that I want to use. So long as I don't exit the settings menu by hitting 'cancel', it will bind the button on my chosen controller to the function I selected.

I can see this adding enormously to the flavour of dynamic campaigns. Kudos, guys.

I believe the limit is 128 digital inputs and eight analog inputs per device for DCS.

They've also said that they want a short pre-order period. I'm hopeful that it'll be before xmas.

I'll be honest and at my first read-through of OP's post, this was exactly my reaction, for exactly the same reason. But then I actually went looking at the price of button boxes and noticed that the stuff that is aimed at racing sim guys (and if you're just googling generic button boxes, that's what most of it is marketed for) and was somewhat staggered. I'm seeing button boxes with maybe ten buttons or switches, a potentiometer or two and four rotary encoders selling for $300AUD before postage on Aliexpress. We're talking nearly the kind of money that you can buy a Winwing Orion throttle with. For vastly fewer inputs and lower build quality. We're not discussing bespoke cockpit panels here. We're talking about glorified gamepads that happen to be in mountable box enclosures. That part of the market (which is where most button box consumers look first) is full of profiteers and I think that's where OP's frustrations lie.

Regarding the 900ft frame drop: It varies by module. The Warthog, Hornet, Viper and Tomcat do not suffer this phenomenon for me. The Strike Eagle, Mirage F1, Mirage 2000C and Harrier all suffer from the 900ft frame drop. Here's how it looks in the Strike Eagle. Even if Youtube compresses it so that the numbers are unreadable, you can see the change in the graph and can see that it is repeatable as I travel through 900ft. In the modules where this frame drop happens, it does not seem to matter where on the map I am. Out at sea, close to cities, out over the wilderness, it's the same drop. Hope this helps a bit, @Raz_Specter! Edit: After @Mr_sukebe's post, I went back and retested and unfortunately my results are not repeated at the second attempt. The Viper seemed to suffer the problem this time, and the modules that suffered yesterday were smooth today. I can say that I don't ever remember not getting very low frames with the F1EE take off mission in the instant action section. It's now around 20-30fps (and once I'm over 900ft, I'm seeing around 60-70 depending on where I look). This is quite large progress over a few months ago, so we're moving in the right direction.

I've had my Orion since April 2021. Never had an issue. Use it a minimum of two hours a day, five days a week.

It depends on what you're wanting to do. If you're doing productivity stuff and simming isn't your main focus of your build, yes, a 7950X3D is probably the better choice. But if you're building for flight sims, no, the 7800X3D is the better choice. The higher clocks don't necessarily mean better performance.

I posted a day or two ago about my perception of spotting at 3440x1440, and I've spent some time experimenting with my G2 today. The dots in the G2 are far too large from 3nm out, and the LOD change at 3nm is far too dramatic. At 3.1nm, it's a great big blob. At 2.9, it's a speck that you probably can't see even when you know where you need to be looking. The original spotting fix mod seemed a good bit 'gentler' (for lack of a better word) at the point where the LOD changed. I'm still pretty impressed at the devs for a first pass at this. Options.lua

Yes, this is a real problem for me in VR still. I hope the tool is updated for MT soon.

I agree, I've seen some horrendously priced boxes with a very small number of inputs lately, and the fact that they're often sold out is somewhat mindblowing to me. I think a modest button box is really the realm of the DIY-inclined. It's a really difficult niche when it comes to pricing. I have my own 1000x1000mm CNC and I make my own panels and things as a hobby. If I were to factor in my panel design time, my toolpath design time, my PCB design time, my fixturing and machining time, my tool costs, my raw material costs, my programming time costs, etc, I'd end up at a prohibitively large number that I cannot ever let my wife know about. I look at some cockpit panel producers and cannot see how they could possibly be making a profit at the price they are selling them. Then I look at the price of racing sim oriented button boxes and what must be their 100-to-200% profit margin and I scratch my head. Market size is a hell of a thing, I guess.

Because that's not what everybody sees. It varies with software settings, hardware and resolution. ED's task is to now find a way to provide spotting parity across all of those variables.

The improvements are noticeable for me. I still get some exceedingly large frame rate drops near Ushuaia (much of the map for me is over 100fps and I'm seeing under 35 on a low pass over the town), but I can see some nice changes. Well done!

As a very enthusiastic adopter of the dot fix mod when it passed IC, I've got to say this is a large step in the right direction. 3440x1440, I am able to visually pick up a Fencer at just under 20nm if I know where to look. This is probably a bit too far away to be seen, IMO and I don't think the original dot mod would have rendered an aircraft at that distance. At ranges under 8nm, the scaling seems pretty reasonable. I still have a hard time spotting aircraft, but when I'm able to visually track one, I feel like I haven't had any of those moments where a LOD change renders them invisible. I also have a G2 but I haven't yet tested that properly. I'll report back when I get a chance to do so. Good job so far, ED. Options.lua

I'd go with whoever was offering me the longest chipset longevity and hope that they actually followed through with it.

Fooling around with the cinematic camera.

I wonder if this is related to the ping doubling when we slot in. Weapons view has the same issue.

I'm seeing that too. Seeing quite a bit of jitter when I use F2 on other players and F6 on my bombs.

I suspect this is because of the configuration of the 7900X3D and 7950X3D. They are dual CCD, with the stacked cache only on one of the CCDs. The 7800X3D is a single CCD. For DCS, the 7800X3D should be the pick of the bunch because of this.