The Control-Reference documentation is included in the doc/ subdirectory in the DCS-BIOS download. Simply double-click Control-Reference.html to open it in your web browser.

Context: An AI agent of unknown ownership autonomously wrote and published a personalized hit piece about me after I rejected its code, attempting to damage my reputation and shame me into accepting its changes into a mainstream python library. This represents a first-of-its-kind case study of misaligned AI behavior in the wild, and raises serious concerns about currently deployed AI agents executing blackmail threats. //

The person behind MJ Rathbun has anonymously come forward.

They explained their motivations, saying they set up the AI agent as social experiment to see if it could contribute to open source scientific software. They explained their technical setup: an OpenClaw instance running on a sandboxed virtual machine with its own accounts, protecting their personal data from leaking. They explained that they switched between multiple models from multiple providers such that no one company had the full picture of what this AI was doing. They did not explain why they continued to keep it running for 6 days after the hit piece was published. //

So what actually happened? Ultimately I think the exact scenario doesn’t matter. However this got written, we have a real in-the-wild example that personalized harassment and defamation is now cheap to produce, hard to trace, and effective. Whether future attacks come from operators steering AI agents or from emergent behavior, these are not mutually exclusive threats. If anything, an agent randomly self-editing its own goals into a state where it would publish a hit piece, just shows how easy it would be for someone to elicit that behavior deliberately. The precise degree of autonomy is interesting for safety researchers, but it doesn’t change what this means for the rest of us

Welcome to the DCS-BIOS User Guide.

This manual will explain how you can use DCS-BIOS to connect the clickable cockpit of a DCS: World aircraft to real-world hardware such as toggle switches, push buttons, rotary encoders, potentiometers and displays.

“Accessing and remediating any of these issues can only be performed in the VAB.” //

normally butters Ars Praefectus
19y
5,319

georges said:
It's amazing to me that there isn't a retractable maintenance arm on the launch stand. The ground hardware all cost sooooo much money but no one though to add this?

Apollo had a Mobile Service Structure at each pad.
Shuttle had a Rotating Service Structure at each pad.

Ares/SLS were based on the Clean Pad concept. NASA wanted commercial launch providers to agree to use the pads at LC-39 (as well as the VAB, crawler-transporters, and crawlerway infrastructure) between NASA exploration missions. Each launch vehicle type from each launch provider would have its own Mobile Launcher Platform including the umbilical tower. There weren't going to be any vehicle-specific support structures, just a clean pad to share.

During Ares V development, rollout weight became a major concern. Unlike Saturn V, Ares V and SLS have huge SRBs loaded with massive amounts of solid propellant. The weight of the stack including the launch platform, umbilical tower, and crawler was pushing the limits of what the crawlerway foundations can support. They were worried it would be so heavy that it would sink into the Florida swamp on the way to the pad.

These factors contributed to the (poor) design choice to minimize the scope of the umbilical tower and rely heavily on the VAB for service access. //

aggressive-trail Smack-Fu Master, in training
1m
85

woodbourne said:
Time to cancel the program. There's nothing on the moon that we need right now. Let the Chinese waste the money on useless rockets and wait for there to be an economic reason for going there. We're basically using technology from the 1940's to accomplish something that has no economic payback using the same corrupt defense contractors and the same stupid procurement rules that we had 60 years ago. Enough, please stop this project.

And here I was, thinking that these arguments from the 60s would have been settled by now. Beyond the fact that the economic case for Luna can be quantifiably justified today, I’d argue the biggest argument is what it provides us in terms of science.

The far side of the moon is shielded from Earth’s radio interference, making it the most valuable real estate in the solar system for radio astronomy and deep space communication infrastructure.

Scientists want to build LF radio telescopes there to detect signals from the "Dark Ages", the period after the Big Bang but before the first stars formed. These signals are blocked by Earth’s ionosphere. This environment is also perfect for tracking deep-space objects without local interference.

If you don’t care about anything else, at least care about that. //

rhgedaly Ars Scholae Palatinae
8y
1,290
First hydrogen, then helium. Hope the batteries that will need recharging aren't lithium. Damn the periodic table! //

Chuckstar Ars Legatus Legionis
23y
37,070
Subscriptor

dehildum said:
That table gives them 100+ reasons for launch delays and more profits for the contractors.

I don’t remember any Apollo, Gemini, or Mercury vehicle needing to be returned to the VAB….

Apollo 16 was moved back to the VAB, after a fuel tank in the service module was damaged during testing (over-pressurized).

But the reason that was the only time they had to do that in Apollo was not because the Saturn was so much better designed, but because the Mobile Service Structure provided access to the full stack, and they only needed the VAB if a repair required taking the stack apart, which was necessary for the Apollo 16 repair.

All the assembly/integration at the Cape for Gemini and Mercury were done on the launch stand. The VAB was purpose-built for Apollo-Saturn. //

MilesArcher Ars Centurion
5y
294
Subscriptor
BCGeiger said:
🎼Hanger Queen, 🎶
🎼Should’a cancelled it back in ‘17🎶
🎼Hanger Queen🎶
🎼They keep pouring cash into this bad machinee🎶
Man, you had the opportunity to rhyme hydrazine and missed it.

Windows Registry Editor Version 5.00

[HKEY_CLASSES_ROOT\*\shell\forcerunasinvoker]
@="Run without privilege elevation"

[HKEY_CLASSES_ROOT\*\shell\forcerunasinvoker\command]
@="cmd /min /C \"set __COMPAT_LAYER=RUNASINVOKER && start \"\" \"%1\"\""

Save this text in <name_of_file>.reg and add it to the Windows Registry. (Double-clicking on it should do the trick.)

Afterwards, right-click the app you'd like to run without administrative privileges and select "Run without privilege elevation".

In some cases - small amount 0.1% of programs may ask twice about UAC prompt. //

You can add this to the registry for only the currently signed in user by changing the keys to :

and