www.algodoo.com

Now, I need some people to run AFS System project.
I need some thymers to work with Codec Cards, some designers that will make new, more attractive design, and some beta testers. You can be the beta tester by downloading the AFS scene if you will add the comment, maybe with bug report. So, do it please!


The target of this collab is to make new, more effective storage system. Without lasers and phun compatible.
Because i can't run Algodoo now, i'm on linux...

Well, Now i need some people. I tried to beat this problem, but people didn't download it so much and the didn't have an interest of it. If you know, i made some floppies that had 6 storages and 24 storages. They were very poor, becuz they had only text support without textures and anything else. Yeah, it was about year ago, when i learned thyme and i used copied or stealed parts because i didn't make my owns... That was good times, almost better than now...

There is the scene i talked about.



So, join in and help to make new storage type with new, more capacity...

Jobs that we need:
Thymer for Codec Cards
Designers
Beta Testers

Hey!!! I need some people!!! If you can't understand, tell me, and i'll explain. Or just join in! It's FREE ! or not?

Don't double-post after one day.

Hmmm... Chronos... don't be foe, be a friend and don't post please silly things in here Better join in!

Chronos wrote:Don't double-post after one day.

Chronos, you are the only spammer here with over 2500 posts.
I think this collab is pretty useless because no one likes floppies xD

jedi wrote:

Chronos wrote:Don't double-post after one day.

Chronos, you are the only spammer here with over 2500 posts.
I think this collab is pretty useless because no one likes floppies xD

You need to learn to tell the difference between spamming and posting. You also need to stop looking stupid calling someone out on something untrue.

Besides, floppies would work the same as the CDs that people have made, just in a case.

Jedi, True, but i know some ppl that likez floppiez

Ok, but this floppy does have more features than classic floppy or classic CD made in PHUN!
It have 4 storages, every can store Text + Texture, and two can store Color too.
Well, the first storage is used for formate, for example : TXT, TXT+, TEX+ and the reader sends this to Codec Cards and they will identify the codec or formate and then the Codec Card will send the content to the monitor.
Well, if you don't understand, it looks like this:

Storage Box 1 ---> Identyfier
(Reader) (Codec Cards)
(Text)

The second stores the text, if you use TXT, TXT+ or TEX+ codec

(Identyfied)
Codec Card ---> Monitor
/\ /\ /\
| | |
Storage Box 2
(Text)

The third stores texture if you use TXT+ codec. I know, the texture could be placed in the first or second box, but i want to full the storage space

(Identyfied)
Codec Card ---> Monitor
/\ /\ /\
| | |
Storage Box 3
(Texture)

The fourth stores color of screen if you use TEX+ codec.

(Identyfied)
Codec Card ---> Monitor
/\ /\ /\
| | |
Storage Box 4
(Color)


There are full charts:


TXT Codec Chart

(Reader) __________(Codec Cards)___________
Storage Box 1 ---> | Identyfier | ---> Monitor
(Text) =================================
/\ /\ /\
| | |
Storage Box 2
(Text)

TXT+ Codec Chart

(Reader) __________(Codec Cards)___________
Storage Box 1 ---> | Identyfier | ---> Monitor
(Text) =================================
/\ /\ /\ /\ /\ /\
| | | | | |
Storage Box 2 Storage Box 3
(Text) (Texture)

TEX+ Codec Chart

(Reader) __________(Codec Cards)___________
Storage Box 1 ---> | Identyfier | ---> Monitor
(Text) =================================
/\ /\ /\ /\ /\ /\ /\ /\ /\
| | | | | | | | |
Storage Box 2 Storage Box 3 Storage Box 4
(Text) (Texture) (Color)

Can I be Designer??
My idea:

You can put hundreds of tiny tiny squares on the reader and the disk that have text opacity is 0 and the text is something like: ["TEXT", "your text here", "TEXTPOSITION", ["X", 1234, "Y", 1234], (text2, textposition2 and so on) "IMAGE1", "blah.png", (image2 and so on...), "CODE", ["PRINT", "your code here"]] . Sorta hard, but I know you can do it.

Heh, you can be... but i think i ended it up a little...

Hm...

Are you using phun or algodoo?

Kutis 96 wrote:Heh, you can be... but i think i ended it up a little...

Hm...

Are you using phun or algodoo?

I am using phun. I need to use phun because, like you, I am using Wine (if you are still Kutis96.Linux.Ubuntu on algobox).

cocolover76 wrote:

Kutis 96 wrote:Heh, you can be... but i think i ended it up a little...

Hm...

Are you using phun or algodoo?

I am using phun. I need to use phun because, like you, I am using Wine (if you are still Kutis96.Linux.Ubuntu on algobox).

Nope, he is now using a copy of XP with algodoo.

his skype is now
kutis96.algodoo.phun
as he forgot his old password

Fell free to also add me on skype(Name is in signature), i am a beta tester for AHOX... although kutis does forget that sometimes

This was made last year.

I actually thought about mentioning the "Please don't bump" thing, but I restrained myself.

I got micro-flamed last time I did that.

Someone Else wrote:I actually thought about mentioning the "Please don't bump" thing, but I restrained myself.

I got micro-flamed last time I did that.

Me too! Also welcome to the forums cocolover76!

Anyway, I have an idea for a disc drive. Basically, a, well, disc with a lot of coded boxes on the edge. These are indexed by controllerAcc and the thing is actuated by materialVelocity.

A scripted box on the edge of the disc would be programmed with its own controllerAcc- stick in a number, it finds the storage box with the appropriate code, and sets its own text to the text of the appropriate box.

In that controller box goes this code:

Code: Select all

{e.other.textureMatrix(8) == 2.5} ? {
   friction = +inf;
   e.other.text = text;
   text= "";
   controllerAcc = e.other.textureMatrix(7)
} : {};
{math.toInt(e.other.controllerAcc) == e.other.controllerAcc} ? {materialVelocity = controllerAcc - e.other.controllerAcc
} : {};
{e.other.controllerAcc == controllerAcc} ? {
   friction = 0;
   text = e.other.text
} : {}


The controller box must be shoved into the disc by a spring. You must hit the controller box with another box with 2.5 for the last textureMatrix value and the target address in the second-to-last textureMatrix value.

Then, once the disc has stopped moving, hit the controller box again with the same box.

I have an idea for something like a film drive.

You put a program on each "frame" and the first one is a selector program, and a conveyor belt communicates with the selector program and moves the film until it is on the right frame and then, motorized pulleys push down a collider which collides with the frame and gets the program.

This would be useful for something like a game.

And, of course, not only the selector frame can move the conveyor, but other frames also can.



Just an idea....

1 more thing: I like this post because my FIRST post is on here.

So that's kinda like a highly advanced Turing machine?

One that can do a lot mare than read values, write values, set its own internal state, and move the tape one click?

Someone Else wrote:So that's kinda like a highly advanced Turing machine?

One that can do a lot mare than read values, write values, set its own internal state, and move the tape one click?

Yep.

Sounds good. Now... How to increment the tape...

I'm thinking a Geneva-wheel-type system. The tape would be a long chain, set up in such a way that when you put it in a pipe, it cannot stretch or compress.

Each link would have a vertical slot in it.

A disc on a noncolliding, motorized stick would be able to push the chain one link at a time in either direction. Each clockwise rotation moves the chain one link to the right, each counterclockwise rotation moves the chain one link to the left.

The disc dips down into a slot just as the stick is horizontal, moves the chain to the left or right as it rotates around, and finally exits the slot just as it returns to horizontal.

This image does a good job of illustrating the principle.

Now imagine the driven wheel as a straight rack.

Each link would be indexed by controllerAcc, and somehow it would use scene.my.toAddress and scene.my.currentAddress to tell the hinge to go forward, backward, or stop.

You know, I will try to build this now.

Someone Else wrote:You know, I will try to build this now.

You don't have to. I found one on Algobox.

But this one looks REALLY BAD if you have the fireworks aka annoying red lines (which I have had ever since 5 months ago).

Oh, and don't expect a reply from me until summer because I have TRILLIONS of things to do.
I may reply if I get lucky.

You can get rid of those redlines with F5 or something like that.

cocolover76 wrote:

Someone Else wrote:You know, I will try to build this now.

You don't have to. I found one on Algobox.

Well, I want to build one myself.

But only if I can find time to do it, and I actually do it, not something else.

I actually have built a somewhat rudimentary text-programmed computer.

However, I still haven't decided how exactly I will make it move the tape.