Author Topic: Hard Drive (Default Events) *New* [Anatomy Video]  (Read 14427 times)

I am particularly enjoying the Diamond casing's look, gives it a sci-fi vibe to it.

The drive sequentially locks, but can only be totally locked or unlocked with the erase chip. You can't pick and choose what to erase or write to in..

... well actually that is another bug. I've just realized that means if you have half a drive written and try to unlock it, then other half will become locked. forget lol.

I have just completed a modified HD with memory prongs minus this bug.

Examples: With this modification, if you input the first ten, but leave the last five, the first ten lock. Then, if you lock it, the last five lock but the first ten do nothing and stay locked.
If you write all of them, all of them lock. Then, pressing the lock/rewrite button on your input node will do absolutely nothing, but pressing it a second time will unlock everything.

As of yet I have not figured out any way to add a complete erase to the modification; that is, to set all of them back to 1. I only know it will mean making the memory prongs and 8-state system instead of 2. It may already be being worked on, along with the official fix for the locking bug, but I had this idea and thought I would try it out, and it works.

Technically the system would:
> have to read memory packets
> unlock the packet
> add as much as it needs to hit 8 (which is the value that equals 1 since its a reset)

The fix needs to be selective locking / unlocking. This could be achieved by using another timing system perhaps, but it'll need some thinking.

So,

I've been having these crazily ambitious ideas with what to do with the brick hard drive concept, and most of them come together to form this musicbox thing.

The idea follows the general theme MicroBlock put for the MBLK Precision Harddrive: No named bricks, default events only, default bricks only. It might, however, conclude with one custom soundpack.

Just thought I'd put it by here first, since it will be based off this concept and credits it for this, and I don't want to go into it if it might jeopardize the context or other factors of this project. It's going to be the most exceedingly, insanely difficult eventing project I've ever gone into in Blockland, so it will take a while.

It will be about the size of the average small BL house, and it might have TWO different output nodes, including the HIO port either way. I have also been experimenting with a storage concept I currently dub "Composite storage" involving memory chip pairs per single prong. This is thus far what I'm on, because it is a highly ambitious challenge to get it right.

Some of my plans for this include using the Precision HD as an index for the Musicbox thing; a selector for different sequences (Songs) as well as a memory repository for other stuff. I will also try to utilize any other components released by MB. It will also have its own output system for playback purposes. I estimate the end result will have at least several thousand brick-bits and states, suitable for composite song storage. The first edition will use the default synths and have a unique keyboard input, similar to a piano input, but with some sort of chord-input system and timing delayer.

Once again, just thought I'd put this by this topic first, so that I don't pull this giant project off against any ill wills.

I like the direction all of this is heading in.

So kind of like the thing Truce built a year ago with default events that can save pictures? I imagine this can probably do more though.

So kind of like the thing Truce built a year ago with default events that can save pictures? I imagine this can probably do more though.

Similar in the idea you should be able to save states with events, but entirely different in that it inteprets information through relays, projectiles, and colors. Truce's didnt' do nearly as much, and couldn't be adapted-- nor could it send through a cable.

Same base idea, totally different events. This is far more complex.

How did you do this without VCE.

How did you do this without VCE.
I think Icy used relay and toggle events.

I think Icy used relay and toggle events.
I thought of that, but look at the size.
You couldn't store bullstuff if he did that. He had to have used something else.
Just saying, this could be done with 1 brick via VCE. Though what's the fun in that.

How did you do this without VCE.

Hey there, you recently inquired into my hard drive.

It works using relays and toggle events basically. If you want to understand exactly how, I have a video here that explains in detail what it does: http://www.youtube.com/watch?v=kRGAj2kJncY

Its devoid of any event mods, only default.

Thanks for taking interest.