Tippis

It's not really a question — what would happen is well-established and known. And no. That would contravene the entire purpose of having 3D models to begin with, much less having different levels of detail on them. The reason you don't remember this is because what you're describing never happened. That would be a pointless, backwards, and pretty darn stupid solution since — aside from being dots — the two are nothing alike and it would in fact make every problem you're complaining about even worse. Not only would you be able to see them at much longer ranges, the visibility would be entirely a matter of resolution where higher resolutions make them more difficult to spot, they'd be trivially easy to manipulate to give yourself even more unfair advantages, and on top of that there's the fact that one is a UI element rendered on top of the world, whereas the other is a world object and part of the simulation. Every bad thing imaginable at once. If you believe dot labels are a better solution, just turn them on. Problem solved. Or, well… problem caused, really since the outcome is the exact opposite of what you want (assuming you do not dearly desire having an unfair and unrealistic advantage).

And that's the whole issue: it does. And the distances are too long. And it creates P2W. It sounds like they're trying to improve how the system works in VR.

What's wrong is the assumption that they'd vanish from view “like they should”.

Our current one. I have only shown it about a bajillion times, but fine, I'll demonstrate it again. If I zoom in to a 20° FoV, the frustrum covers 349.1 mils. On my display, that angle is rendered using 3440 pixels. Each pixel thus covers 0.1 mils. For the wingspan of an F-16 (just under 10m) to be less than 0.1 mils and therefore only cover one pixel, that plane would have to be 100km (54nm) out. That is quite a lot more than “a few miles” and an order of magnitude beyond what most semi-qualified guesstimates suggest should be reasonable. It's even more than what the old spotting dot system allowed for, and that was already ridiculous. And that's on my modest hardware. For others, it could be even farther. Or much much shorter. All three cases are bad because none of them are the same. Even if by pure accident, someone gets a proper and sane spotting distance limit on their system, that limit only applies to them and their accidental realism puts them at a severe disadvantage and others throwing money at the problem would be at a severe advantage. No. Unified spotting dots show up for less than half of that. If dot labels bother you, redefine them or turn them off. The spotting dots also need to be dialled back — I have never stated otherwise — but they are massively better than relying on the unlimited range that pure trigonometry and the 3D model would inherently provide. We can also discuss what the proper size for the dot should be, but then we immediately have to figure out what should be the benchmark — the lowest common denominator — that can be reliably and equitably the target for all displays irrespective of their resolutions. It is quite obvious that the VR one is bonkers, but that doesn't really help us answer the question of which one isn't? Which one should be picked as the standard? If you want to argue that we should do away with zoom, then I wish you the best of luck on that debate. If you want to argue that I can't see that single pixel anyway on my display then, sure. With my current setup you're actually correct. There's just one problem: I can move the display closer, or just lean in, and the problem immediately comes back. And if you want to argue that, screw all that trigonometry noise — just put a rendering cap in, then fine. That would indeed work for limiting how far out you can see other planes. But realise that this means they will pop in at, oh, let's say 5nm and be about 1 mil, or in my case 10 pixels wide. It won't exactly be subtle. I'm talking about what would happen if we didn't use a dot system to put a hard cap on how far out a contact would be rendered on modern hardware. You've never seen it because it's not done that way, and for very good reasons. You didn't have to worry about it in the olden days because the hardware couldn't display it anyway, and in many cases there was a hard cap on rendering contacts, and the same hardware limitations made sure you couldn't see the pop-in. Much. Would you prefer it were three times that number? Because if we remove the cap and the dot, and only rely on the model, that's what you'll get. Well, not in VR, obviously, but that is sort of the problem. You wouldn't get it but others would. You would have to rely on radar, AWACS and RWR, but others wouldn't.

That's because the current spotting system ensures that it doesn't happen. If you just let the 3D model do its thing, like you suggest, there would be no limit to how far out aircraft could or would be rendered, so the range at which you'd be able to spot those planes would be completely disconnected from any sense or semblance of realism. Iwould only be your graphics setup rather than any part of the simulation that said that, actually, planes can be seen just fine from across the entire map. Or worse, you wouldn't be able to spot them at those ranges, but they will be able to spot you just fine. Essentially the problem we had with the old system, except your suggestion just changes the unequal dot for an unequal 3D model. The end result is the same, and we'd be right back where we started where the spotting system has to be revamped. This is a VR discussion, yes, but what is rendered in VR relates to and has to consider what is shown on monitors, or VR will end up with some serious disadvantages (or advantages, which is just as bad). And without dots, there is no way to control that point, equalise it across hardware, and make that single dot of an equitable visibility. We are already at the point where our displays can (and will) render details that the pilot should not be able to see. That needs to go. In addition, this ability differs with settings and hardware. That also needs to go. If realism is a core goal, what the hardware is able to generate is no longer a viable limit. We must introduce and enforce artificial ones. If equitability is a core goal, we must not let higher-resolution displays show targets before they can show up on lower-resolution ones. We must introduce and enforce artificial sizes. In both cases, we end up having to make sure a single dot is rendered at some given distance, in many cases long before it is actually 1px large on the screen, and we have to make sure that single dot fades into the background in a controllable way. What better way is there to display a single dot with its size and colour tied to strict in-game parameters, than to have a dot-based system that use in-game parameters to dictate its colour and size rather than some arbitrary out-of-game factors? Are you serious with this question?!

Which is why you need to put something in its place and why cannot allow the LoD to run free. If you do, you get the situation we had before where you saw aircraft at potentially infinite range, because that's what the rendering will do if you don't tell it otherwise. So. Back to the same question: if we don't use dots to hide the transition from a hard cap on rendering distance to where the 3D model can start to be rendered at what is an appropriate size for the distance, what else should we use? Should the 3D model just pop in? Should we add klaxons to try to divert the player's attention from the obvious jarring effect that appears on the screen?

Good thing that they're not doing that, then. In fact, the system you were so much in favour of was doing exactly that, and now you are upset that it's gone. But more to the point, the game should also not favour high-spec hardware. If you want P2W, go play Warthunder.

Have you tried reading the meany reasons given and responding to them? How do you make sure the 3D model is only visible at realistic ranges? How do you avoid pop-in? How do you make sure it is shown equitably across different display types? This is exactly the problem relying on the 3D model alone causes and that the dots solve.

They're also completely separate and largely irrelevant to the thing that dots are meant to represent in simulation. If you want to get rid of the dot system, you first need to come up with a better idea for how to represent what they're meant to show. Getting rid of dots without any replacement would have the exact opposite effect to what you're asking for. If you want the level of unrealism a dotless spotting system would create, go play Afterburner Climax.

That should worry you. The rest are talking about it — they just don't want to acknowledge the consequence of what they're asking for. Yup. Only way to equitable compensate for different resolutions. And it works. Success, until someone can figure out something better. Do you have any suggestions?

Good to hear. Yay for Bohr bugs.

That's not the point of confusion, really. The fact that it works like this is pretty much well understood and at the heart of the discussion of how to make the dots VR-adapted, most likely by realising that the game is being played in VR and using a different resolution scaling factor than you'd get in pancake. It's not necessarily the dot that is 10x larger — you get multi-pixel dots in 2D as well — it's the visual size of the pixels is that much larger so the dot itself should be smaller to compensate. After all, this kind of compensation between higher and lower resolutions is part of what the dot is supposed to solve. Adding a similar compensation for larger or smaller visual size of pixels should be pretty obvious. No, the “confusion” is rather between the two positions of “we should fix the dots so they take the display system into account” and “we should remove dots so that planes are rendered at infinite range if you pay enough cash for it”. A bit unfair a characterisation, perhaps, but ultimately, that is what the latter side is effectively campaigning for.

So, provide a solution. Don't just whinge and dig your heels in and demand the return of an infinitely worse solution. Provide the data and feedback needed to make the problem go away. They won't be. In fact, it shouldn't even be a choice. It should just be equal, to everyone. Again, this was the problem with the old system, where you could choose to have an advantage. Worse still, you could pay to have an advantage. It was truly an abomination, and the new systems, for all the work that still needs to go into it, has rightfully gotten rid of it. Maybe …to you. On your setup. That is not as good of an argument as you wish it to be. In fact, it harkens back to exactly why we had to get rid of the old system — it was also fine on your system, and you demonstrated this by seeing how easy targets were to see. Unfortunately, you did this at ranges where they should have been impossible to see so you only defeated your own argument. But more to the point, at that range the issue to solve isn't one of seeing the aircraft, but of aspect identification. That is exactly what scaling is intended to solve. You are confusing the issue with something wholly unrelated, and are essentially demanding that a workable, realistic, and equitable solution should not be put into place because “it's fine for you”. But you and your system are both irrelevant, and your one argument against this solution that you have explicitly admitted you don't understand, to a problem you have admitted you don't know anything about, is just unfounded guesswork because you have also admitted you have never seen it in action. It's pure argument from incredulity: because you believe it can't possibly be good — having no actual experience with it — it therefore must actually be bad, and must therefore not be used to solve the one problem it is exceedingly good at solving. Not at the sizes we're talking about here. So you got that one backwards. The model isn't needed here and is indeed a huge waste of rendering time to use just to create a single speck, especially when the dot that needs to be there can do it instead. Additionally, funnily enough, if you want it to be the model that reports all that, then we're in a range band where we should be using scaling to correctly convey those cues. So now you're in favour of that in spite of your protestations. Oops. Oh, and since you don't even play in VR, your wish for a system where out-of-game factors are the only thing that determine spotting distances and in-close aspect and target recognition isn't even relevant to the discussion at hand.

Not in any sense of the word, nor in any of the functionality, no.

Can you offer a good idea for how to replicate the (very necessary) functionality and not make it inherently exploitable?

Darn. Next guess would be that it's basically the opposite: that something else is trying to steal focus for whatever reason, and DCS is flighting back since you've set it up that way. Are you running any external tools or mods that might react to what you do in-game, or which have their own overlays that might be of the mistaken impression that they're being called for? I know it's a bit of a shot in the dark, but I hade a very similar problem once and I tracked it down to — of all things — the fan controller software trying to tell me that, onoz, demand for cooling just rose and would I like to adjust my profile to something more aggressive? So it might not even be DCS that's annoying here.

Absolutely agreed. Well, maybe apart from the WT bit, since I think the aim has always been one of realism more than anything, but they haven't got it (even nearly) dialled in yet. Hence why I think what is needed most of all is data — how it appears compared to how it should appear — with a whole bunch parameters taken into account.

…aside from the whole “crazy and obtuse” and now “arrogant” bit. Good news: no such presumption is made. I am simply explaining how your sense of immersiveness relates to the notion of having a “false dot system”, namely that the one you prefer is just as — and actually in many ways more — “false” than the one you feel is less immersive. I'm not saying that you're not finding it immersive. I'm saying that whether you do or not is not a factor as far as determining which is better from a realism and simulation standpoint. It may very well be that you feel a bad solution is more immersive than a good one, and that's fine, I suppose. But you need to realise that the end goal is probably more skewed towards a good and more realistic solution than one that satisfies your sense of immersion. Your preferences are not universal, nor are they by necessity the guiding factor in determining what the spotting dot solution should generate. If you want to offer an argument why we should have a system that shows contacts at highly unrealistic (and arbitrary) ranges, then do so. If you want to offer an argument why we should have a system that is inherently unbalanced, then do so. If you want to offer an argument why we should have a system that lets out-of-game factors rather than in-game simulation determine performance, then do so. Just don't expect “my immersion” to be a particularly convincing one. Alternatively, offer an argument for a solution: at what ranges should what targets be what size and/or faded into the background to what degree. Discuss solutions for how to achieve that across a multitude of displays and settings so we don't have the current problem of VR being burdened with inappropriate 2D rendering calculations. Then your immersion may end up being served without reverting back to an old and demonstrably bad solution.

That sounds an awful lot like it's trying to change focus and show the desktop because you have clicked something else. Are you running true fullscreen or borderless? Do you have the “confine mouse to game window” option checked?

You're not offering much in the way of argumentation, just abuse. So no, I don't suppose I must do anything of the kind. The probably do. That's why the old system had to go, with how exploitable and hackable it was, and with how it made it see all other aircraft at absurd ranges, regardless of whether it's realistic or not. That's also probably why they're not bowing to the pressure of gamers who want their old exploits and imbalances back.

I do. I just look at the problem differently. …and this is the actual problem. The one that the new dots are set up to solve. You have now chosen the old issue of targets appearing at utterly ridiculous levels, but only unreliably, and if you use specific settings. This is far more exploitable — deliberately or accidentally — than what we currently have. It is also much less realistic than what we have now. With your choice, are still getting a “false dot option”, just one that is much worse from a simulation perspective. And from a balance perspective. And from a situational awareness perspective (and I don't mean in the sense of “I can see them” but rather, “I have no idea whether they can see me or not because we're not seeing the same thing even though we should”). What you assume is more immersive is actually a fare falser dot solution, in just about every way, than the new one. You're just used to it and more comfortable with it, that's all. Yes there is. It is more realistic. You may not like how and why it is more realistic, but it is. Unquestionably. Because it much more closely simulates the limitations of the human eye. Not all the way, granted. Hell, maybe not even close to all the way. But still much more closely than what we had before. The old dots were ridiculously false in how far out they would let you spot a target. It is more equitable. This may not seem important if you only play in SP, but it is. Because it means we are actually simulating a critical component in the whole flying thing: the pilot. Previously, we didn't. We just let people choose their setting how, through that, how superhumanly good their pilot's eyesight was. And it was always superhuman. The old dots were ridiculously false in how differently they portrayed the pilot. It is more tweakable. This may not seem like it matters, but it does. Because now ED can control, pretty much universally, what players see at specified ranges, whereas previously they had no control. This means it can be further developed and enhanced into an actual spotting system that the game has been lacking for… oh, roughly… ever. The old dots were ridiculously false in how it was a one-size-fits-all solution that actually didn't fit anything. The only non-bright side is that development seems to be slow and that we're currently stuck with a naive solution that doesn't take into account what kind of display the player is using when figuring out how large the dot should be. I suppose you might want to add the visibility ranges as well, but since those can be tweaked more easily, it's actually a bright side even if the fact that you can't see as far as you could before didn't already make it so. I and DCS have a mutual understanding of what the ‘S’ stands for. It is crucial in understanding why the pilot's limitations can't be left to the player to arbitrarily choose, or their hardware to arbitrarily dictate. It should be a part of the core simulation. Now it is. This can only ever be a good thing. Do you understand how problematic and frustrating the old spotting dot solution was in MP, where some people could see targets at well beyond even BVR missile engagement ranges, whereas others couldn't could barely see targets in WVR ranges? And that some people lost their targets when they entered realistic visible ranges, whereas others would suddenly see them clear as day at that range, but not before? And that the old system was wholly decided by hardware and settings, rather than anything that was actually part of the world simulation? Because that was the reality with the old dots. They were horrid, especially in MP. Especially in a competitive setting. An apparent reason why ED seems to be slow to rectify any problems with the new dots is that there is so much effort being sent on saying “no, give us the old crap one” as opposed to having a constructive discussion on how the new — vastly better — ones should be tweaked to provide sensible visibility across the entire range of devices and resolutions the players use. They can't really act on data that isn't made available to them.

Just in general, think how vibrant the game could be if all map assets were available as placeable static. There are so many bits and bobs floating around in the terrain packs and in the bazaar that could see use as decoration for other places than where they show up now, and the amount of work to make that happen should be pretty darn negligible on ED:s end.

Look at the bright side: at least you are under no illusion that you can't be seen just because you can't see them. If you stand out like a beacon then so do they, as opposed to the olden days, where you would stand out like a beacon but they didn't.

Why would anyone apologise for something that never happened?

It's not impossible. It's just very very hard, especially if you want to add in other parameters. But being very very hard isn't a good reason to just throw up your hands and do nothing. An attempt at an equitable solution is better than leaving it laughably exploitable. It's only self-limiting if your physical setup makes it so, and if you don't adjust your settings. But more to the point, it isn't self-limiting in the simulation unless you actively put that limit in. The hardware is now more than capable of exceeding those limits so you need to make sure to tell it not to. Of course not, but you have to adjust your simulation to match, so that it doesn't create an unrealistic result. That is the end goal here, after all: as accurate a simulation as possible. The development of new displays and graphics card and CPUs and storage solutions to feed more and more detail at long and longer distances means we now can't just rely on trigonometry to decide how small or large a target should appear. It means we must also start simulating the wetware sensor system that actually interprets all that trigonometry into something we can see. Just because your display system can accurately render a CE2 at 50nm doesn't mean it should. Because you can't see a CE2 at 50nm. Instead, that processing oomph should, or at least could, be spent on increasing the accuracy of that simulation — maybe adding in all that glare and contrast and all that fun stuff. Giving your pilot superhuman vision just because the hardware allows it completely removes any pretence of being a simulation. Imagine suddenly giving the F-5 an 250nm 360° AWACS radar and over-the-shoulder launched datalinked Phoenix missiles. You could — our hardware allows for it — but it would be wrong because that is not a capability the platform has. The virtual pilot is no different. It needs to be accurately simulated too.