You can handle whatever comes at you. Blur, commence the breach.
Did I miss something or wasn't Joe supposed to attempt to hack the door open and the breach being only a failsafe in case the hack fails?
M127 Member
- Last Seen: 9 yrs ago
- Joined: 11 yrs ago
- Posts: 281 (0.07 / day)
- VMs: 0
-
Username history
- M127 11 yrs ago
Status
User has no status, yet
Bio
User has no bio, yet
Most Recent Posts
Did I miss something or wasn't Joe supposed to attempt to hack the door open and the breach being only a failsafe in case the hack fails?
also damn, verona, that messin with the mech crap had to have eaten up almost the entire four hours.
Probably. The exact time is up to the GM. xD
I wonder what'd happen if someone was to play this song at Madison while piloting: https://www.youtube.com/watch?v=8peoKZ-l4_4
Joe simply skimmed the dossiers, only paying models he didn't recognize extended attention, there was no point in reading what one already knows. After the briefing he gave Jingo a neutral "Is there anything we need to clear up before this?" look, it was easy to mistake for any other requesting look though.
Once everything was clear Joe approached his NC to get inside; some engineers were still doing checks, mostly software-checks, but nothing that would hinder him from entering. As he sat down, Joe didn't connect, as he had other priorities, but he still closed the cockpit's hatch.
After the hatch closed and he was out of sight, Joe quickly reached into one of his pockets, pulling a small memory-card out. If he didn't make a mistake, it should contain a script, that, when run, crashes most NC's control programs. The NC should then switch to a fallback console-interface(provided it has one at all); terrible at controlling the NC, but very good at managing and configuring the internal computer. Joe inserted the card into a designated slot, and used the manual controls and a tiny screen to order the computer to run the script: The tiny screen was instantly flooded with error messages and then went black, leaving only a blinking white underscore at the top left of the screen. An engineer checking some software shouted a curse at the crash, drawing the attention of everyone in the hangar to himself.
Joe continued by plugging himself in, obviously the connection itself failed due to the crashed programs though, which Joe fixed bypressing the 'reset' button, which was well hidden behind the seat. The button reset the program processing the input from the plug, allowing Joe to use the command prompt to do a deep and direct check and configuration of the systems.
The reason why he did this was mostly the inconvenience of the default configuration, in addition to the standard variations of that configuration also not meeting his requirements, as they mostly were sensitivity or feedback options, or a control-remapping[mostly to allow controlling additional limbs in NCs that had them]. He was ok with the input for the legs being directly mapped to the corrosponding leg-joints, as the legs weren't really useful for controlling anything except for one's stance, however, he hated a direct mapping of the arms, as that only left voice-command for any non-motoric function access/control. The main problem he had with voice command was that one can only speak so fast, while motion or motion-controlled-controls[keyboards, buttons, switched] are much quicker to be performed and parsed.
As such he preferred to instead have his upper body not be mapped to the NC, but instead to a virtual body in front of a virtual control-board with frequently used controls on it, and also a virtual keyboard to access not so frequently used functions. Mods like these weren't really freely available from trustworthy sources, so he had to create it himself using whatever was already installed on the computer. Luckily most NC's computers had a tiny mostly hidden virtual 3D environment for debugging purposes. It would have to suffice for him to do it in time, especially if the engineers were trying to fix the 'problem' in the software while he was working on it.
As a quick and dirty solution Joe simply killed the processes allowing the laptops, notebooks and other devices of the engineers to connect to the NC's computer. Promptly a second curse echoed through the hangar; a laptop and its screen, separated, flew after it.
Time passed until he was finished, and Joe was exhausted at the end. Apart from the digestive system, the human brain was the most energyhungry part of the human body.
He still had a littlebit of time until the mission started, so he decided to rest while listening to some comm-chatter.
Once everything was clear Joe approached his NC to get inside; some engineers were still doing checks, mostly software-checks, but nothing that would hinder him from entering. As he sat down, Joe didn't connect, as he had other priorities, but he still closed the cockpit's hatch.
After the hatch closed and he was out of sight, Joe quickly reached into one of his pockets, pulling a small memory-card out. If he didn't make a mistake, it should contain a script, that, when run, crashes most NC's control programs. The NC should then switch to a fallback console-interface(provided it has one at all); terrible at controlling the NC, but very good at managing and configuring the internal computer. Joe inserted the card into a designated slot, and used the manual controls and a tiny screen to order the computer to run the script: The tiny screen was instantly flooded with error messages and then went black, leaving only a blinking white underscore at the top left of the screen. An engineer checking some software shouted a curse at the crash, drawing the attention of everyone in the hangar to himself.
Joe continued by plugging himself in, obviously the connection itself failed due to the crashed programs though, which Joe fixed bypressing the 'reset' button, which was well hidden behind the seat. The button reset the program processing the input from the plug, allowing Joe to use the command prompt to do a deep and direct check and configuration of the systems.
The reason why he did this was mostly the inconvenience of the default configuration, in addition to the standard variations of that configuration also not meeting his requirements, as they mostly were sensitivity or feedback options, or a control-remapping[mostly to allow controlling additional limbs in NCs that had them]. He was ok with the input for the legs being directly mapped to the corrosponding leg-joints, as the legs weren't really useful for controlling anything except for one's stance, however, he hated a direct mapping of the arms, as that only left voice-command for any non-motoric function access/control. The main problem he had with voice command was that one can only speak so fast, while motion or motion-controlled-controls[keyboards, buttons, switched] are much quicker to be performed and parsed.
As such he preferred to instead have his upper body not be mapped to the NC, but instead to a virtual body in front of a virtual control-board with frequently used controls on it, and also a virtual keyboard to access not so frequently used functions. Mods like these weren't really freely available from trustworthy sources, so he had to create it himself using whatever was already installed on the computer. Luckily most NC's computers had a tiny mostly hidden virtual 3D environment for debugging purposes. It would have to suffice for him to do it in time, especially if the engineers were trying to fix the 'problem' in the software while he was working on it.
As a quick and dirty solution Joe simply killed the processes allowing the laptops, notebooks and other devices of the engineers to connect to the NC's computer. Promptly a second curse echoed through the hangar; a laptop and its screen, separated, flew after it.
Time passed until he was finished, and Joe was exhausted at the end. Apart from the digestive system, the human brain was the most energyhungry part of the human body.
He still had a littlebit of time until the mission started, so he decided to rest while listening to some comm-chatter.
The IC-post is extremely short as I had no idea what to write about, as the condition was not met.
Seeing everyone head to the briefing room rather quickly Joe silent followed. He didn't see a need to thank Alex and Slinky for the ride, they had simply done their job.
He also got a look at his NC in person, and surprisingly wasn't too impressed. All one could tell from a look at this distance was already described in the file of the NC.
Joe didn't recognize any of the engineering personnel, although he heard quite a lot of stories about his father's former colleagues from him.
He also got a look at his NC in person, and surprisingly wasn't too impressed. All one could tell from a look at this distance was already described in the file of the NC.
Joe didn't recognize any of the engineering personnel, although he heard quite a lot of stories about his father's former colleagues from him.
(by posting this post I confirm to be present whenever any roll-call occurrs within this RP from any point in time)
Edit: My IC post will either be after @NuttsnBolts's or a collab with him, as the actions of his characters will have a major impact on Joe's behaviour here. Well, the impact will simply be one condition which is either met or not met, but it will still dramatically affect the post.
Edit: My IC post will either be after @NuttsnBolts's or a collab with him, as the actions of his characters will have a major impact on Joe's behaviour here. Well, the impact will simply be one condition which is either met or not met, but it will still dramatically affect the post.
Same here pretty much. Nothing I could make a sufficiently long IC-post about.
Since nobody is posting at all, I guess it means it's safe to move on and timeskip to once harold is done? @LHG100
@LHG100 Sure thing! Might need a link to it though, if it was pasted earlier I miiiight have missed it lol
titanpad.com/UY7nuvmAo4
© 2007-2026