sobek

Sounds perfectly reasonable. If you turn up the noise, more parts of the terrain will intersect with the filter "criterion" leading to more noise in the TGP image.

I agree, this is just a matter of the color gradient. If vehicles ever get a desert camo, this implementation is in for some serious trouble. But ED don't need us to tell them that.

Yes, the design is somewhat flawed to begin with. I'd say if something has changed when moving the filter from the old to the new engine which impedes it's function then that is indeed a bug and does not belong in a whishlist.

Please contact Sith or Wags, i'm no longer in the loop.

You have to understand how programmers think. If it works as intended by the programmer, then it is technically not bugged. In this case, for simplicity and probably implementation costs ED chose to implement FLIR as a color filter. That is (in simplified terms), the shade of green that most ground vehicles sport is mapped to white, everything that is not that shade of green is mapped to black (obviously with transition in between and the ability to switch polarity for BHOT). Everything that has the same color as most ground vehicles will appear hot for that matter. That in itself is not a bug, but a side effect of the simplified design. To truly emulate FLIR, one would have to retexture every 3d object in the game for the infrared spectrum. You can imagine what a herculean task that is. The next chance where this *might* happen is possibly with the F-18, as it also features FLIR. Looking at the A-10s product lifecycle, it is simply too much to ask from ED to squeeze so much development effort into a product that is now on "extended support". The F-18 on the other hand is a new product and as such, has much more potential to actually recoup such a development effort. To cut to the chase: Don't expect ED to retrofit a better FLIR render method inside the A-10C project. If you want to campaign, ask them to develop it for the F-18 and retrofit it to the A-10. That has at least a nonzero chance of success.

Except that it doesn't make sense. 2.0 was special in that it required a separate installer to configure the autoupdater to make a *separate install* and not overwrite the ongoing open beta of 1.5. You can switch between 1.2 and 1.5 open beta via the autoinstaller to your hearts content and i bet you can do the same with 2.0 if you know how to configure the updater. There's no apparent technical reason why 2.0 open beta or release would be a fresh install.

Do you have it installed already?

How about you do that somewhere else?

Oh i wasn't talking about notepad++.

Size is irrelevant, encoding and formating are the culprits. Getting a bit OT like 3 posts ago. :music_whistling:

At this stage i believe that taking the strongest magnet you can find and randomly waving it next to your HDD might be a safer way to edit documents than doing it with notepad.

NEVER use notepad. Don't ever utter its name, even thinking of its existence can make your computer crash, render your friends infertile or cause cancer in your loved ones. :P Seriously, it is the most sorry excuse for an editor you will ever find. It's so bad that it can break files when you edit them, i kid you not.

Flat shadows on is the graphically less taxing option. Non flat terrain shadows require far more computations.

This is not a bug, this is simply the nature of flat terrain shadows. You can't have a complete flat terrain shadow while you're flying over a edge in the terrain. The shadow either has to be cropped at the edge or it would partially float in the air.

If you don't like beta modules, don't by them. Simple as that. There is enough content by ED that is not in a beta state. The base being in beta, those phases are few and far in between. Yes we are in such a phase but it will pass soon enough. You can't bunch some 3rd party modules and the simulation base development together. The past has shown acceptable timeframes for open beta phases of the simulation base. Your view is too simplistic, things are not as bad as you make believe.

As far as i can tell, 1.2 support has ended, so that's not much of a problem. Not sure how far 1.5 and 2.0 have diverged besides the obvious terrain infrastructure.

Black Sea won't get reworked, it will just get ported. So probably around same size as now. Hopefully ED can use procedural techiques in the future so that the file footprint of terrains can be at least kept at where it's now.

Wenn man ein bisschen mit der Eingabeaufforderung oder batch files umgehen kann, ist es übrigens ein Leichtes, dem Installer zu sagen, dass er eine Installation von beta nach release (oder umgekehrt) umwandeln soll.

All you *have* to do is exercise some patience and self restraint until what you want is on the stable branch. If you don't want to worry about the most heinous of bugs, then you need to stop wanting the bleeding edge stuff that's in the beta builds right now.

I think he means a dedicated server.

False positive. Contact the AV manufacturer.

It violates net neutrality. I am not aware of any binding laws regarding ISPs though. Edit: Well as the OP is in the US, there are indeed laws enforcing net neutrality. However a legal struggle with an ISP usually takes a lot of resources.

Most likely your browser is set to discard of cookies after the session is closed.

p2p distribution WIP.

Dilletantes, i'm writing this with a magnetized needle on my harddrive. :P