Algodoo

Great! It needs limitations and more speed! I'll do that for you!

Nice 8/10! Good artwork (it's a perfect tribute to the original game ^^)

Perfect artwork!

Good job!

Thanks! ^^ You're great! Crossing the cables wont work! We need more cable segments with different collision groups or a new script method for the circles and boxes..

@all: Thanks for your comment and rating! It was a very hard scripting work

@bukk530: You got it!

Very nice improvement of Bronies scene! Works fine ^^
Did you use a global text string and on-key functions?

A new data cable is under construction


Imagine this as the cable made by RA2lover and me:
-o-o-o-o-o-o-o-o-

o=circle
-=box

This is the collision scheme:
Frame 1: -o-o-o-o-o-o-o-o -
Frame 2: - o-o-o-o-o-o-o-o-
Frame 3: -o-o-o-o-o-o-o-o -
...
[8 collisions per frame (cable lenght = 4)]

RED = collision
BLUE = no collision

The new cable should work like this:
Frame 1: -o -o-o-o-o-o-o-o-
Frame 2: - o- o-o-o-o-o-o-o-
Frame 3: -o -o -o-o-o-o-o-o-
Frame 4: -o- o- o-o-o-o-o-o-
Frame 5: -o-o -o -o-o-o-o-o-
...
[1-8 collisions per frame (cable lenght = 4)]

RED = collision
BLUE = no collision
This will increase the performance of cables a lot.

Here is the new cable!

NOTE: Keep in mind that this new cable could have less performance if it gets a 50Hz input signal, but peripherals shouldn't send at this constant frequency

Quote [lollerman]: "...and 4 to first and second texturematrix numbers..."
You mean: ...and 4 to first and fifth texturematrix numbers...

Version 2 is ready soon..

OMG! That's godlike

Fantastic! 10/10

Nice mechanism! 10/10

Now it should work

Good idea!

Thank you! ^^
I know ^^ It's only research
It's fixed!!

IMMA FIRIN' MA LAZOR!

o _o
/######################
|###############10/1­0###
\######################

_______________________
|______________________|h_ __
|10/10 _________________||=|##L_
|________________.====._||_|__._]
`(_)(_)`__________ `(_)(_)"""="=(_)

@all: Thanks!

@juha686: Please describe exactly what you have typed in.
Don't press Ctrl-Z (otherwise phun will crash)

@juha686:
I succeeded to reproduce this error..
And i have found the reason why this won't work...
There is a ALU problem.. The ALU does not recognize the correct input..
Thank you for testing, juha686

Quote[juha686]: "the whole screen starts blinking"
It's already fixed Thank you anyway

Hahaha ^^ It's great! I understand you: That was hard work! Spawned circles (on mouseclick) trigger the buttons... Different matrices are used to store values and digit informations! Nice!

Wow! Great idea! 10/10
128 variables? That's not necessary! Create a simple array with 128 entries and link to the different indices. A1 would be scene.my.screen(0), A2 would be scene.my.screen(1) and so on...

The PCP Logo is not located in the "textures" folder. I can't see it. I only see the logo in the preview.. Nice! This should be our official logo ^^

Bugs:
-The keyboard is destroyed. Shift, enter and backspace keys are broken.
-The text covers the other text which was generated by the computer

I'll try to help you tomorrow!
There are too little differences between V2 and V3. I propose to decrease the version number.

That's cool!

@professionalphun: I'll do that. I included some floppies, but they currently contain no information. I'll upload ASCII art which will be stored on the floppies...

edit: Floppy 1 and 2 store a ASCII art.
Floppy 3 stores the introduction screen.

@swiss.assault: Your idea is great! I found the bug and corrected the scene.
Here's the link.
I disabled the rating function because the concept was invented by you.

I don't know how to eliminate the circles depending on the sim-time, but I know a way to eliminate the circles after they collide X times with another object.

Very good scene! 10/10 Make sure that the textures are all located in the "Phun/textures" folder to avoid texture errors.

fadeTime := 0.5 is correct. Your laser is very fast and thats the reason why you don't see a difference between 1.5 and 0.5. Try 0.05 and you'll see what I mean..

@xplane80: Good idea! I already know this calculator (scene response!) and it's operating mode. Let's design a new computer with global variables in the future. This is easier for our developing progress while it's harder to understand how it works (you can't see the sourcecode in phun)