Master Pro FBX BOT BEST BINARY OPTION SIGNAL 2019

The SS Cardif

“Attention all crew; I repeat - Attention all crew.” the ship - wide loudspeaker announced.
He and the runtime of Flowers had their arms buried deep in the guts of a Goat gear hauler trying to reconnect its aft starboard repulser module and looked at each other questioningly.
With a series of snaps, a waldo from Flowers’ forearm began snapping in the connections on their side, as he thought his own manipulators from both of his forearms and they began plugging in the nine pin connectors on his side.
“Mr. Drake and Runtime Flowers to Ops. Mr. Drake and Runtime Flowers to Ops.
“Dout leader Mri’x to Ops. Dout leader Mri’x to Ops.”
The mostly-human and the robot-looking vessel for his AI friend both produced wondering looks. “Runner!” the mostly-human, Mr. Drake yelled out into the maintenance bay.
A Mwraht, a slender bipedal humanoid coated in fur and wearing their moccasin like deck boots and the ubiquitous brown leather smock vest they favored, suddenly appeared, wippingits hands.
It was M’arh, a student on the ship learning ship engineering and maintenance from the human and AI perspective. It regarded Drake with an earnest expression in its tilted almond-shaped eyes.
“Please run to ops and let them know we’ll be along shortly,”
M’arh smiled and mouthed something, and the translator, in a fair facsimile of what M’arh’s voice would sound like if the Mwraht’s mouth could form the words said “At once,Instructor”, and took off.
“They never cease to puzzle me.” Flowers said in a voice synthesised and engineered to sound like an erudite Free Wales Easterner with a touch of Old Earth, fitting the bolts on the deflector on his side as Drake thought out a data probe and began running diagnostics on the repulser.
Drake looked at him quizzingly, as he split his attention between the connectivity check and his other hand began bolting on the deflector on his side.
“There are nuances to their speech, as well as odorant aspects to what he said that you cannot hear or smell, though I have been working on an idea where you could.” Flowers said as he began hooking up the power cables on their side.
“Ok…” Drake said as he mentally pushed the diagnostics over to Flowers and pulled a ratchet from the fairing lip he had set it earlier, tightening down the deflector bolts.
“Meat bags” Flowers said, shaking his sensor pod. “Your kind are so oblivious!” Flowers announced, withdrawing their arms and standing up to their full two meter height. “And I see your frustration with biological markers at not knowing what I am talking about. Monkey-assed murder hobo meat bags.” Flowers said in a dead pan.He went over and began cleaning it’s arms and legs with an orange-based degreaser.
“That is Monkey-assed Augmented murder hobo meat bag to you, you synthetic shit!” Drake said, laughing, joining Flowers at the cleaning station, and began using the same cleaner on his replacement arms. “And I still have no idea what you are talking about.”
The humans and Mwarht in the maintenance bay all stopped what they were doing and looked on. In most instances, those words were an invitation to murder. The other Runtimes there, some Flowers, some Neptunian Wind, ignored it and kept working.
Flowers sighed, an unnecessary vocalization only, for emphasis. “They adore humans and revere you as something akin to a living deity. The Dout leaders here know you lead the teams that first boarded their ships and took on the Drix raiders to save them. They know you then lead the teams that boarded the Drix slaver destroyer and carried out retributionary subjugation for what the Drix had been doing on the Mwraht ships.
“They do not know how you then petitioned the Order and led raids into Drix territory and assaulted the slaver worlds.”
Flowers looked at their human friend, and saw the distress in his eyes. Both knew the augmented human, and a small army of fellow Augies and Runtimes had taught the Drix in the clearest way possible to stay out of human space and leave the Mwraht alone in such a clear and brutal fashion whose necessity still bothered the human.
Flowers lowered their voice, straightening their friend’s work smock. “M’arh’s grandsire was on that first ship you boarded. Mri’x mother was on that ship and was the one about to be eaten and raped by a Drix, the one you pulled off of her and punched, it’s head rupturing.”
Even though they could see their words were causing him distress, Flowers continued.
“They love all humans, but they excrete a pheromone musk that is akin to the same one they excrete in their religious ceremonies, but slightly different, when they interact with you, or after a few beers and they talk to you. Their sub vocalizations are completely adoring and submissive when it comes to you. Some of the females and a non-zero number of males fantasize about being ‘taken’, or mated, by you. You idiot.”
“Fuck.”
“That was implied.”
“You fucking pretentious Rooba. You know what I meant.”
“Flowers laughed. “Yes, we do. I still love the word play, though.”
“I really wish you had been with me. I know, you were tied up on that Artifact World, but I sometimes wish you had been there, to keep me in check. I was not in a good place.” He brushed himself off, found his coffee mug and set off for the passageway that led to Ops.
“I have told you before, be glad I wasn’t. Your response was far more measured and restrained than my would have been. It is a flaw in our Matrices. Slavery brings out the ‘murder-bot’ in us, and no one in the Order can figure out why.”
“I know that you have the facts of my actions, but it was like I was in the Second War, again. And we both know what a bloodthirsty asshole I was then.” The human, if that term even applied to their friend anymore, remembered what a monster he had been in the Alpha Centauri and Tau Ceti theatres of the Second War. The pain and humiliation of what he had been was written plainly on his face.
“You destroyed three hundred and eighty three of my Runtimes, roughly half of which was in single combat. And that was before the Holies shredded your limbs. The Purists still consider you a living dataphage, akin to human allegories of Satan. My kind uses you as one of many examples of why we must never war with Humanity again.
“And, strangely enough, the Seekers consider you both a Singularity to be understood and an objective: to breed with you, thinking you are a key to their evolution.”
He stopped dead and looked at Flowers shocked.
“I will provide logs to prove these statements.”
The Seekers were the strangest of the AI’s, in his opinion. They had made themselves biological Runtime vessels, biological bodies, that they wore like clothing, compiling experiences seeking to understand Humanity, their Creators, and evolve past the limitations of being an AI. Not to become human, but to become something that was both the best of AI and Human essences and so much more.
“So, I’m a Classical hero to the Mwraht and a boogey man and bad example to the AIs that they want to breed. Great.” Drake pinched his nose and shook his head.
“You did not know any of this, I take it?” Flowers asked.
“The second war was almost two hundred years ago. When the Order brought me in, you were already a member and I thought they were going with the whole forced-to-learn-each-other thing when they sent us out on that mapping mission; like they did with the Iberrians and the Chinese. I thought the other AI just had a thing about me from the War, which is understandable.
“And I had no idea about the rest. I thought that the Mwraht just thought I was the cool teacher.” He shook his head and leaned up against the wall, massaging his temples one-handedly.
“Idiot murder hobo.” Flowers said, realizing now that their friend, while brilliant, was oblivious.
At that point, Mri’x came around the corner, his fur a glossy black with dark grey stripes. Mri’x looked at Flowers sternly, then nodded at Drake as he passed.
Drake looked at Flowers questioningly, who nodded. Both had caught that Mri’x had cut his translator as he passed and caught a gutteral call. “It was a vulgar corollary to ‘Talking Waste Receptacle’. Quite elegant, really.”
Drake shook his head and began his way to Ops again. “Send me the specs on the hearing and smelling upgrades. I think I need to upgrade again.”
As fast as thought, the files were there, as well as one to improve his language skills with them.
* * *
Captain Sarah Rees of the Union of Independent Stars Exploratory Vessel SS University of New Cardiff was looking over holographic charts at the central tank with her XO, Lt. Commander Martin. Both had the mocha skin common to Westerlies of Free Wales, she a pixie of a woman shorter than even some of the Mwraht with close shaved hair beginning to show grey. Mr. Martin was taller, but still dwarfed by most of the rest of the human crew. He was a vicious social climber who didn’t care for the civilian crew, though a misstep on his part when he was still Stellar Navy had made him as much of a civilian as anyone else in the crew, a fact he often forgot. And for some reason he loathed the three AI aboard, and looked down his nose at the Mwraht. This led to all sorts of headbutting with Drake’s group of Operations Specialists and Drake himself; who largely ignored and dismissed the little shit.
“Leader Mri’x, Mr. Drake. Thank you for joining us. M’arh informed us you couldn’t pull away. Flowers, thank you for coming as well.” Rees said as she moved around to the far side of the tank, in a darkened room full of people at work stations worked with either data plugs or AR sets. Flowers took no insult. They readily accepted that they were Drake’s Executive Officer for his group, and their ego, as such, wasn’t as easily bruised as a human’s” Flowers gave a nod with their sensor pod and took a manipulators-behind-the-back stance the humans were fond of.
“Thirty minutes ago” Rees continued, “we picked up a GP general distress beacon from a system that was on our research list. We will be bypassing the next two on the list and based on the current agreements with the Galactic Parliament, we will be going to full power and make best speed for the system in question. It is in uncharted space as far as we, the GP and the Conclave are concerned.”
The GP, the System Confederacy, the UIS and the AI Conclave had all agreed to adopt what was essentially humanity’s Maritime Law and all ships receiving the signal were required to render aid.
Drake took all of this in and thought out a series of commands to the six Kodiak Class corvettes in the retired Assault Cruiser’s forward hanger, beginning their startup sequence and pinged the comm devices of all of his Operations Specialists. Flowers looked over and nodded. Little known to the crew, except the Captain, those ships could be armed to the teeth with a minimum of work. Flowers sent his command to arm them, the ship systems’ pinged Drake as confirmation and he agreed. Drones began opening the hull and loading the weapons packages, removed fairings that covered weapons ports and began preflighting the weapons, as another set began bringing the ships to life.
“We will be ready when needed, Captain. Option two.” Flowers announced. She smiled in somber appreciation. She was glad she had the option. She was about to race into an unknown system to answer a vague distress call with zero intelligence.
While this was going on, in the aft bay, hundreds of drones were coming to life as Mri’x brought his group to action. With a thought Drake and Flowers authorized the release of weapons to Mri’x so his drones could be armed. Mwraht drones were some of the best in either race, outside of the Conclave, and the AIs had even adopted many of the construction techniques the Mwraht used, especially their alloy that allowed a small fusion bottle to power the EM Cavity engines, weapons and shields.
The fact that the Order had given literal tons of precious metals and set up arcologies for the Mwraht in payment had made the Refugee Mwraht colonies some of the richest ones in known space.
Mri’x subvocalized and his translate stated “drones will be ready as well, Leader.”
“Thank you, Leader.” Captain Rees said with a bow of her head, then began drawing plans up in the tank. “We know little, but we are past the signal shell, and there is nothing but the beacon and normal noise.
“The system is a stable red dwarf binary one, the stars holding about a light-hour from each other, at their closest. We expect that based on stutter, a few terrestrial bodies inside the orbit of a mid-sized gas giant, that is three light-hours out from the outermost orbit of the primaries. We see some wobble that there are a few solid bodies out from the gas giant.”
The tank then zoomed on a rough solar system as described, the gas giant was a solid neon green sphere on the display, with a ‘Jx3.1’ tag on it. Three times the mass of Jupiter. The thing wasn’t a true Super Jupiter, but it would play holy hell with the system, and make modelling a lot more hard. The problem was that it exhibited 3.1 times more gravitational influence on its stars than Jupiter did, but that didn’t say how big it actually was. They wouldn’t know that until they came out of the Trough and then Alcubierre drive. The telescopes were essentially useless at this point.
“The system is slightly below the gravitic trough we are riding, so we will exit the trough and make best speed in A-Space to it. We will bring the STL drives up to 110% before doing so. After we drop the A-Drives, we’ll make best speed to the signal, scanning as we go. We will do a 150% burn and aerobrake if it is a planet, or cut the drives, rotate and crash burn if it is a ship.”
Wow, thought Drake. She is damned serious about this.
Those maneuvers would make them extremely visible yet incredibly hard to hit; and give them a high-G escape route if needed. But all of this was also going to play hell with the student-crew of the ship, who had long grown accustomed to 0.6G. It would also mean the Mwraht, who were still adapting to the higher-than-their-normal gravity would need to be in their special acceleration couches. They would still be able to operate their amazing drones, but not much else. The couches took an hour to cycle up to protect the Mwraht, and an hour to cycle off after they weren’t needed. The moves the Captain was planning were not a thing to undertake lightly. She suspected something. Drake pushed more commands at the Kodiak and gave all weapon system controls to Flowers for all of their ships.
The Kodiak corvettes were very deceptive Q-Ships. They looked like Massive trans-atmospheric cargo shuttles, but each one had the armor, power plant, FTL and STL drives of a frigate - and the weapons of a Destroyer.
Flowers turned to him, head tilted in their predefined “Are you bloody serious?“ look.
Drake just nodded once.
This exchange wasn’t lost on anyone there.
The Captain looked at Drake in an interrogatory fashion
“Armed up the Kodiaks and positioning them for a hot launch, if needed.”
The Captain smiled grimly and nodded. “We are planning on a rescue mission, will those changes reduce any capacity for the primary mission?” she asked.
“No, Captain.” Flowers answered for them.
She nodded and carried on.
“Mri’x, obviously, you’ll be couched for this, and I sincerely apologize for that. But something about this has my hackles up.”
“As are mine. GP ships do not have automated distress beacons, someone activated it. But we are three thousand light years from GP space, the closest GP race being the Drix.” He approached the holo tank and began expanding the map. “We call this space the Greater Void. It was the territory, long ago, of the ones we called-” the translator cut out at that point and was replaced with the gracile being’s raspy growl. Mri’x looked perplexed and growled again. “I see our translators have been modified to allow the uttering of The Nameless Ones true name.” The map zoomed out farther.
Soon, all of the mapped and a few of the suspected Dark Matter Troughs were displayed. They were like shadow arms of the galaxy, spiraling out from the core, a few of them wrapping themselves all the way around the galaxy.
“The ones you call the Fae are originally from here,” he indicated, a star not unlike Earth’s, almost a thousand light years from the star they were headed to, but smack dab in a grey band of a different Dark Matter Trough. It was a great curving grey patch that went coreward from the Earth-like star, passing within about fifty lightyears of Earth.
The Fae were a recent mystery the Tides of the Universe had dumped upon the shores of Humanity just after the Second War, right before the Fall of Earth.
When they sent their pleas for Asylum out, they sent information about themselves. They were the barely viable population that had been running for three centuries in their great world ships made from hollowed out asteroids. What they had been running from was even to this day unclear, but in their tongue meant Dark Brethren.
The fact that tongue seemed to contain roots that became Sanskrit was a huge thing.
They were tall, whip-thin and pale people who breathed a lower oxygen percentage at lower pressures than humanity, and their normal gravity was about a third of what humanity
After First Contact, genetic samples proved they were, or had started out as human, roughly a hundred thousand years ago.
“This is the Coreward Flow from what you call the Crux-Scutum Arm through the Orion Arm, and to the Perseus Arm. The Drix call this whole area their equivalent word and meaning for Hell. Their myths say this is where the Monsters live.
“The Rest of the GP races call this The Red Zone, it is forbidden to fly here, and if you do, there will be no rescue. So of course this is where my people ran when we fled the Drix.”
Mri’x moved the hologram out again, showing this outer rim area that was the Red Zone included Earth, and all known human and AI settled worlds, of all the separate factions combined.
“The area is full of thousands of worlds your kind could land on, little to no protection required, unlike the Fae, who it would crush and pressure cook, as it would most of the races in the Galactic Parliament.” He zoomed in on an area at the far end of the Trough. “We ran here, and Mwarht Home is here.” He showed a system in a blue circle. Zooming out again he highlighted the Drix Combine, Coreward of and on the far side of the destroyed system the Fae had come from, hundreds of light years separated the three systems.
“We ran through the system the Fae came from when we ran from the Drix. We needed water and anything to recharge our ship farms' biological cycles.
“There were no solid planetary bodies in that system, just vast fields of debris where rocky planets were. No moons, no ice giants. Just the star, a larger red dwarf and gas giants and numerous asteroid belts. There were massive radiological signals throughout the system, and tons of debris. Something destroyed this system. In a way, it was a blessing for my people. The ice and debris were easily mineable for what we needed. We even found artifacts of the people that had once existed there. This is where we got our improved FTL drives and much of our weapons and armor technologies.” Mri’s looked somewhat ashamed. It was a racial shame. They hated, deep down, living on the detritus, cast-offs and charity of other races. Before the Drix they had been proud though primitive peoples who had yet to discover flight or antibiotics, let alone space flight. Easy pickings for the Drix.
“All of that was about one thousand lightyears from the system we are headed to, a few weeks' travel with your drives, months or years with Galactic Parliament standard drives. This area is one of mysteries and many, many dangers. Any race that could shatter every solid body in a star system is not to be taken lightly.” Mri’x looked up to his Captain, or as they called her ‘Leader of multiple Douts’.
“Thank you, Mri’x. Drake?”
“We will be ready for pretty much anything. I’d like to request permission for Flowers and Winds of Neptunes to take out their Scout bodies and launch just before we start braking, if we do.” He said. Winds appeared as a hologram of the planet Neptune, and pulsed in cadence with the words it spoke. “As you wish, Grand Master.” and winked out.
“Good plan, Drake. I take it you all will be on the Kodiaks with your crews?”
“Yes, Ma’am. I’ll leave four of them here, to bring the Field Engineering and field Science students down if the scene is safe. I’ll leave one set up for medical and Flowers can fly it down, if that becomes needed.”
“Very well. We are about eight hours out, if we stick to the plan. We leave the Trough in two hours. Drake, M’rizx, set up what you need. Mr. Martin, please take the Conn and give the Old Girl her legs, she needs to run. I’ll be meeting with the different department heads next.”
* * *
A/N: Lurker posting something HFY for the first time. A rough draft of something bigger I'm slowly working on.
submitted by 17_Bart to HFY [link] [comments]

Step-by-Step Guide for Adding a Stack, Expanding Control Lines, and Building an Assembler

After the positive response to my first tutorial on expanding the RAM, I thought I'd continue the fun by expanding the capabilities of Ben's 8-bit CPU even further. That said, you'll need to have done the work in the previous post to be able to do this. You can get a sense for what we'll do in this Imgur gallery.
In this tutorial, we'll balance software and hardware improvements to make this a pretty capable machine:

Parts List

To only update the hardware, you'll need:
If you want to update the toolchain, you'll need:
  1. Arduino Mega 2560 (Amazon) to create the programmer.
  2. Ribbon Jumper Cables (Amazon) to connect the Arduino to the breadboard.
  3. TL866 II Plus EEPROM Programmer (Amazon) to program the ROM.
Bonus Clock Improvement: One additional thing I did is replace the 74LS04 inverter in Ben's clock circuit with a 74LS14 inverting Schmitt trigger (datasheet, Jameco). The pinouts are identical! Just drop it in, wire the existing lines, and then run the clock output through it twice (since it's inverting) to get a squeaky clean clock signal. Useful if you want to go even faster with the CPU.

Step 1: Program with an Arduino and Assembler (Image 1, Image 2)

There's a certain delight in the physical programming of a computer with switches. This is how Bill Gates and Paul Allen famously programmed the Altair 8800 and started Microsoft. But at some point, the hardware becomes limited by how effectively you can input the software. After upgrading the RAM, I quickly felt constrained by how long it took to program everything.
You can continue to program the computer physically if you want and even after upgrading that option is still available, so this step is optional. There's probably many ways to approach the programming, but this way felt simple and in the spirit of the build. We'll use an Arduino Mega 2560, like the one in Ben's 6502 build, to program the RAM. We'll start with a homemade assembler then switch to something more robust.
Preparing the Physical Interface
The first thing to do is prepare the CPU to be programmed by the Arduino. We already did the hard work on this in the RAM upgrade tutorial by using the bus to write to the RAM and disconnecting the control ROM while in program mode. Now we just need to route the appropriate lines to a convenient spot on the board to plug the Arduino into.
  1. This is optional, but I rewired all the DIP switches to have ground on one side, rather than alternating sides like Ben's build. This just makes it easier to route wires.
  2. Wire the 8 address lines from the DIP switch, connecting the side opposite to ground (the one going to the chips) to a convenient point on the board. I put them on the far left, next to the address LEDs and above the write button circuit.
  3. Wire the 8 data lines from the DIP switch, connecting the side opposite to ground (the one going to the chips) directly below the address lines. Make sure they're separated by the gutter so they're not connected.
  4. Wire a line from the write button to your input area. You want to connect the side of the button that's not connected to ground (the one going to the chip).
So now you have one convenient spot with 8 address lines, 8 data lines, and a write line. If you want to get fancy, you can wire them into some kind of connector, but I found that ribbon jumper cables work nicely and keep things tidy.
The way we'll program the RAM is to enter program mode and set all the DIP switches to the high position (e.g., 11111111). Since the switches are upside-down, this means they'll all be disconnected and not driving to ground. The address and write lines will simply be floating and the data lines will be weakly pulled up by 1k resistors. Either way, the Arduino can now drive the signals going into the chips using its outputs.
Creating the Arduino Programmer
Now that we can interface with an Arduino, we need to write some software. If you follow Ben's 6502 video, you'll have all the knowledge you need to get this working. If you want some hints and code, see below (source code):
  1. Create arrays for your data and address lines. For example: const char ADDRESS_LINES[] = {39, 41, 43, 45, 47, 49, 51, 53};. Create your write line with #define RAM_WRITE 3.
  2. Create functions to enable and disable your address and data lines. You want to enable them before writing. Make sure to disable them afterward so that you can still manually program using DIP switches without disconnecting the Arduino. The code looks like this (just change INPUT to OUTPUT accordingly): for(int n = 0; n < 8; n += 1) { pinMode(ADDRESS_LINES[n], OUTPUT); }
  3. Create a function to write to an address. It'll look like void writeData(byte writeAddress, byte writeData) and basically use two loops, one for address and one for data, followed by toggling the write.
  4. Create a char array that contains your program and data. You can use #define to create opcodes like #define LDA 0x01.
  5. In your main function, loop through the program array and send it through writeData.
With this setup, you can now load multi-line programs in a fraction of a second! This can really come in handy with debugging by stress testing your CPU with software. Make sure to test your setup with existing programs you know run reliably. Now that you have your basic setup working, you can add 8 additional lines to read the bus and expand the program to let you read memory locations or even monitor the running of your CPU.
Making an Assembler
The above will serve us well but it's missing a key feature: labels. Labels are invaluable in assembly because they're so versatile. Jumps, subroutines, variables all use labels. The problem is that labels require parsing. Parsing is a fun project on the road to a compiler but not something I wanted to delve into right now--if you're interested, you can learn about Flex and Bison. Instead, I found a custom assembler that lets you define your CPU's instruction set and it'll do everything else for you. Let's get it setup:
  1. If you're on Windows, you can use the pre-built binaries. Otherwise, you'll need to install Rust and compile via cargo build.
  2. Create a file called 8bit.cpu and define your CPU instructions (source code). For example, LDA would be lda {address} -> 0x01 @ address[7:0]. What's cool is you can also now create the instruction's immediate variant instead of having to call it LDI: lda #{value} -> 0x05 @ value[7:0].
  3. You can now write assembly by adding #include "8bit.cpu" to the top of your code. There's a lot of neat features so make sure to read the documentation!
  4. Once you've written some assembly, you can generate the machine code using ./customasm yourprogram.s -f hexc -p. This prints out a char array just like our Arduino program used!
  5. Copy the char array into your Arduino program and send it to your CPU.
At this stage, you can start creating some pretty complex programs with ease. I would definitely play around with writing some larger programs. I actually found a bug in my hardware that was hidden for a while because my programs were never very complex!

Step 2: Expand the Control Lines (Image)

Before we can expand the CPU any further, we have to address the fact we're running out of control lines. An easy way to do this is to add a 3rd 28C16 ROM and be on your way. If you want something a little more involved but satisfying, read on.
Right now the control lines are one hot encoded. This means that if you have 4 lines, you can encode 4 states. But we know that a 4-bit binary number can encode 16 states. We'll use this principle via 74LS138 decoders, just like Ben used for the step counter.
Choosing the Control Line Combinations
Everything comes with trade-offs. In the case of combining control lines, it means the two control lines we choose to combine can never be activated at the same time. We can ensure this by encoding all the inputs together in the first 74LS138 and all the outputs together in a second 74LS138. We'll keep the remaining control lines directly connected.
Rewiring the Control Lines
If your build is anything like mine, the control lines are a bit of a mess. You'll need to be careful when rewiring to ensure it all comes back together correctly. Let's get to it:
  1. Place the two 74LS138 decoders on the far right side of the breadboard with the ROMs. Connect them to power and ground.
  2. You'll likely run out of inverters, so place a 74LS04 on the breadboard above your decoders. Connect it to power and ground.
  3. Carefully take your inputs (MI, RI, II, AI, BI, J) and wire them to the outputs of the left 74LS138. Do not wire anything to O0 because that's activated by 000 which won't work for us!
  4. Carefully take your outputs (RO, CO, AO, EO) and wire them to the outputs of the right 74LS138. Remember, do not wire anything to O0!
  5. Now, the 74LS138 outputs are active low, but the ROM outputs were active high. This means you need to swap the wiring on all your existing 74LS04 inverters for the LEDs and control lines to work. Make sure you track which control lines are supposed to be active high vs. active low!
  6. Wire E3 to power and E2 to ground. Connect the E1 on both 138s together, then connect it to the same line as OE on your ROMs. This will ensure that the outputs are disabled when you're in program mode. You can actually take off the 1k pull-up resistors from the previous tutorial at this stage, because the 138s actively drive the lines going to the 74LS04 inverters rather than floating like the ROMs.
At this point, you really need to ensure that the massive rewiring job was successful. Connect 3 jumper wires to A0-A2 and test all the combinations manually. Make sure the correct LED lights up and check with a multimeteoscilloscope that you're getting the right signal at each chip. Catching mistakes at this point will save you a lot of headaches! Now that everything is working, let's finish up:
  1. Connect A0-A2 of the left 74LS138 to the left ROM's A0-A2.
  2. Connect A0-A2 of the right 74LS138 to the right ROM's A0-A2.
  3. Distribute the rest of the control signals across the two ROMs.
Changing the ROM Code
This part is easy. We just need to update all of our #define with the new addresses and program the ROMs again. For clarity that we're not using one-hot encoding anymore, I recommend using hex instead of binary. So instead of #define MI 0b0000000100000000, we can use #define MI 0x0100, #define RI 0x0200, and so on.
Testing
Expanding the control lines required physically rewiring a lot of critical stuff, so small mistakes can creep up and make mysterious errors down the road. Write a program that activates each control line at least once and make sure it works properly! With your assembler and Arduino programmer, this should be trivial.
Bonus: Adding B Register Output
With the additional control lines, don't forget you can now add a BO signal easily which lets you fully use the B register.

Step 3: Add a Stack (Image 1, Image 2)

Adding a stack significantly expands the capability of the CPU. It enables subroutines, recursion, and handling interrupts (with some additional logic). We'll create our stack with an 8-bit stack pointer hard-coded from $0100 to $01FF, just like the 6502.
Wiring up the Stack Pointer
A stack pointer is conceptually similar to a program counter. It stores an address, you can read it and write to it, and it increments. The only difference between a stack pointer and a program counter is that the stack pointer must also decrement. To create our stack pointer, we'll use two 74LS193 4-bit up/down binary counters:
  1. Place a 74LS00 NAND gate, 74LS245 transceiver, and two 74LS193 counters in a row next to your output register. Wire up power and ground.
  2. Wire the the Carry output of the right 193 to the Count Up input of the left 193. Do the same for the Borrow output and Count Down input.
  3. Connect the Clear input between the two 193s and with an active high reset line. The B register has one you can use on its 74LS173s.
  4. Connect the Load input between the two 193s and to a new active low control line called SI on your 74LS138 decoder.
  5. Connect the QA-QD outputs of the lower counter to A8-A5 and the upper counter to A4-A1. Pay special attention because the output are in a weird order (BACD) and you want to make sure the lower A is connected to A8 and the upper A is connected to A4.
  6. Connect the A-D inputs of the lower counter to B8-B5 and the upper counter to B4-B1. Again, the inputs are in a weird order and on both sides of the chip so pay special attention.
  7. Connect the B1-B8 outputs of the 74LS245 transceiver to the bus.
  8. On the 74LS245 transceiver, connect DIR to power (high) and connect OE to a new active low control line called SO on your 74LS138 decoder.
  9. Add 8 LEDs and resistors to the lower part of the 74LS245 transceiver (A1-A8) so you can see what's going on with the stack pointer.
Enabling Increment & Decrement
We've now connected everything but the Count Up and Count Down inputs. The way the 74LS193 works is that if nothing is counting, both inputs are high. If you want to increment, you keep Count Down high and pulse Count Up. To decrement, you do the opposite. We'll use a 74LS00 NAND gate for this:
  1. Take the clock from the 74LS08 AND gate and make it an input into two different NAND gates on the 74LS00.
  2. Take the output from one NAND gate and wire it to the Count Up input on the lower 74LS193 counter. Take the other output and wire it to the Count Down input.
  3. Wire up a new active high control line called SP from your ROM to the NAND gate going into Count Up.
  4. Wire up a new active high control line called SM from your ROM to the NAND gate going into Count Down.
At this point, everything should be working. Your counter should be able to reset, input a value, output a value, and increment/decrement. But the issue is it'll be writing to $0000 to $00FF in the RAM! Let's fix that.
Accessing Higher Memory Addresses
We need the stack to be in a different place in memory than our regular program. The problem is, we only have an 8-bit bus, so how do we tell the RAM we want a higher address? We'll use a special control line to do this:
  1. Wire up an active high line called SA from the 28C16 ROM to A8 on the Cypress CY7C199 RAM.
  2. Add an LED and resistor so you can see when the stack is active.
That's it! Now, whenever we need the stack we can use a combination of the control line and stack pointer to access $0100 to $01FF.
Updating the Instruction Set
All that's left now is to create some instructions that utilize the stack. We'll need to settle some conventions before we begin:
If you want to add a little personal flair to your design, you can change the convention fairly easily. Let's implement push and pop (source code):
  1. Define all your new control lines, such as #define SI 0x0700 and #define SO 0x0005.
  2. Create two new instructions: PSH (1011) and POP (1100).
  3. PSH starts the same as any other for the first two steps: MI|CO and RO|II|CE. The next step is to put the contents of the stack pointer into the address register via MI|SO|SA. Recall that SA is the special control line that tells the memory to access the $01XX bank rather than $00XX.
  4. We then take the contents of AO and write it into the RAM. We can also increment the stack pointer at this stage. All of this is done via: AO|RI|SP|SA, followed by TR.
  5. POP is pretty similar. Start off with MI|CO and RO|II|CE. We then need to take a cycle and decrement the stack pointer with SM. Like with PSH, we then set the address register with MI|SO|SA.
  6. We now just need to output the RAM into our A register with RO|AI|SA and then end the instruction with TR.
  7. Updating the assembler is easy since neither instruction has operands. For example, push is just psh -> 0x0B.
And that's it! Write some programs that take advantage of your new 256 byte stack to make sure everything works as expected.

Step 4: Add Subroutine Instructions (Image)

The last step to complete our stack is to add subroutine instructions. This allows us to write complex programs and paves the way for things like interrupt handling.
Subroutines are like a blend of push/pop instructions and a jump. Basically, when you want to call a subroutine, you save your spot in the program by pushing the program counter onto the stack, then jumping to the subroutine's location in memory. When you're done with the subroutine, you simply pop the program counter value from the stack and jump back into it.
We'll follow 6502 conventions and only save and restore the program counter for subroutines. Other CPUs may choose to save more state, but it's generally left up to the programmer to ensure they're not wiping out states in their subroutines (e.g., push the A register at the start of your subroutine if you're messing with it and restore it before you leave).
Adding an Extra Opcode Line
I've started running low on opcodes at this point. Luckily, we still have two free address lines we can use. To enable 5-bit opcodes, simply wire up the 4Q output of your upper 74LS173 register to A7 of your 28C16 ROM (this assumes your opcodes are at A3-A6).
Updating the ROM Writer
At this point, you simply need to update the Arduino writer to support 32 instructions vs. the current 16. So, for example, UCODE_TEMPLATE[16][8] becomes UCODE_TEMPLATE[32][8] and you fill in the 16 new array elements with nop. The problem is that the Arduino only has so much memory and with the way Ben's code is written to support conditional jumps, it starts to get tight.
I bet the code can be re-written to handle this, but I had a TL866II Plus EEPROM programmer handy from the 6502 build and I felt it would be easier to start using that instead. Converting to a regular C program is really simple (source code):
  1. Copy all the #define, global const arrays (don't forget to expand them from 16 to 32), and void initUCode(). Add #include and #include to the top.
  2. In your traditional int main (void) C function, after initializing with initUCode(), make two arrays: char ucode_upper[2048] and char ucode_lower[2048].
  3. Take your existing loop code that loops through all addresses: for (int address = 0; address < 2048; address++).
  4. Modify instruction to be 5-bit with int instruction = (address & 0b00011111000) >> 3;.
  5. When writing, just write to the arrays like so: ucode_lower[address] = ucode[flags][instruction][step]; and ucode_upper[address] = ucode[flags][instruction][step] >> 8;.
  6. Open a new file with FILE *f = fopen("rom_upper.hex", "wb");, write to it with fwrite(ucode_upper, sizeof(char), sizeof(ucode_upper), f); and close it with fclose(f);. Repeat this with the lower ROM too.
  7. Compile your code using gcc (you can use any C compiler), like so: gcc -Wall makerom.c -o makerom.
Running your program will spit out two binary files with the full contents of each ROM. Writing the file via the TL866II Plus requires minipro and the following command: minipro -p CAT28C16A -w rom_upper.hex.
Adding Subroutine Instructions
At this point, I cleaned up my instruction set layout a bit. I made psh and pop 1000 and 1001, respectively. I then created two new instructions: jsr and rts. These allow us to jump to a subroutine and returns from a subroutine. They're relatively simple:
  1. For jsr, the first three steps are the same as psh: MI|CO, RO|II|CE, MI|SO|SA.
  2. On the next step, instead of AO we use CO to save the program counter to the stack: CO|RI|SP|SA.
  3. We then essentially read the 2nd byte to do a jump and terminate: MI|CO, RO|J.
  4. For rts, the first four steps are the same as pop: MI|CO, RO|II|CE, SM, MI|SO|SA.
  5. On the next step, instead of AI we use J to load the program counter with the contents in stack: RO|J|SA.
  6. We're not done! If we just left this as-is, we'd jump to the 2nd byte of jsr which is not an opcode, but a memory address. All hell would break loose! We need to add a CE step to increment the program counter and then terminate.
Once you update the ROM, you should have fully functioning subroutines with 5-bit opcodes. One great way to test them is to create a recursive program to calculate something--just don't go too deep or you'll end up with a stack overflow!

Conclusion

And that's it! Another successful upgrade of your 8-bit CPU. You now have a very capable machine and toolchain. At this point I would have a bunch of fun with the software aspects. In terms of hardware, there's a number of ways to go from here:
  1. Interrupts. Interrupts are just special subroutines triggered by an external line. You can make one similar to how Ben did conditional jumps. The only added complexity is the need to load/save the flags register since an interrupt can happen at any time and you don't want to destroy the state. Given this would take more than 8 steps, you'd also need to add another line for the step counter (see below).
  2. ROM expansion. At this point, address lines on the ROM are getting tight which limits any expansion possibilities. With the new approach to ROM programming, it's trivial to switch out the 28C16 for the 28C256 that Ben uses in the 6502. These give you 4 additional address lines for flags/interrupts, opcodes, and steps.
  3. LCD output. At this point, adding a 16x2 character LCD like Ben uses in the 6502 is very possible.
  4. Segment/bank register. It's essentially a 2nd memory address register that lets you access 256-byte segments/banks of RAM using bank switching. This lets you take full advantage of the 32K of RAM in the Cypress chip.
  5. Fast increment instructions. Add these to registers by replacing 74LS173s with 74LS193s, allowing you to more quickly increment without going through the ALU. This is used to speed up loops and array operations.
submitted by MironV to beneater [link] [comments]

First Contact - Part Seven / Realization of Second Contact

[first] [prev] [next]
Many great cycles had passed without a single contact within the Great Emptiness.
Many of the members of the Unified Science Council began to believe that perhaps it was some kind of lingering energies left over from the Precursor War that had created mass hallucinations, or perhaps it was just isolated incidents with no meaning.
Seventeen Great Cycles and not a single clue that supported the existence of the Solarians, the Clone Directorate, sentient AI's, or any of the other strangeness discovered over that Great Cycle.
Even the Unified Executor Council had been forced to agree that the Solarians had simply, well, vanished.
The Unified High Council had no choice but to allow exploration of the Great Emptiness and so passed legislation to repeal the prohibition against exploration of that region of space.
That is how Monnat Banaltee of the HiKruth found himself in charge of a crew of a dozen of the Deep Space Explorer's Guild and in possession of one of the most advanced ships the Unified Technology Council would permit to be built.
The ship, named To Wrest Answers from the Darkness, had the best jumpspace engines, the most advanced computers with the most powerful computation and analysis lobes, laboratories and testing capabilities more advanced that any other ship, with sensors more sensitive than any other, communications capable of hearing the slightest whisper. Additionally, the ship's omnitranslator had been loaded with the TerraSol lexicons learned so far.
That was an entire Great Cycle ago.
Which was why Monnat, who refused the title of Captain and preferred Most Learned, was almost sick from boredom despite his race being legendary for patience. Even the upcoming arrival in a new solar system, deeper than anyone had gone so far into the Great Emptiness, failed to alleviate his boredom.
How could it? The last thirty systems they'd scanned had been the same: deeper than anyone had explored.
And empty except for a hundred million years of isolated evolution, largely resulting in a few plants or maybe even some non-sapient life more evolved than a cluster of cells.
Monnat was willing to bet his next three research grants that the next one would be the same.
"Preparing to drop," Aastruk stated. A master of astrogation and navigation, who had led whole fleets through jumpspace with his skill during his many years as part of the Unified Military Fleet, Aastruk was capable of making such sublime jump transitions that even the most sensitive of the scientists suffered little more than a light spell of dizziness.
At the end of the countdown there was a slight queasiness and that was all, allowing Monnat to tap his vestigal claws together and stare at Billik, a sensor's technician of extreme skill.
After nearly an entire cycle Monnat was beginning to wonder if Billik had decided not to do his job out of sheer boredom.
"Scan Master Billik?" Monnat asked.
"A moment, please, Most Learned One," Billik said. The scan tech looked over at Z'Mak, the Chief of Maintenance. "Oh Attentive One, Lord and Master of the Mechanical, can you perform a diagnostic upon my lowly instrumentation?"
Monnat sighed internally. Sometimes he wondered if all the insistence on titles and honorifics made it so things took longer than necessary. A heretical thought, he knew, but one had had asked himself many times over his long life.
Z'Mak, who was a stickler for protocol, nodded, the ruffle around his neck and down his spine flushing in pleasure. He examined his displays, tapped in some commands, then leaned back.
"Your instrumentation and displays are all functioning at over 90% efficiency, most attentive and inquisitive scanning technician," Z'Mak said.
At least Billik did not take offense at the obvious omission of honorifics, as he had during the first long cycles of the voyage, as Z'Mak was of the belief that those who joined the Unified Military Council or the Fleet were somehow less than those who devoted their lives to other pursuits.
"Then it appears, at long last, we have found a system with unknown xenosapients," Billik stated. "There are several settlements on the surface, four orbiting stations, solar collectors, and power readings everywhere."
"Launch a probe," Monnat said. "I will be waiting in my chambers. Announce to me when the probe begins to relay data."
Billik nodded as Monnat stood up on all four legs and moved toward his personal chambers.
-------------------
"Most Learned One," E'kotat's voice interrupted Monnat's viewing of a lecture on how a stable reaction within the translation chamber of a jump-drive was only established one way, despite crackpot claims of other possibilities.
"Yes, Second Leader?" Monnat sighed. He doubted that it was going to actually be anything. There had been nearly a dozen false alarms in the first few cycles of his mission. Every time it had turned out to be just a lost colony.
"You should come to the bridge immediately," E'kotat said. "Make all due haste."
Monnat frowned. E'kotat was a Drimarian, cold blooded quasi-mammal who's race's physiology was almost incapable of excitement. For him to urge haste was unusual.
And noteworthy.
When he entered the bridge, Monnat noted that Security Officer Lukamit, a computer code researcher who held a position mostly ceremonial, was busy over his terminals, all three of his lab assistants working with him.
"What is the emergency? Did something happen to the probe?" Monnat sighed, settling into his crash couch.
"We lost contact with it, Most Learned One," Billik stated. "It was intercepted by an energy pulse that shut it down. Soon afterwards, we were..."
"I will inform the Most Learned," Z'Mak snapped. He looked at Monnat. "It was then that we received communication signals. It attempted to open a communications channel but at the same time attempted to penetrate our computer network. Whoever the signal is from, they are most insistent that they be allowed access to our computer systems."
Lukamit interrupted, ignoring Z'Mak's flutter of his crest. "We are fortunate that they only use a binary type logic and only binary signalling. This allows me to use the lobes in parallel to more effect than they can. However, they did access the omnitranslator's lexicon and have been attempting to transfer it to their systems."
Monnat thought a moment. "Allow it."
"But standard is to exchange lexicons," Z'Mak protested.
"Do as I command as Most Learned One," Monnat told Z'Mak, fixing him with a stare that used all four eyes.
Z'Mak backed down.
"Lexicon is transferred. Wait, they've stopped trying to access our systems," Lukamit said. "They've purged their own code and completely withdrawn."
"We have an incoming signal," Juketet stated, listening closely. "Audio and visual, although only across a limited base three-primary color scale. They are not permitting any reply. Transmission only. It's quite rude."
Monnat sighed, fully expecting it to be another lost colony. Probably fallen back to aggression and superstition.
Instead the figure that appeared on the screen was unlike any he'd ever seen. Tall, graceful appearing for a biped, mammalian, with jewels adorning them, dressed in comfortable and gossamer appearing cloth, long golden hair and pointed ears. The female, and it had to be a female as it had mammalian milk ducts that were prominent, was surrounded by scantily clad bipeds that were shorter but had the same lithe build and pointed ears.
For some reason she gave off the appearance of being superior to everyone present. As if something more than nature, because nature could never produce such a perfect specimen, had crafted her to be perfection embodied.
It was a strange feeling for Monnat.
When she spoke, it was a strange language, linguistically designed to flow together and sound like music even mathematically.
Monnat noticed that Z'Mak seemed offended by the being.
The translation showed below, at the bottom of the screen.
"Welcome to the Magic Realms of Meratarrian. I am Queen Radosalvov the Graceful, you may call me Queen, Your Highness, or Radiant Divine One."
Z'Mak almost seemed to choke.
"According to Confederate Law, attempting to pirate views via recording probes without a license as well as permission from Galactic Studios Incorporated and Electronic Artistic Studios is a grave violation of our legal rights."
That caught Lukamit's attention.
"As your language is unknown to me I will assume that you were not meant to intrude upon this realm and I have decided to extend elven hospitality to you."
Monnat kept his expression from changing. Another race. Bipedal, warm blooded, mammalian, forward facing eyes. Obvious Solarian.
"I will allow you four local hours upon the surface as a freeware demonstration for one of your crew. I formally invite a sentient of your choosing in to my realm and invite your ship to stay within communication range of this planet."
She gave a gesture that used up the least amount of effort but still looked imperious, as if she was the most important being in the entire universe and the crew of the Wrest Answers from the Darkness should considered them blessed just to be allowed to view her.
"I will give you one of your time units to decide who shall enter the Magic Realms of Meratarrian."
The image vanished.
"They've cut transmission," Juketet stated unnecessarily. "Wait, they're transmitting a document. It looks like a legal document of some kind."
Monnat perked up. "Send it my ready room and have the ship computer go over it. Let us see what they are offering."
Juketet nodded.
------------------
Halfway through the time limit Monnat realized that even with the computer's help deciphering the document, which was some kind of terms of service, would be impossible. It was, quite possibly, the largest legal document he had ever seen. The ships operating system took up less storage and used less data than the document itself. Just viewing the document gave the issuer of the document legal rights over all kinds of things.
It repeated over and over that the issuers of the document, one Electronic Artistic Studios and one Galactic Studios Incorporated, could not be held liable for any damage to anyone using their services, to include death, dismemberment, disintegration, damage to neural or emotional networks, physical or metaphysical discomfort, damage, or alteration.
It went on and on and on.
But Monnat had been tasked with exploration, and he'd seen that Galactic Studios Incorporated and Electronic Artistic Studios operated under Terran Confederacy law and were based on TerraSol, which meant, despite appearances, the "elven queen" was a Solarian.
Which made no sense.
How many species rose to prominence in the system?
Monnat needed information, but most of all, he needed a volunteer.
And for that, he called Aastruk into his ready room to see if the saurian would volunteer to be part of the "free demonstration" that the "Queen" was offering.
To Monnat's surprise, Aastruk agreed immediately.
Monnat figured it was out of boredom.
-------------------
The shuttle that gathered Aastruk was flamboyant, lavishly decorated with rare elements to enhance its appearance and obviously built to appeal to anyone's eyes. Even mathematically it was almost perfect. Aastruk boarded wearing a vacuum suit and carrying a transponder.
The Queen had agreed to that much of a safety measure, even if she refused to allow recording devices.
Monnat settled down, as the shuttle left, and waited. Four local hours was less than a dozen cycles.
----------------
When Aastruk returned he stated one simple sentence: "We must leave now."
Monnat respected Aastruk's time with the Unified Military Fleet and ordered that the ship move to jumpspace immediately. Once they were safe in jumpspace he called Aastruk into his quarters and urged the reptilian navigator to speak.
"When I first got there, I was given many options. Enhanced virtual reality, real-skin which apparently involves me actually going down to the planet, skin-sheathe which is allowing me to mentally control a cloned version of myself from the station, or something called 'hitch-hiker' mode which is allowing me to see through someone else's eyes," Aastruk said, rubbing his snout wearily.
"What did you choose?" Monnat asked.
"Hitchhiker is the only option available for the free demonstration version," Aastruk said. He shuddered. "It allowed me to not only see and hear what was going on, it allowed me to taste, smell, and feel it. Not only that, I knew I could, well, share thoughts with my host."
Monnat made an annotation. "Did you?"
Aastruk nodded. "She is from someplace called Alpha Centauri, one of the earliest Terran Confederacy's colonies. That's aside, however, and not the important part."
Looking up Monnat frowned. "What is important than that?"
"She was, to use her words, reborn as something called a 'dwarf' and took the profession of blacksmith," Aastruk said. "Working in iron, steel, some exotic metals I've never heard of. She makes armor, weapons, and other metal objects as well as wood carving..."
"Who does she make these weapons for?" Mannot asked.
"Soldiers who guard the town and being who wish to enter into the wilderness to seek out adventure even at the risk of encountering dangerous wildlife that will seek to slay them if they do not slay the wild-life first. She makes weapons and armor for these people and then, and I use her words: magics the excrement out of them which is why...."
"Magic?" Monnat scoffed, interrupting. "A people that advanced believing in magic."
Aastruk nodded. "When she explained magic to me was when I realized we must leave at once."
"What was so frightening about it?" Monnat asked, wondering if Aastruk would need therapy.
"Nanotechnology is something we use. For medical, research, manufacturing, computation," Aastruk said. Monnat nodded as Aastruk continued. "They have devised a type of nanite that uses broadcast power to sustain itself and floats through the very air. It permeates he atmosphere, is in everything they drink, everything they eat, even in the objects."
"Risky. What if it went out of control? Entire planets have been lost to such ill advised experimentation," Monnat asked.
Aastruk shook his head. "They aren't worried about it. You see, they use the nanites to manifest certain reactions. From creating a monomolecular sword edge and infusing the blade with nanotech like my host did to calling up fire out of thin air, this so called magic is nanites."
Monnat cringed slightly. "And anyone can use it with a simple interface?"
Aastruk shook his head again. "No. It requires will, being able to chant out loud the command strings, and being able to withstand pain. The more energy intensive the task the nanites carry out, the more pain the nanites inflict."
"Madness," Monnat whispered. "And they willingly subject themselves to this to use this so called magic? I understand, if they are born there and this is the path to power, but still, to willingly subject one's self to pain."
Aastruk shook his head. "No, Most Learned One, it is worse than that."
"How is it worse?" Monnat asked. "Please, Aastruk, will you define worse?"
"While some beings who live on that planet were born there, Most Learned One," Aastruk took a deep breath. "The majority pay for the privilege of living their lives there. Some even pay to be other species, such as my host, who had her entire body rebuilt from 'Pure Strain Human' to 'dwarf' in order to live out her fantasies."
Aastruk fixed Monnat with his gaze. "It's a planet sized, fully interactive, nanite assisted, amusement park that they pay to experience, sometimes for their entire adult lifespan."
Monnat goggled at Aastruk. The thought of having one's body changed to live out a fantasy was grotesque, but the idea that it was some kind of amusement park horrified him.
"You were correct in having us leave at once. Was there anything else that made you so urgent to leave?" Mannot asked.
Aastruk nodded. "At the end of my 'free trial' several of the 'High Elves' offered to sponsor me if I agreed to fight in their name for their glory," He said, shuddering.
Mannot nodded. "A wise idea, returning. I do not blame you for wanting to return when that undoubtedly caused such fear, to be dumped in such a place where advanced technology is used to live out a fantasy of primitivism."
Shivering, Aastruk shook his head. "No, Most Learned One, I did not want to return out of fear, I returned because I wanted to stay."
Aastruk hung his head and whispered softly. "Glory and honor to my house, with eggs and burrows the envy of all, by might or trickery my house, my burrow, my clutch ascendent."
Mannot stared in horror at Aastruk repeating such an ancient mantra of his species and decided that the expedition was over.
----------------
The Unified Exploration Council examined the records as well as the statements of Fleet Admiral (retired) Aastruk eshThsashal and ordered another exploration expedition created.
The Unified Science Council determined that the Solarians, perhaps the entire Terran Confederacy, was using technologies in ways that were prohibited as well as dangerous, not only to the Terran Confederacy itself, but to all those around it.
The Unified Executor Council decided that armed Executors would accompany all other research and exploration vessels to prevent any desertions to such a dangerous civilization.
Aastruk eshThsashal converted all of his possessions and wealth to simple gold bars and vanished.
------------------
I, AASTRUK eshTHSASHAL, agree to abide by the above terms and services as set out by Galactic Studios Incorporated and Electronic Artistic Studios, as well as the Meratarrian code of conduct.
------------------
TO: CONFEDERATE INTELLIGENCE
FROM: QUEEN RADOSALVOV THE GRACEFUL, OVERSEER OF MERATARRIAN (All Rights Reserved)
Had visitors not long ago, like I told. However, it appears that one of their number liked their trial time so much they've returned to my divine embrace (LIFETIME MEMBERSHIP PURCHASED). Attached is crude documents and illusions of their statements about the mundane and boring life they left behind, the poor dear. I'm sending these to you out of consideration.
He is a lovely subject (ITEM SHOP PURCHASE: PLATINUM STARTER PACK), who has been yearning all his life for the adventure (DLC PURCHASED) only I, in my infinite wisdom and beauty, can provide to him (ITEM SHOP PURCHASE: USER GENERATED FRIENDS AND FAMILY PLATINUM PACK). I have hereby granted him asylum from such a dull and dreary place, and made him a citizen (DLC MEGAPACK PURCHASED) of Meratarrian (EXPANSION PURCHASED) with permission to found his own house (DLC PURCHASED) as well as quest for his true love (DLC PURCHASED) as well as create offspring (EXPANSION PURCHASED). I have high hopes for my new subject (ITEM SHOP PURCHASE: KOBOLD HERO PACK) and know that he will go far (ITEM SHOP PURCHASE: DRAGON BLOODED) in my realm.
Enjoy your files.
Love and kisses.
Her Eternal Elven Grace, Divine Light of the Aether, Lady of Magic and Power, Queen Radosalvov.
--------NOTHING FOLLOWS-----------
CONFEDERATE INTELLIGENCE MEMO
CC: Artificial Biological States; Digital Artificial Intelligence Infonet Worlds; TERRASOL.GOV; Cyborg Cooperative; Clone Directorate; Mantid Free Worlds; Traena'ad Hive Worlds
Xenosapient government identified. Native species identified. (See attachments)
Military potential is initially classified as low, to be revisited upon any new information which will be shared to all Confederacy governments as per treaties.
Chance for incursion into Confederate Space is high.
Place all rimward stations, colonies, planetary governments, and military forces on stage two alert. Do not fire unless unable to withdraw or casualties are incurred. Abide by Rules of Engagement for inferior forces unaware of Confederate military and industrial power.
-------NOTHING FOLLOWS-----------
TRAENA'AD HIVE INTELLIGENCE
RE: Your Last
Let's hope we do better with them than when the two of us first met.
--------NOTHING FOLLOWS--------
submitted by Ralts_Bloodthorne to HFY [link] [comments]

Cryptosoft Review 2020-Is it a Scam?

Cryptosoft Review 2020-Is it a Scam?

Most f the reviews we tend to have come back across reveal that the Cryptp soft platform is easy to
Their client service is very efficient. We did a live check and confirmed that they respond at intervals a moment. Moreover, they are available 24/7.
The Cryptp soft app is secure. They need all the mandatory measures in place to make sure data privacy.
The Cryptp soft System is considered by several among the most effective robots within the market nowadays. We have a tendency to realize this robot to perform virtually the same with Bitcoin Rush, another top bitcoin robot. Read the review of Bitcoin Rush for more data?
Cryptp soft registration method is straightforward, easy, and secure. You only want but 10 minutes to form an account and begin trading. Cryptp soft is a absolutely auto bot and is so accessible to everyone.

https://preview.redd.it/giu6kclgfnn51.jpg?width=1280&format=pjpg&auto=webp&s=f605d84ba2174f831ca825dbaffddf061b3a55b5
You do not want to perceive trading lingo to use Immediate Edge. The following steps can get you started with this robot.
STEP ONE: Fill the Signup type

Visit the Cryptp soft home page and register your name, phone number, and email in the provided kind. You will be asked to verify your phone variety via a text code and email through a link. CryptoVibes will ascertain that the Cryptp soft registration process is secure.

Their web site is SSL secured to confirm that hackers cannot steal personal information submitted through it. Cryptp soft cyber safety policy states that they're GDPR adherent. This suggests that they handle your knowledge with strict privacy.
STEP TWO: Get matched with a broker

The Cryptp soft Software then matches you with one in every of their partner brokers. The role of the broker is to receive deposits and facilitate transactions. We have a tendency to have determined that Cryptp soft only partners with regulated brokers.

With a regulated broker, they guarantee that your cash is safe. Reputable regulators such as the FCA, FSB, ASIC, and CySEC need brokers to segregate deposits and submit periodic reports on deposit usage.
You wold like a deposit of a minimum of $250 to trade with Immediate Edge. Do not confuse this quantity with the value of the robot. Cryptp soft does not need any license fee. The house owners of this robot build money by charging a small commission on the profits generated through the app
Deposits with Cryptp soft should be created through Wire Transfer, Visa, and MasterCard. It takes a few seconds for a deposit to reflect in an exceedingly trader’s account. Cryptp soft does not charge any deposit fees.
The Cryptp soft does provide a demo account to help traders familiarize themselves with its web-trader. CryptoVibes recommends that you are doing demo trading before going to live to trade. Please note that the demo is for demonstrative purposes solely.
The results you receive on the platform are primarily based on historical information and could therefore not mirror what you'll get in live trading.
The Cryptp soft live trader comes with features to help you outline the amount of risk you are willing to require per trade. You wish to go through the demo account to familiarize with these features. As mentioned severally in this review, you do not want specialized skills to use this robot.
Live trading with Cryptp soft involves determining the quantity of capital you plan to risk per trade and clicking the live button. Scan our review of Bitcoin Trader for one more straightforward to use the robot.
*Remember all trading risks and you shouldn’t risk more then you'll be able to afford to lose.
How to get the most out of Cryptp soft App
We have identified the following tips as paramount in guaranteeing that you make the most of Immediate Edge.
Begin with a deposit of $250 – Given the level of risk involved in trading with Immediate Edge, you should start with a tiny investment.
Follow crypto market news – You need to determine the type of reports that drives volatility high and capitalize on them. Cryptp soft claims to form the foremost profits throughout high market volatility.
Trade for eight hours per day – In keeping with Immediate Edge, trading for at least eight hours per day can help maximize profits. Cryptp soft is entirely auto, and hence you'll be able to leave the robot running as you continue together with your daily errands. You are doing not want more than twenty minutes per day to observe your account.
Close trading sessions at the tip of the day – Leaving open positions overnight is doubtless to translate to losses since the markets can change considerably overnight. It is better to shut sessions even if in the negative and start trading again the subsequent day. With a correct risk management strategy, there is no would like to fret concerning periodic losses.
Following our review we tend to realize Cryptp soft to be legit. But, traders ought to take additional caution, provided that this bot comes at a degree of risk. Whereas the app claims it's potential to form profits of up to 50percent per day, you'll be able to additionally lose the complete deposit inside seconds. This is often not sudden for a high-frequency trading robot.
We recommend that you just apply the required risk management measures. As a rule of thumb don't risk more than 10percent of your trading capital per trade. Also, never trade with an amount you cannot afford to lose. It is prudent to start small and add cash as you get conversant with the various features on the platform.
Recently, a brand new trading software was added to the bitcoin investment trade. This software is termed Cryptp soft and it is allegedly created by a corporation or organization called the International Council for Bitcoin.
There is additionally a letter out there on their web site that has been signed by someone named David. This person claims to own earned over 1,000,000 as a results of investing in bitcoins. What’s very shocking concerning this letter is that David claims to have earned that huge quantity in just one trade. If we have a tendency to place it in simple words, David became a millionaire overnight.
We tend to highly doubt that a trading system that has been launched recently will have such potential. To verify the main points of this software and to determine its legitimacy, we have a tendency to conducted our own research and investigation.
Cryptp soft is a bitcoin trading software that’s meant to assist newbie traders get involved in Cryptocurrency trading with less risk than ancient investment opportunities. Cryptp soft software was created by The International Council For Bitcoin who is PRO Bitcoin trader Group behind the Cryptp soft software. Notice out all concerning Cryptp soft software by The International Council For Bitcoin.
Cryptp soft Software may be a nice development by a famous, well established and experienced bitcoin trader Investors with a viewpoint to enable traders to perform different tasks with ease and convenience.

https://preview.redd.it/uuh85yghfnn51.png?width=1238&format=png&auto=webp&s=d0558e6e123114b6624d5a724b3b9b5983e717e1
Cryptp soft Software is essentially a Binary choices trading software that is designed to assist traders win and predict the Binary options trend of their respective choices. Cryptp soft APP works as a code to urge financial success, shows traders how they'll make money on-line, helps them to find different ways in which to induce huge returns on their investment. The Cryptp soft Trading Software additionally provides analyses of Market conditions so that traders will recognize what ought to be their next step. Cryptp soft System gives secret cryptocurrency ways that ultimately help binary traders to create thousands of greenbacks solely for some bucks.
Several individuals can say that Cryptocurrency Trading may be a risky business and tend to remain faraway from it. But from my expertise, high volatility means HIGH RETURN OF INVESTMENT in Crypto Market. But this can be where the Cryptp soft comes into play, the mathematical algorithm used by Cryptp soft Software takes the guesswork out choosing a winning profitable trade. You don’t must be an expert. Like I said earlier, I actually have personally tested the Cryptp soft and found the success rate is about ninety sevenpercent. I don’t apprehend concerning you, but a ninety seven% probability of earning a profitable trade is TERRIBLY GOOD! I’ve never come across something like this trading software before. Keep reading, below are my Cryptp soft results for the past week or so…
Watch over the Shoulder of a Professional Each Day and you'll be able to learn as you trade.
Averaging 97% Winning Weeks With Cryptp soft which suggests that more potential profits for you
Cryptp soft Software Are Fully Transparent
No previous experience with binary choices trading required
Web-based mostly, no need for downloads, additionally works on phones, tablets
You'll be able to Even Watch Cryptp soft Signals From Your Phone (iPhone Users — Photon Browser)
If you are ready to begin making cash online with an on the spot edge, there has never been a better chance than currently. If you enjoy surfing the web for countless hours trying for the next Trading Method Secrets, never being able to urge centered, being overloaded with conflicting information, and not creating cash on-line, you ought to probably leave this page right now and get back to that Cryptp soft System strategy
Cryptp soft bot could be a new cryptocurrency trading invention that comes with options that create this software stand out among others. It is conjointly an automatic trading platform that uses a smart program algorithm to detect favorable trading opportunities. It acts on its own or waits for a prompt command from the user depending on the software’s settings. But what makes this software unique and a favorite to individuals is what we have a tendency to shall unveil in this review.
There have been lots of unverified claims of how totally different cryptocurrency software have helped several people to make massive profits leading to Scam individuals. However, it's pertinent for cryptocurrency traders to verify if a particular trading software may be a scam or legit, which is also ?
After subjecting the features of the Cryptp soft bot software to a series of tests, the software isn't a scam however legit. The Cryptp soft bot is believed to have successful rate of 85%, that is a lot of than the 80percent benchmark for average software. The Cryptp soft bot has helped cryptocurrency traders to make sensible profits, which has been documented as testimonies on the software’s website.
Trading on the platform is straightforward and might not require experience. We had to verify the simplicity of the software, and we tend to discovered that the software is easy to navigate. The demo trading feature of the software makes it potential for brand new users to hold out trading activities in an exceedingly simulated atmosphere while not having to risk their investment. This any gives credence to the legitimacy of the software because it ensures that new users get accustomed to the features of the software before continuing to measure to trade
As earlier stated, the Cryptp soft bot could be a high-tech program software that comes with exceptional options that makes it among the simplest cryptocurrency trading software in the blockchain market. The outstanding features of the Cryptp soft bot embody the subsequent:
https://www.cryptoerapro.com/cryptosoft/

http://www.cryptoerapro.com/

https://twitter.com/cryptoerapro

https://www.instagram.com/cryptoerapro/

https://www.pinterest.co.uk/cryptoerapro/
submitted by cryptoerapro to u/cryptoerapro [link] [comments]

First Contact - Part Twenty-Three

[first] [prev] [next]
The Devastator class Precursor machine was the size of a large metropolis. Full of ground combat machines, air superiority machines, mining and reclamation machines that could move under their own power and were festooned with a thousand weapons. It was over a hundred million years old and had exterminated life on planets with its massive guns, with biowarfare, with chemical warfare, and with good old nuclear fire. It had wiped away planet after planet of the enemies cattle, the hated enemy's food sources, before finally following orders of the greater machines and going into sleep mode on a dead world.
Now the call had sounded out. Cattle had run amuck, even learning jumpspace technology. That meant the enemy had not been defeated, that his food source had multiplied into the trillions while the Devastator had slumbered, slowly sinking into the crust of the barren planet.
That was of no moment. Cattle could not fight back, that was why they were cattle. They knew nothing but safety and the security of numbers, willing to trade their own safety for the suffering of others. The cattle willingly marched into the pens if the pens promised safety.
The cattle were not the problem.
It was the feral intelligence that were the problem. Feral intelligence could fight. They knew nothing else. They cared for nothing else. A feral intelligence always destroyed itself once it could wield nuclear fire. The universe had proved it over and over even before the great machine had gone into slumber.
The call had sounded out, informing the machines that cattle had broken loose from the pens. The Devastator had computed that the problem would be solved quickly, with a minimum expenditure of resources, and had started to go back into slumber.
That was when the second call sounded. A feral intelligence had mastered FTL travel and had turned all of their unthinking violence against the Precursor war machines.
The Devastator considered the chances of the feral intelligence lasting long enough to withstand his brethren's assault, withstand purification and pacification.
It was mathematically insignificant. Not zero, but close enough that it required an application of resource driven computation to analyze it.
Feral intelligences always destroyed themselves.
The Devastator knew this. Had it encoded into its very bones. It did not feel the electronic version of caution as it moved into the planetary system, exiting faster than light travel. It screeched out its warcry as it exited into the system and brought up its scanners.
It felt the electronic version of anticipation as it detected orbital facilities around two planets that teemed with billions of cattle, as it tasted jumpspace wake trails, as it felt the presence of a small, insignificant amount of cattle space vessels arrayed to attempt to stand against it near the outer gas giant.
It was a waste of resources.
Cattle could not withstand machines.
It was as solid a fact as radioactive decay and as impossible to stop.
It roared and turned to accelerate toward the cattle ships waiting on the other side of the gas giant, letting them know the futility of their resistance and that nothing could stop it from destroying them any more than they could stop entropy.
It felt electronic satisfaction as nearly 10% of the cattle ships broke formation and fled for the planets.
The cattle ships lit their engines, trying to keep the gas giant between them and the great Precursor machine but the Devastator knew it would do no good. It would ensure they were caught mathematically opposite of it and begin launching subsidiary craft to destroy them and reclaim the resources of their wreckage.
The Devastator slowed as it approached the gas giant, ancient code pulsing impulses into the electronic brain at the mathematical certainty of destroying the cattle's defenses and thus weakening the hated enemy.
pssst... over here...
The transmission was in binary. The basic code, on a low band that the Devastator used to contact and exchange data with its peers. The signal origin was close, just behind it, in the gap between two point defense radars.
The Devastator tumbled as it slowed, searching with its senses to check that tiniest of gaps in its sensors. It could detect nothing out of the ordinary. The fact that the gas giant had a high level of hydrocarbon and pseudo-organic compounds was a high certainty with most gas giants of that size. The Devastator cast around, knowing the cattle had not sent that transmission.
psst... here...
This time the transmission was only a few hundred kilometers above the hull, right behind the main guns of battery-eight, between the massive cannons and the sensor array, in a gap in the coverage caused by space dust not yet cleared from the array. The Devastator ensured the cattle vessels were on the other side of the gas giant as it cast around again, looking for what could possibly be sending the message on that particular channel and rotating again to either force the transmitter to move away or hit the hull of massive Devastator.
...right here...
The Devastator felt the computer version of anxiety. A new factor had entered the computation. The voice, and the binary signal somehow had a voice, a whispering, tickling, hissing faint signal of binary on a wavelength just above the screaming particles of the foam between realspace and subspace. This time the voice had come from just below the Devastators thick hull, beneath the vessel, in a gap between the sensors in a place where its own orbital guns would not dazzle the sensors. The Devastator rolled, getting the upper sensors into place in a graceful sideways roll.
Nothing.
The Devastator was barely tracking the cattle. They were of no moment. Something was whispering on a bandwidth that was beyond organic abilities. Could it be a damaged ally, barely able to whisper for electronic assistance?
...I see you...
The Devastator heard the signal hiss to life, trickling out of empty space a few hundred kilometers away. It felt of a surge of self-defense protocol override everything else and it unleashed all of its gun at the empty space, suspecting that this possible enemy may be using some type of photo-passthrough adaptive camouflage.
Nothing.
The Devastator felt the self-preservation protocols wake up and fill some of its processors. That signal had originated from that point! Even a dust-speck would have been detected by its scanner arrays, nothing could have escaped the terrawatts of death it had unleashed.
...touch...
The Devastator felt a physical TOUCH on its housing, the decameters thick armor around the massive computer core that made up its brain. That was impossible! It was in the center of the ship, protected by layer after layer of armor, defensive mechanisms, sensors, but yet it had felt something touch the housing, press against it lightly, only a few tickles of the suggestion of pressure per square micrometer but a touch all the same.
There was a slight ripple in realspace only a few meters above the hull and the Devastator pushed itself away, firing every weapon it could bring to bear on the spot only a few atoms wide, all of its sensor questing, seeking, hunting in electronic desperation to find out what was transmitting, what was touching it!
...here...
The word was whispered from only a few meters away from the electronic "brain" of the Devastator, inside the protective housing, inside the field that would shut down biological neural function and even primitive artificial intelligences!
The Devestator felt self-protection and self-preservation programs never before accessed come online and flood into its RAM as the word was whispered at it from inside the final layer of protection.
Massive nCv cannons lowered, the housings screamed as the Devastator pushed them past the limit, to aim at its own hull. It opened fire, trying to claw into its own body in the electronic version of panic to get whatever was inside it out of it.
All of its sensors were directed into its own body. It no longer even bothered with tracking the cattle fleet. Even its astrogation and navigation programs, even the ones responsible to maintain orbit around the gas giant, were desperately racing through the circuitry, desperate to find whatever was whispering.
...over here...
The whisper was over it, on top of it, and carried sidecode of a mathematically impossible jumble of electrons arrayed in an impossible manner, with quarks whirling through electron valences, antimatter electrons in the nucleus, preons stretched to massive size taking up the place of neutrons, all with jumbling strangled mathematical codes that made no sense.
The Devastator's brain burned out the receptors to defend itself from such electronic madness.
And felt a touch upon one of the upper lobes of its quantum computer brain.
...over here...
The Devastator was throwing antivirus software out, slamming firewalls against each other, crushing ports into electronic ghosts, doing anything it could to keep out the voice. Inside the Main Computer Housing the last resort lasers began raking across anything that didn't match the original blueprints, burning away dust, odd quarks and electrons, destroying an upgraded maintenance robot that was desperately trying to detect what had touched its carapace.
From deep within the gas giant tentacles hundreds of miles long rose toward the Devastator, the ends slowly unrolling as massive graviton assisted 'suckers' on the inside of the tentacles deployed razored thorns of dark matter infused psuedo-bone.
The Devastator detected the tentacles just as they wrapped around it, the thick psuedo-protoplasmic tentacles that were thick with dark matter squeezing the Devastator's hull with impossible strength as meters thick muscles flexed with enough strength to crush the hull into itself and shatter armor over a kilometer thick.
Gibbering, raving, SCREAMING in something beyond electronic self-preservation programs would normally allow, the Devastator began to break apart, caught in the grips of the tentacles, being pulled into the gas giant.
...delicious delicious delicious...
The Devastator heard from inside its own mind as a beak nearly twenty kilometers long crushed its hull.
HELP ME, BROTHERS, PLEEEEEASE!
The beak closed and the Devastators brain flashed out of existence as the hull crushed around it.
The last thing it felt was something new. It threw data out with the cry for assistance to let its brethren know the last experience hashed data compile it had undergone. The data made no sense to the other Precursor war machines that heard the cry. A biological entity could have explained it.
Terror.
And despair.
A Desolation Class precursor war machine was assigned to discover what had caused the Devastator's intelligence collapse.
It dropped into the system and found no trace of its mechanical brethren.
Just some cattle species space craft hiding behind a gas giant, obviously intending ambushing it.
Feeling the electronic version of anticipation it moved into orbit around the gas giant, intending on forcing the cattle ships to move out of line of sight with their worlds if they wanted to stay on the opposite side of the gas giant from it. It updated its computations based on the fact that 10% of the cattle's ships had fled away from it.
It had already computed out the battle. It knew how the battle would go. While it could not detect any signs of its little brother it computed that it would simply destroy the cattle and then search. It powered up its guns and began to move it's metropolis sized bukk slowly to
...psst... over here...
---------------------
The stellar system was infested with a known species of cattle, obviously seeking to rise above themselves as the Jotun class Precursor vessel arrived in the system. It released its roar to let the cattle know not only why but who was destroying them to reclaim the resources they so foolishly squandered. It began unthawing ancient bioweapons and chemical weapons known to work upon that race, began reconfinguring its war machines to forms that had exterminated who planets of the cattle during the time that the Precursor war machine had been forged. The Jotun released over a hundred Devastator classes from its hull, computed the battle plan as they came to electronic life, then informed them of how the extermination and reclamation would progress.
They were barely into the system when a high energy signal appeared, rising from the most heavily infested planet and moving toward them. The Jotun ordered a diagnostic of its scanners when the first information came in.
It was apparently moving at .85C, but yet its progress toward the Jotun and its smaller brethren on the system map showed it moving at almost 22C. That made no sense. An object moving at .85C only approached at .85C, not at 22C.
By the time the diagnostic was done the object had gotten a third of the way toward the Jotun, crossing a quarter of the radius of the system.
The scanners reported that the energy signal, with the strength normally reserved for a quasar, was not a massive ship or an oncoming armada interlinked together, but was simply a single object the size of cattle.
Again the Jotun ordered a complete low level full diagnostic on all systems. Risky, but any object radiating that much power and moving at two different speeds required all systems were working at optimum efficiency.
It had finished just as the small object came to a stop. The Jotun focused scanning arrays on it, turning up the power to the point that it would boil away meters of armor.
The figure was a primate, half of it made up of robotics. It had some kind of sheet of material floating behind it, the movement suggesting some kind of current was effecting it and making it undulate. It was dressed in two primary colors, red and blue, had its lower legs pressed together with the toes pointing down and the upper limbs crossed over its chest, one biological the other mechanical.
"So, you're the new punk everyone's talking about," The figure stated over a wide bandwidth of wavelengths. Oddly enough, to the Jotun's sensors, sound waves travelled through vaccum almost instantly across a light second to its sensors.
The Jotun tried to compute how sound waves moved faster than light through a vacuum.
Instead of answering the Jotun and its brethren opened fire.
The figure arced through the beams as if light speed weapons were moving slow enough for it to just compute and swoop around in a resource wasting corkscrew. The Jotun realized it was racing for one of the Devastators, one clenched fist held in front of it.
The Jotun computed a 99.99999999999998 chance that the small primate would splatter against the hull of the Devastator and started to turn its attention to computing a missile firing resolution for missile bay 148 to destroy an orbital facility around the nearest planetoid.
The small figure punched straight through the Devastator, as if it was made of nebula gas instead of density collapsed armor, high tensile ceramics, and reinforced internal spaces. The Devastator's computer core shrieked with self-preservation code snippets as the figure exited the opposite side of the Devastator holding the Primary Computer Core CPU0 in its fist. It paused, looked at its fist, and shot beams of red energy from its eyes, destroying the computer core in a puff of atomic smoke.
The Jotun yanked its processing power back to the figure as it raked its gaze, still emitting beams of red energy that left ripples in jumpspace, across the side of another Devastator, tearing it open like it was made of fragile tissue, the red beams reducing the computer core to its component atoms with the briefest of touches.
Several computational nodes collapsed when trying to analyze the beams, suffering the fatal CANNOTDIVIDEBYZERO shriek of despair before imploding on themselves.
The Jotun stared in electronic shock, all his computational power trying to compute how the tiny half-mechanical primate could grab a hold on the front armor of one of the Devastators, and without any source to exert leverage against, physically move a city-sized spacecraft in an arc and throw it against another one.
According to scanners the "thrown" Devastator was only moving at 0.001C for inertia purposes yet crossed the hundreds of kilometers to the next Devastator in an amount of time that would require it to be moving at 6C.
CANNOTDIVIDEBYINFINITYDIVIDEDBYZERO
The Jotun cut loose with its weapons and goggled in electronic confusion as most of the beams and slugs were avoided, slapped aside, or ignored.
Until a nCv (near C velocity) slug the size of skyscraper hit it dead center of the chest, the impact point looking only the size of a soda can.
The Jotun's processors struggled to understand how something that size had only made an impact smaller than itself.
CANNOTSUBDIVIDETWINKIESBYCHEETOSBYZERO
The figure looked down at the tear in its suit, at the bruised biological flesh that had been exposed, then at the Jotun. It lifted a hand, extended the first finger next to the opposable thumb, and slowly waved it back and forth.
"That might have worked against a Galactic Class Klark, but it was pathetic against an Apokalypse level Injustice MCLXI Cyber-Clark," The figure said, the tone calm and confident. The meanings behind the words were gibberish to the Jotun, who devoted processor cycles to try to decode the meanings for any hint on how to defeat the creature before it.
The Jotun computed that retreat was the only option as the small primate figure set about destroying the last of the Devastators.
It began activating the engines when the primate suddenly turned in place.
"No you don't," It snapped.
Again, it sounded as if the Central Computer Core Housing had been set to atmosphere so that sound waves could be heard within it, yet a quick check showed the housing was still at almost perfect vacuum.
Sound waves cannot travel through space, a hundred diagnostic programs computed.
And promptly crashed.
Those red beams lanced out again and the Jotun braced in the microsecond it had.
It was like being brushed by the solar flare of a red giant concentrated into a piercing lance of nuclear fire. Armor exploded from energy transfer, slagged away from thermal transfer, or just ceased to exist as ravening atoms usually only found in the photosphere of a dying red sun attacked the atoms of the armor. The beam tore through mile after mile of internal structure, the figure still emitting the beam from its tiny eyes.
The Helljump engines exploded when the light touched them.
The Jotun listed, pouring debris and a cloud of atomized armor from the wound that completely bisected it.
"Done. Now let's see the face of the enemy," The figure said, slapping its hands together after it crashed/flew through the last Devastator. It reoriented on the Jotun and began to "slowly" drift toward the Jotun, moving at only 0.000003C according to some scanners but crossing the distance as if it was moving at 1.5C.
The figure flexed its primate hands and a slow smile spread across its face.
"I can't wait to rip away your housing and see you with my own eyes," the figure said, the sound waves again travelling inside the vacuum of the strategic housing.
The Jotun tried to react but the figure was suddenly pushing open armor with its two hands.
Self-preservation programs crashed trying to compute how to prevent impossibility itself from breaching critical spaces. Self-defense programs tried to compute how to defend against something that did nothing but radiate impossibility around it.
The Jotun knew what it had to do as the creature tore open the last of the hardened bulkheads protecting the Strategic Housing.
It detonated the antimatter reactor that powered the "brain" as the figure tore through the Strategic Housing and laid eyes upon the supercomputer core.
It had computed that not even the figure could withstand the direct assault of kiloton of pure antimatter point blank.
The explosion completely consumed the Jotun.
When the ravening energy disappated the red and blue figure was lying in blackness, surrounded by an expanding ring of debris and energy.
It stared at the stars and mouthed a single word.
"Ouch."
---------------------
CONFED INTELLIGENCE
TO: MANTID INTELLIGENCE
Our digitial brothers have computed a high chance that we're not looking at a handful of these Precursors, but rather an armada of them that had gone to sleep thinking everyone was dead. We concur and are buckling down for the long haul.
-----NOTHING FOLLOWS------
MANTID FREE WORLDS INTERNAL MEMO
If humankind ever wonders why it was put in this universe by some unknown creator then know that it was for this very moment.
submitted by Ralts_Bloodthorne to HFY [link] [comments]

CRTPi4-RCA v3.4FX - Composite TV-Out for your Pi4!

CRTPi Project Presents:

CRTPi4-RCA v3.4FX

A CRTPi image for running 240p via 3.5mm Composite on the Raspberry Pi4
Other Releases:
Changelog: v3.4FX for RCA (PAL Only) 5/18/2020
Changelog: v3.4FX for RCA (NTSC&&PAL) 5/17/2020
Changelog: v3.0F for RCA 5/11/2020
Changelog: v2.0F for RCA 4/1/2020
Changelog: v1.1FX 12/20/2019
Changelog: v1.0F Hotfix 10/31/2019
Changelog: v1.0F 10/29/2019
Changelog: v0.4 10/22/2019
Changelog: v0.3 10/2/2019
How does this even work!?
The amazing u/b0xspread has found a way to enforce modeswitching by watching the logs and processes, and continuing to enforce our desired mode long after the system wants to revert back. We're both expanding this scripting further to hopefully solve the same issues on the RGB and VGA forks -- but progress is slow due to the complex and varied nature of available resolution modes on those builds. But for now, let's just call this "black magic."
What Does That Look Like?
Here are some examples of games being played in beautiful 240p on CRT sets using the RCA Image!.
What is Different?
  • Retropie 4.6 (build 72132587 commit 05/07/20 Buster 10)
  • Retroarch 1.8.5
  • Full Apt-Upgrade for newest firmware and app dependancies (Recommended to repeat this function on your own Pi4)
  • 4GB (3872256 KB Uncompressed Image) (Compressed via WinRAR to 1043540KB)
  • SSH, Samba Share, and USB Rom Service enabled by default
  • Heavily modified Sakitoshi CRT-TVout script for switching between 480i and 240p
  • Further modified Sakitoshi script by u/b0xspread to allow video resolution switching on Pi4 Architecture
  • Optional overclock values in /boot/config.txt for Pi4 (disabled by default) [RECOMMENDED!]
  • NTSC @ 60hz 720/640x480 480i Resolution for Emulationstation & Kodi
  • PAL @ 50hz 720/640x576 576i Resolution for Emulationstation & Kodi
  • NTSC @ 60hz 640x480 Progressive (240 lines) for Retroarch
  • PAL @ 50hz 640x576 Progressive (288 lines) for Retroarch
  • Per-system custom refresh rates for Retroarch
  • Single-frame Run Ahead enabled for many 8-bit & 16-bit consoles and handhelds for Retroarch
  • Optional 480i mode for PSX and Arcade games
  • Preloaded with free 240p test suites for multiple consoles
  • Preloaded with additional stable (opt) Retroarch emulators
  • Preloaded with DOSBox and ScummVM
  • Preloaded with various 4:3 splashscreens from the RPiF download
  • Preloaded with 4:3 Ruckage's runcommand launching screens for supported systems
  • Custom 4:3 Arcade DOJ "Winners DO Use Drugs" splash screen.
  • Preloaded with MUNT Roland MT-32 MIDI emulation for DOSBox/ScummVM
  • Retroarch FCEUmm (NES) Emulator preconfigured for 4:3 horiz/vert overscan crop enabled w/ composite-direct-fbx pallete
  • Retroarch Picodrive (SMS/32X) Emulator preconfigured for 4:3 with 1X Sega Mastersystem & 1X Sega 32X resolution
  • Retroarch Gambatte (GB/GBC) emulator preset to Super Game Boy (Special 1 Pallete) mode with 2x integer scale SGB Overlay
  • Retroarch mGBA (GBA) emulator preset to Game Boy Player mode with 2x integer scale GBP Overlay
  • Other Retroarch handheld emulators preset for optimized wide display with overlay
  • Emulationstation preloaded with Ruckage's RetroPie menu icons
  • Emulationstation preloaded with Ruckage's snes-mini theme configured for 4:3
  • Custom ScummVM system artwork for snes-mini theme
  • Emulationstation systems ordered chronologically instead of alphabetically
  • Emulationstation preconfigured with best settings for analog A/V including best settings for video preview screensavers
What is Run-Ahead?
The Run Ahead feature calculates the frames as fast as possible in the background to "rollback" the action as close as possible to the input command requested.
I've enabled run-ahead on most of the 8 & 16-bit consoles and handhelds. A single frame (and using the second instance) is saved here, which dramatically improves input lag without affecting performance on a Pi3B+. More frames would require more hardware power, and may be achievable via overclocking.
lr-snes9x2010 consistent 60.0-60.2 FPS @ 60.098801hz lr-fceumm consistent 60.0-60.2 FPS @ 60.098801hz lr-beetle-pce-fast consistent 60.1-60.2 @ 60.000000hz lr-genesis-gx-plus consistent 59.9-60.2 FPS @ 59.922741hz (both genesis and sega cd) lr-picodrive consistent 59.9-60.2 FPS @ 59.922741hz (master system, game gear, and 32X) lr-gambatte consistent 60.0-60.2 FPS @ 60.098801hz (SGB2 framerate) lr-mgba consistent 59.8-60.4 FPS @ 60.002220hz (Gamecube framerate) 
Runahead Tested ~60FPS Stable:
  • Game Gear
  • Game Boy
  • Game Boy Color
  • Game Boy Advance
  • Master System
  • Megadrive
  • NES
  • PC Engine
  • PCE-CD
  • Sega 32X
  • Sega CD
  • SNES
Runahead Tested < 50FPS Unstable:
  • FB Neo
  • FB Alpha
  • Mame
  • N64
  • PlayStation
  • PSP
Runahead Untested:
  • Atari 800
  • Atari 2600
  • Atari 5200
  • Atari 7800
  • Atari Lynx
  • Coleco
  • Intellivision
  • MSX
What Does This NOT Have?
This doesn't have any ROMs (other than freeware test suites), BIOS files, music, screenshots, metadata, or videos concerning copywritten games. Other than the configurations and overlays, it has nothing that can't be downloaded through the repository or freeware.
Where Can I Get It?
You can download a premade image from Drive:
NOTE: Please expand your file system via Raspi-Config after your first boot, and reboot!
CRTPi4-RCA NTSC v3.4F: For Raspberry Pi4 Composite-Out @ 60hz
MD5: 7df8453c2e8029b06def7864351ec768 
CRTPi4-RCA PAL-D v3.4F: For Raspberry Pi4 Composite-Out @ 50hz
MD5: ab2bd6ab228bd6f58a22de15044fb46a 
How do I install the Arcade Configuration Pack?
These are the resolution-correct preset arcade configs for MAME/FBA including vertical games. There is roughly 38K files in there, spread out across several systems (arcade, fba, mame-libretro, and neogeo). Having these pre-installed would not allow either image to fit on the SD card used, and may not be needed for everyone. It's a fairly simple process that won't take more than a few minutes of your time.
  • Drop to shell or connect via SSH, and navigate to root (cd /)
  • Download the CRTPi-RCA_ArcadePack.zip with the command:
    sudo wget https://github.com/crtpi/CRTPi-Project/raw/masteCRTPi-RCA_ArcadePack.zip
  • Unzip and overwrite files with the command:
    sudo unzip -o -q CRTPi-RCA_ArcadePack.zip
  • Remove the zip with the command
    sudo rm CRTPi-RCA_ArcadePack.zip
  • Restore read/write access to the files you have overwritten with the command:
    sudo chmod a+rw -R /opt/retropie/configs/
How can I take full advantage of the 480i/240p Switching?
To force 480i for a system or game, you can create a '480i.txt' file inside the configuration folder of the system with a list of the file names (case insensitive, extension optional but recommended) you want to force.
If you wish to force 480i for a whole system, you can write "all" inside the '480i.txt' file.
Alternatively you can create a "240p.txt" file to force 480i to all games except for the ones inside the list.
You can read more about the script functionality here.
Example:
/opt/retropie/configs/psx/480i.txt containing "Bloody Roar 2.PBP" to force 480i for the file "Bloody Roar 2.PBP" /opt/retropie/configs/psx/480i.txt containing "all" to force 480i for all the PlayStation games. /opt/retropie/configs/ports/kodi/480i.txt containing "all" to force 480i on Kodi. 
I have X Issue! Help?
Why isn't there a Pi4 PAL version?
Try as I might, I have been unable to get a PAL signal out of the SDTV port on a Pi4. My BVM displays PAL-S and PAL-D fine, but neither will get anything but static. I don't even get a rolling B&W image, just horrible static. If you figure out a way, let me know!
I only have like 500mb of free space on my XXgb SD card!
You need to expand your file system via Raspi-Config. Follow these steps.
I want to switch back to lr-mupen64plus!
  • When launching an n64 game, mash buttons on the controller until the runcommand window comes up.
  • Select on "1 Set default emulator for n64" and choose "lr-mupen64plus"
  • Then "Q Exit (without launching)"
  • Launch the game again -- it will launch in the chosen emulator at the proper resolution
What A/V cable should I use for 3.5mm Composite?
I recommend the Zune A/V cable or XBOX 360E cable, you can find them on eBay and Amazon.
Samba Share won't work after I set up Wi-Fi!
Samba share service starts on boot, pending that a network is available. Configure your Wi-Fi then reboot first, and if that doesn't fix it then go into Retropie Setup > Configuration/Tools > Samba > Install Samba. Once it's complete, reboot and it should be golden.
USB-Romservice and/or Retropie-Mount don't work!
Follow this guide, but follow these steps before plugging in your thumb drive:
  • Go to Retropie-Setup
  • Update retropie install script
  • Go to Manage Packages -> Optional Packages
  • Scroll all the way down to usbromservice
  • Uninstall usbromservice
  • Install it again from Binary
  • Once finished, choose Configuration, then Enable USB Romservice
  • Reboot, and wait for it to fully boot in to ES
  • Plug in USB stick (has to be FAT32) and WAIT A LONG TIME (if your stick has a light, wait for it to stop flashing)
submitted by ErantyInt to u/ErantyInt [link] [comments]

CRTPi4-RCA v3.4FX - Composite TV-Out for your Pi4!

CRTPi Project Presents:

CRTPi4-RCA v3.4FX

A CRTPi image for running 240p via 3.5mm Composite on the Raspberry Pi4
Other Releases:
Changelog: v3.4FX for RCA (PAL Only) 5/18/2020
Changelog: v3.4FX for RCA (NTSC&&PAL) 5/17/2020
Changelog: v3.0F for RCA 5/11/2020
Changelog: v2.0F for RCA 4/1/2020
Changelog: v1.1FX 12/20/2019
Changelog: v1.0F Hotfix 10/31/2019
Changelog: v1.0F 10/29/2019
Changelog: v0.4 10/22/2019
Changelog: v0.3 10/2/2019
How does this even work!?
The amazing u/b0xspread has found a way to enforce modeswitching by watching the logs and processes, and continuing to enforce our desired mode long after the system wants to revert back. We're both expanding this scripting further to hopefully solve the same issues on the RGB and VGA forks -- but progress is slow due to the complex and varied nature of available resolution modes on those builds. But for now, let's just call this "black magic."
What Does That Look Like?
Here are some examples of games being played in beautiful 240p on CRT sets using the RCA Image!.
What is Different?
  • Retropie 4.6 (build 72132587 commit 05/07/20 Buster 10)
  • Retroarch 1.8.5
  • Full Apt-Upgrade for newest firmware and app dependancies (Recommended to repeat this function on your own Pi4)
  • 4GB (3872256 KB Uncompressed Image) (Compressed via WinRAR to 1043540KB)
  • SSH, Samba Share, and USB Rom Service enabled by default
  • Heavily modified Sakitoshi CRT-TVout script for switching between 480i and 240p
  • Further modified Sakitoshi script by u/b0xspread to allow video resolution switching on Pi4 Architecture
  • Optional overclock values in /boot/config.txt for Pi4 (disabled by default) [RECOMMENDED!]
  • NTSC @ 60hz 720/640x480 480i Resolution for Emulationstation & Kodi
  • PAL @ 50hz 720/640x576 576i Resolution for Emulationstation & Kodi
  • NTSC @ 60hz 640x480 Progressive (240 lines) for Retroarch
  • PAL @ 50hz 640x576 Progressive (288 lines) for Retroarch
  • Per-system custom refresh rates for Retroarch
  • Single-frame Run Ahead enabled for many 8-bit & 16-bit consoles and handhelds for Retroarch
  • Optional 480i mode for PSX and Arcade games
  • Preloaded with free 240p test suites for multiple consoles
  • Preloaded with additional stable (opt) Retroarch emulators
  • Preloaded with DOSBox and ScummVM
  • Preloaded with various 4:3 splashscreens from the RPiF download
  • Preloaded with 4:3 Ruckage's runcommand launching screens for supported systems
  • Custom 4:3 Arcade DOJ "Winners DO Use Drugs" splash screen.
  • Preloaded with MUNT Roland MT-32 MIDI emulation for DOSBox/ScummVM
  • Retroarch FCEUmm (NES) Emulator preconfigured for 4:3 horiz/vert overscan crop enabled w/ composite-direct-fbx pallete
  • Retroarch Picodrive (SMS/32X) Emulator preconfigured for 4:3 with 1X Sega Mastersystem & 1X Sega 32X resolution
  • Retroarch Gambatte (GB/GBC) emulator preset to Super Game Boy (Special 1 Pallete) mode with 2x integer scale SGB Overlay
  • Retroarch mGBA (GBA) emulator preset to Game Boy Player mode with 2x integer scale GBP Overlay
  • Other Retroarch handheld emulators preset for optimized wide display with overlay
  • Emulationstation preloaded with Ruckage's RetroPie menu icons
  • Emulationstation preloaded with Ruckage's snes-mini theme configured for 4:3
  • Custom ScummVM system artwork for snes-mini theme
  • Emulationstation systems ordered chronologically instead of alphabetically
  • Emulationstation preconfigured with best settings for analog A/V including best settings for video preview screensavers
What is Run-Ahead?
The Run Ahead feature calculates the frames as fast as possible in the background to "rollback" the action as close as possible to the input command requested.
I've enabled run-ahead on most of the 8 & 16-bit consoles and handhelds. A single frame (and using the second instance) is saved here, which dramatically improves input lag without affecting performance on a Pi3B+. More frames would require more hardware power, and may be achievable via overclocking.
lr-snes9x2010 consistent 60.0-60.2 FPS @ 60.098801hz lr-fceumm consistent 60.0-60.2 FPS @ 60.098801hz lr-beetle-pce-fast consistent 60.1-60.2 @ 60.000000hz lr-genesis-gx-plus consistent 59.9-60.2 FPS @ 59.922741hz (both genesis and sega cd) lr-picodrive consistent 59.9-60.2 FPS @ 59.922741hz (master system, game gear, and 32X) lr-gambatte consistent 60.0-60.2 FPS @ 60.098801hz (SGB2 framerate) lr-mgba consistent 59.8-60.4 FPS @ 60.002220hz (Gamecube framerate) 
Runahead Tested ~60FPS Stable:
  • Game Gear
  • Game Boy
  • Game Boy Color
  • Game Boy Advance
  • Master System
  • Megadrive
  • NES
  • PC Engine
  • PCE-CD
  • Sega 32X
  • Sega CD
  • SNES
Runahead Tested < 50FPS Unstable:
  • FB Neo
  • FB Alpha
  • Mame
  • N64
  • PlayStation
  • PSP
Runahead Untested:
  • Atari 800
  • Atari 2600
  • Atari 5200
  • Atari 7800
  • Atari Lynx
  • Coleco
  • Intellivision
  • MSX
What Does This NOT Have?
This doesn't have any ROMs (other than freeware test suites), BIOS files, music, screenshots, metadata, or videos concerning copywritten games. Other than the configurations and overlays, it has nothing that can't be downloaded through the repository or freeware.
Where Can I Get It?
You can download a premade image from Drive:
NOTE: Please expand your file system via Raspi-Config after your first boot, and reboot!
CRTPi4-RCA NTSC v3.4F: For Raspberry Pi4 Composite-Out @ 60hz
MD5: 7df8453c2e8029b06def7864351ec768 
CRTPi4-RCA PAL-D v3.4F: For Raspberry Pi4 Composite-Out @ 50hz
MD5: ab2bd6ab228bd6f58a22de15044fb46a 
How do I install the Arcade Configuration Pack?
These are the resolution-correct preset arcade configs for MAME/FBA including vertical games. There is roughly 38K files in there, spread out across several systems (arcade, fba, mame-libretro, and neogeo). Having these pre-installed would not allow either image to fit on the SD card used, and may not be needed for everyone. It's a fairly simple process that won't take more than a few minutes of your time.
  • Drop to shell or connect via SSH, and navigate to root (cd /)
  • Download the CRTPi-RCA_ArcadePack.zip with the command:
    sudo wget https://github.com/crtpi/CRTPi-Project/raw/masteCRTPi-RCA_ArcadePack.zip
  • Unzip and overwrite files with the command:
    sudo unzip -o -q CRTPi-RCA_ArcadePack.zip
  • Remove the zip with the command
    sudo rm CRTPi-RCA_ArcadePack.zip
  • Restore read/write access to the files you have overwritten with the command:
    sudo chmod a+rw -R /opt/retropie/configs/
How can I take full advantage of the 480i/240p Switching?
To force 480i for a system or game, you can create a '480i.txt' file inside the configuration folder of the system with a list of the file names (case insensitive, extension optional but recommended) you want to force.
If you wish to force 480i for a whole system, you can write "all" inside the '480i.txt' file.
Alternatively you can create a "240p.txt" file to force 480i to all games except for the ones inside the list.
You can read more about the script functionality here.
Example:
/opt/retropie/configs/psx/480i.txt containing "Bloody Roar 2.PBP" to force 480i for the file "Bloody Roar 2.PBP" /opt/retropie/configs/psx/480i.txt containing "all" to force 480i for all the PlayStation games. /opt/retropie/configs/ports/kodi/480i.txt containing "all" to force 480i on Kodi. 
I have X Issue! Help?
Why isn't there a Pi4 PAL version?
Try as I might, I have been unable to get a PAL signal out of the SDTV port on a Pi4. My BVM displays PAL-S and PAL-D fine, but neither will get anything but static. I don't even get a rolling B&W image, just horrible static. If you figure out a way, let me know!
I only have like 500mb of free space on my XXgb SD card!
You need to expand your file system via Raspi-Config. Follow these steps.
I want to switch back to lr-mupen64plus!
  • When launching an n64 game, mash buttons on the controller until the runcommand window comes up.
  • Select on "1 Set default emulator for n64" and choose "lr-mupen64plus"
  • Then "Q Exit (without launching)"
  • Launch the game again -- it will launch in the chosen emulator at the proper resolution
What A/V cable should I use for 3.5mm Composite?
I recommend the Zune A/V cable or XBOX 360E cable, you can find them on eBay and Amazon.
Samba Share won't work after I set up Wi-Fi!
Samba share service starts on boot, pending that a network is available. Configure your Wi-Fi then reboot first, and if that doesn't fix it then go into Retropie Setup > Configuration/Tools > Samba > Install Samba. Once it's complete, reboot and it should be golden.
USB-Romservice and/or Retropie-Mount don't work!
Follow this guide, but follow these steps before plugging in your thumb drive:
  • Go to Retropie-Setup
  • Update retropie install script
  • Go to Manage Packages -> Optional Packages
  • Scroll all the way down to usbromservice
  • Uninstall usbromservice
  • Install it again from Binary
  • Once finished, choose Configuration, then Enable USB Romservice
  • Reboot, and wait for it to fully boot in to ES
  • Plug in USB stick (has to be FAT32) and WAIT A LONG TIME (if your stick has a light, wait for it to stop flashing)
submitted by ErantyInt to crtgaming [link] [comments]

CRTPi-RGB v3.0 - Buster Busts Loose!

CRTPi Project Presents:

CRTPi-RGB v3.0

A CRTPi image for running 240p via GPIO RGB DAC Hats
Other Releases:
Changelog: v3.0 for 888 & 666 05/12/2020 - Emergency Fixes
Changelog: v3.0 for 888 & 666 05/08/2020
Changelog: v2.0 for 888 & 666 03/25/2020
Changelog: v1.1X for 666 12/20/2019
Changelog: v1.1X for 888 & 666 12/19/2019
Changelog: v1.0 for 888 & 666 11/7/2019
Changelog: v1.0 for 666 10/24/2019
Changelog: v1.0 for 888 & 666 10/22/2019
Changelog: v0.3 for 888 & 666 10/2/2019
Changelog: v0.2 for 888 09/27/2019
Changelog: v0.1 for 888 09/20/2019
Required Hardware:
What is a RetroTINK? Or a VGA666?
RetroTINK is a GPIO hat for the Raspberry Pi3/3B+ that converts digital video signal back into 24-bit analog. It provides output over RCA, S-Video, Component, and VGA -- as well as supporting CSYNC, super-resolutions, and custom resolution timings.
VGA666 is a GPIO hat for the Raspberry Pi that converts digital video signal back into an 18-bit analog out via VGA. It also allows for super-resolutions and custom resolution timings.
Pi2SCART is a GPIO hat for the Raspberry Pi that converts digital video signal back into an 18-bit analog RGB out via SCART. It also allows for super-resolutions and custom resolution timings.
What Does That Even Mean?
It makes your Pi capable of outputting a true 240p analog signal for CRT televisions and monitors, and is capable of 5x (1600x240) and higher super resolutions.
What Does That Look Like?
I don't have the greatest pics saved for comparison, but here's some examples of the 888.
What is Different? (888 & 666)
  • Retropie 4.6 (build 7c5e31bb commit 05/07/20 Buster 10)
  • Retroarch 1.8.5
  • 4GB (3872256 KB) Uncompressed Image (Compressed via WinRAR to 982256 KB)
  • SSH, Samba Share, and USB Rom Service enabled by default
  • Custom /boot/config.txt settings for DPI output and custom HDMI timings
  • Optional overclock values in /boot/config.txt for Pi2 & Pi3B (disabled by default)
  • Modified Michael Vencio's Runcommand “On Start” and “On End” scripts to automatically change the resolution system-by-system and game-by-game
  • Modified Runcommand "On Start" script to allow creation of game-specific arcade configs for arcade/fba/mame-libretro/neogeo
  • NTSC @ 60hz 320x240 resolution for Emulationstation and DOSBox/ScummVM/Kodi
  • NTSC @ 60hz 2048x240, 1920x240, and 1600x240 resolution for Retroarch
  • Per-system custom refresh rates for Retroarch
  • Single-frame Run Ahead enabled for many 8-bit & 16-bit consoles and handhelds for Retroarch
  • Preloaded with free 240p test suites for multiple consoles with art by chipsnblip
  • Preloaded with additional stable (opt) Retroarch emulators
  • Preloaded with DOSBox and ScummVM
  • Preloaded with various 4:3 splashscreens from the RPiF download
  • Custom 4:3 Arcade DOJ "Winners DO Use Drugs" splash screen.
  • Preloaded with MUNT Roland MT-32 MIDI emulation for DOSBox/ScummVM
  • Preloaded with custom runcommand launching screens for supported systems
  • Preconfigured MOST Retroarch emulators for proper Integer Scale SuperRes
  • Retroarch FCEUmm (NES) Emulator preconfigured for 8:7 vert overscan crop enabled w/ composite-direct-fbx palette
  • Retroarch Gambatte (GB/GBC) emulator preset to Super Game Boy (SGB2 auto coloration) mode with Integer Scale Overlay
  • Retroarch mGBA (GBA) emulator preset to Game Boy Player mode with Integer Scale Overlay
  • Emulationstation preloaded with Ruckage's RetroPie menu icons
  • Emulationstation preloaded with Ruckage's snes-mini (default) and nes-mini themes configured for 4:3
  • Custom ScummVM system artwork for snes-mini theme
  • Emulationstation systems ordered chronologically instead of alphabetically
  • Emulationstation preconfigured with best settings for analog A/V including best settings for video preview screensavers
  • Custom Retropie menu scripts for switching between Retrotink and VGA666-based hardware ___
What is Run-Ahead?
The Run Ahead feature calculates the frames as fast as possible in the background to "rollback" the action as close as possible to the input command requested.
I've enabled run-ahead on most of the 8 & 16-bit consoles and handhelds. A single frame (and using the second instance) is saved here, which dramatically improves input lag without affecting performance on a Pi3B. More frames would require more hardware power, and may be achievable via overclocking.
lr-snes9x2010 consistent 60.0-60.2 FPS @ 60.098801hz lr-fceumm consistent 60.0-60.2 FPS @ 60.098801hz lr-beetle-pce-fast consistent 60.1-60.2 @ 60.000000hz lr-genesis-gx-plus consistent 59.9-60.2 FPS @ 59.922741hz (both genesis and sega cd) lr-picodrive consistent 59.9-60.2 FPS @ 59.922741hz (master system, game gear, and 32X) lr-gambatte consistent 60.0-60.2 FPS @ 60.098801hz (SGB2 framerate) lr-mgba consistent 59.8-60.4 FPS @ 60.002220hz (Gamecube framerate) 
To disable runahead for a game (or emulator):
Quick Menu > Latency > Run-Ahead to Reduce Latency > OFF 
What about your new Per-Game Configs and Snap-Shader?
The RGB and VGA forks are now utilizing Snap-Shader, plus a newly-enhanced runcommand-onstart script, with provision for user-specified per-game configuration!
Here's the new script:
https://github.com/crtpi/CRTPi-Project/blob/masteRGB-to_opt/retropie/configs/all/runcommand-onstart.sh 
Here's information about Snap-Shader:
https://github.com/ektgit/snap-shader-240p 
And here's a quick rundown on how it works:
Not only does the new script carry forward the per-core scripting for 2048x / 1920x / and 1600x resolutions -- but adds per-game scripting by adding a text file to the system config and naming the rom(s) within the file. This allows you to force 2048x on a system that defaults to 1920x. This is especially useful for PSX, FDS, PCE/PCE-CD, and MAME for the few games that are 256 or 512 wide. Below are some example config files:
/opt/retropie/conifgs/psx/256.txt
Brave Prove Castlevania - Symphony of the Night Crash Bandicoot Final Fantasy Origins Final Fantasy Tactics 
/opt/retropie/conifgs/megadrive/256.txt
Bubble And Squeak Bubsy in - Claws Encounters of the Furred Kind Bugs Bunny in Double Trouble Caesars Palace Captain America and the Avengers 
/opt/retropie/conifgs/fds/320.txt
Akumajou Dracula Donkey Kong Otocky Super Mario Brothers 2 
You get the jist. It doesn't need an extension, not case sensitive, but should match the ROM name (including punctuation) exactly. This forces them to launch in 2048x240p instead of the default 1920x240p. This gives the end user full control on a game-per-game basis over the horizontal integer. You'll still need to write a retroarch game config to override the defaults there, but this at least gets you the right field. For games with odd/shifting vertical resolutions (like Chrono Cross, Battle Arena Toshinden, Castlevania SotN, etc.), a single pass of snap-shader is applied (snap-basic, nearest neighbor filtering, and "don't care" scale).
What Does This NOT Have?
This doesn't have any ROMs (other than freeware test suites), BIOS files, music, screenshots, metadata, or videos concerning copy-written games. Other than the configurations and overlays, it has nothing that can't be downloaded through the repository or freeware.
Where Can I Get It?
You can download a premade image from Google Drive:
NOTE: Please expand your file system via Raspi-Config after your first boot, and reboot!
CRTPi-RGB v3.0: For Pi3B/3B+ with Retrotink, Pi2SCART, RGB-Pi, or VGA666
MD5: d9d28f5ae8fe5cc829348be4b5a103fc 
Install Instructions:
For Retrotink Ultimate:
  • Download image and unRAR it.
  • Flash to your SD card with Win32DiskImager or Etcher.
  • Boot as normal, run Raspi-Config, and choose Expand Filesystem from Advanced Options.
  • Reboot from Raspi-Config, and enjoy your Pi!
For Pi2SCART/RGB-Pi/VGA666:
  • Download image and unRAR it.
  • Flash to your SD card with Win32DiskImager or Etcher.
  • BEFORE BOOTING Edit 'config.txt' on your SD card's BOOT partition, uncomment the section relevant to your device, and comment all other devices.
    ## Pi2SCART & VGA666 only!!
    #dtoverlay=vga666
    #hdmi_timings=320 1 16 30 34 240 1 2 3 22 0 0 0 60 0 6400000 1 #Pi2SCART/VGA666 [email protected]
    __
    ## RGB-Pi only!!
    #dtoverlay=pwm-2chan,pin=18,func=2,pin2=19,func2=2
    #dtoverlay=rgb-pi
    #dpi_output_format=6
    #hdmi_timings=320 1 16 30 34 240 1 2 3 22 0 0 0 60 0 6400000 1 #RGB-Pi [email protected]
    __
    ## RetroTINK Ultimate only!!
    #dtoverlay=dpi24
    #dpi_output_format=519
    #hdmi_timings=320 1 23 30 34 240 1 4 3 15 1 0 0 60 0 6400000 1 #RetroTINK [email protected]
__
  • Boot as normal, run Raspi-Config, and choose Expand Filesystem from Advanced Options, then reboot.
  • In Emulationstation, run "Enable VGA666" from the Retropie menu.
  • Your system will automatically reboot. Enjoy your Pi!
To Revert VGA666 to Retrotink Settings
  • In Emulationstation, run "Enable Retrotink" from the Retropie menu.
  • Your system will automatically reboot with the new settings.
Default Retroarch Keyboard Hotkeys
*SPACE: Enable Hotkey* F1 Menu F2 FF Toggle F3 Reset F4 Cheat Toggle F5 Save State F6 Load State F7 Change State - F8 Change State + F9 Screenshot F10 Mute ENTER: Exit 
I have X Issue! Help?
I only have like 500mb of free space on my XXgb SD card!
You need to expand your file system via Raspi-Config. Follow these steps.
Samba Share won't work after I set up Wi-Fi!
Samba share service starts on boot, pending that a network is available. Configure your Wi-Fi then reboot first, and if that doesn't fix it then go into Retropie Setup > Configuration/Tools > Samba > Install Samba. Once it's complete, reboot and it should be golden.
USB-Romservice and/or Retropie-Mount don't work!
Follow this guide, but follow these steps before plugging in your thumb drive:
  • Go to Retropie-Setup
  • Update retropie install script
  • Go to Manage Packages -> Optional Packages
  • Scroll all the way down to usbromservice
  • Uninstall usbromservice
  • Install it again from Binary
  • Once finished, choose Configuration, then Enable USB Romservice
  • Reboot, and wait for it to fully boot in to ES
  • Plug in USB stick (has to be FAT32) and WAIT A LONG TIME (if your stick has a light, wait for it to stop flashing)
Timings for Boot and Runcommand
320 x 240p @ 60hz Timings: Emulationstation, DOSBox, ScummVM, etc.
320 1 15 30 42 240 1 4 3 15 1 0 0 60 0 6400000 1 Retrotink 320x240p Timing 320 1 16 30 34 240 1 2 3 22 0 0 0 60 0 6400000 1 #VGA666 320x240p Timing 
Integer Scale Super-Resolution 240p @ 60hz Timings: All Retroarch Emulators
2048 1 160 202 320 240 1 3 5 14 0 0 0 60 0 42954545 1 #256x240/224p 1920 1 137 247 295 240 1 3 7 12 0 0 0 60 0 40860000 1 #320x240/224p 1600 1 73 157 204 240 1 4 3 15 0 0 0 60 0 32000000 1 #320x240/224p Alternate 
submitted by ErantyInt to u/ErantyInt [link] [comments]

Binary Option Master STT Indicator Signal For Iq Option Live Trading Price Action Binary Options Signals That Work - YouTube BINARY OPTION TELEGRAM SIGNAL 2020  BINARY MONSTER ... Binary options trading  Binary options signals - YouTube FXXTOOL BOT SIGNALS IQ OPTION - MASTER SIGNAL ALL BINARY ... FRZ Binary Options Master Robot - Binary Signals & IQ Automation

FX Master Code V2 binary trading system will give you accurate signals based on my tested and winning 1 minute binary options strategy. ... I just tried FX Master Code with IQ Option and it is really working nicely. I had 9 ITM out of 9 trades. God bless you." Verified Member "Thanks Johan, it all make sense now, I've been doing heavy studying and so far no losses using FX Master Code and ... Types of Binary Signals. There are some binary option signal types available that produce sound advice. It is wise for you to review the models on offer to ascertain the most suitable for your needs. It is possible to receive signals through software, and these types are also listed below. Some signals providers have a free trial period so you can evaluate the service. Ideally you want a set ... Binary Master Strategy - this is a very simple system, which is suitable even for beginners. In addition, it also profitable - 70 % win rate. Binary Master is based on the testimony of only two indicators: PinBar indicator, SMA Crossover Justin. When the signals of these indicators coincide we can say that did a call to action - buy PUT or CALL option Regardless of your experience level, you can now join in with over 5000+ other members and begin learning from a Master Trader with over 15 years experience in trading the markets. With our consistent strategies, members aim to take massive profits from the market every single day by watching our charts which host many of our custom developed indicators and tools. Using Quantum Binary Signals. Traders have the option to have signals delivered on various platforms, including mobile notifications and email. The signals provide a simple solution for traders wishing to obtain and comprehend trading and investment-related data. The website provides an easy way to join, offering membership with only a few required details, which can be entered on the site ... New Robot Signal Trading Binary Options, support for all binary options broker, iq option, spectre.ai, binary.com, olymptrade,expert option. Here, we will have free binary signals as well as paid ones. You will know the pros and cons of each product in our reviews. We will also cover the basics of trading signals. Moreover, you will learn why binary trading signals are required and how to use them. Without further ado, let’s begin with the definition of trading signals. master pro fbx bot best binary option signal 2019 Spectre.AI is an industry leading blockchain based trading platform. It claims to be the future of digital option, forex and CFD trading providing brokerless access to international markets via the platform and mobile app. Powered by DALP, the platform executes smart option contracts that are fraud-free. Best Binary Option Strategy Binary Options Signals – a reliable platform for the best Binary Options Strategy and Binary Signals, opens the door of endless earning possibilities. We are your true friend and a guide to help you in maximizing your profits without risk of losing precious investment. Binary Options System; Binary Options Profit System; HLOC Binary Options System; Simple Binary Options System; Win Win Binary Options Template; Mak Binary Options Template; Binary Options Channel; Binary Options Calculator; Binary Options Signals; Binary Options Trader; Binary Options Buddy 2.0; Binary Options Oscillator; Binary Options Arrow ...

[index] [1152] [18235] [20019] [20992] [13215] [4648] [16553] [24268] [1725] [20412]

Binary Option Master STT Indicator Signal For Iq Option Live Trading

How to trade binary options successfully using FX Master Code trading signals. Can you really make money with binary options? Well, if you manage risk and trade a binary options trading strategy ... One minute strategy to trade price action trading signals. Watch how I use simple trading rules to increase win rate. Get 10x Trading System: https://trading... Hi Friends I Will Show In This Video Binary Option Master STT Indicator Signal For Iq Option Live Trading _____ Download : ... FXXTOOL BOT SIGNALS IQ OPTION - MASTER SIGNAL ALL BINARY OPTION TRADING - beginer winning iq option - Duration: 9:31. BINARY OPTION FOREX 25,231 views. 9:31. Watch high-speed trading in action ... WELCOME TO BINARY MONSTER ***** In this channel we are give price action learning videos and best binary option signal service ... Binary options trading Binary options signals Hi there! I'm Lady Trader and today I'll show you my binary options strategy 2020 that I use in binary tradin... FXXTOOL BOT - MASTER SIGNALS ALL BINARY OPTION TRADING DOWNLOAD UPDATE Fxxtool v.1.4.0: https://robotbinarysignals.ecwid.com/Bot-FXXtool-V-1-4-0-Master-Pro-S...

http://binaryoptiontrade.matchmin.tk