The solution is to use image-builder and bake your config into the image.

If it's not feasible, I can see an argument that large enough companies should be required to provide in person support options.

Facebook defintely has enough money to facilitate this.

The inverse of that is that this creates a huge market in the EU, where you don't have to be the best in class and the most capitalistic - you can be good enough and still make a good buck serving local clients.

Inside the game loop, we would keep the global tick counter that incremented on every tick, and timeouts would be based on that rather than on UTC.

The tick counter was updated only when the game logic was actually running. Our approach to pausing was to not run the functions that handled frame updates or physics updates, and to only run the rendering functions.

Generally we would never care about actual world time other than for some timeouts like for network (as the time passes for everyone), or for easter eggs like changing the tree models for Christmas or so.

I don't think anyone serious would implement event timers based on real time.

Slaving heatseekers to radar is the standard way of employing them. I reckon by "having flown around" you're referring to DCS, which is absolutely unrealistic when it comes to engagements.

>Clearly any passive IR detector thats theorized to exist for years either doesn't exist or doesn't work very well. In theory, a smart enough IR camera should be able to notice something very warm indeed is getting rapidly brighter as it approaches you. In practice, these don't exist, or don't work. "Oh yeah they didn't have those when I was in, but they totally have them now" for the last 30 years. Apparently, not yet in 2026.

MAWS exist and they're employed on a lot of aircraft. I don't believe Strike Eagles have them though. An F-35 would get a missile warning for a heatseeker, it's not science fiction technology for quite a while now.

>I find it unfortunate that people who do this for a living can't legally comment, people who do this for a hobby are not asked or actively ignored despite extensive practical experience, and people who mostly have a grift of looking authoritative for legacy media get automatic blind belief despite sometimes spouting total nonsense.

You don't get practical experience by playing flight simulators, it's not comparable to how planes are employed as weapons systems.

I guess we will get the future that was seen in Sun Microsystems with their Ray thin clients after all, but in a way that will provide complete control over population rather than mobility.

What is in cards for us is complete slavery to digital systems.

Absolutely, it's their own network.

>being brought to their premises

Depends on the local laws. Where I live, they can either deal with it, or provide a secured storage space for the duration of the visit.

Either way, if a corporation wants their employees to use a device, they are obliged to make one available. Surrendering your private equipment to their management makes it not yours anymore.

Corporations cannot require you to have your personal devices be managed by them. If you're surrendering your own gear to a company, it stops being your own device.

It's a communication issue at the core, and always doubling down is not making it any better.

It portrays the whole project as being unreliable.

That post has been deleted.

As far as I can tell, nothing has changed other than obscuring the leadership of the project a tiny bit. strcat is still active here in the comments.

Whether you believe it's morally right or wrong, that doesn't matter - he did violate several high profile laws.

"Hypersonic" weapons used in current conflicts are nothing more than a glorified long range missiles that are useless if you can't launch them from the air. They're also currently statistically not significant due to their low amounts.

We're talking community servers here, not corporate ones.

>Sure, the cheater will eventually run out of IPs. But you might as well save both yourself and the cheaters some time and hassle and just add 0.0.0.0/0 and [::]/0 to your IP banlist right now. You will effectively end up with the same result if you're willing to chase every cheater across the address spectrum.

It's not going to end up with 0/0 as the final result. You're assuming that almost any address is available to the cheaters, but that's simply not true. By blocking datacenter IP ranges and Tor exit nodes, you've stopped most of the ways cheaters can easily change their IPs.

You ban their own home IP address, and what are their options? 1. They get a VPN and don't make it through because that IP is already blocked. 2. They hope their ISP allocates a random IP from a range, so if that works they come back and they instead get a range ban. 3. They get a residential VPN and start burning through those precious IPs.

You don't have to chase cheaters if you're running a server. You ban them once or twice and call it a day.