Kilinich's Scenes Vanished

[niffirg1]

I was looking and i noticed all of Kilinich's Scenes are gone! What Happen????

[standardtoaster]

He said that a lot of his scenes no longer worked with Algodoo. :C Because of that he made a stupid and foolish choice IMO. He could've just said that some of his scenes didn't work properly.

[Paradigm 29]

Kilinich will definitely be missed if he doesn't decide to come back soon. It is a shame that he deleted his scenes from Phunbox. Some of the best scenes, months of work, all gone. It is a sad day for Phun to see this happen

[Rhett97]

Dammit.. is he gonna rebuild all his scenes?

[niffirg1]

I sure hope so Rhett i sure hope so. Man his scenes were and are great.

[Wild Bill]

That is very sad!!!!!!! Kinda like Mozart ripping up his sheet music.

I know during testing I had to fix and re-up a few of my scenes. I kept reporting to Emil when an old scene wouldnt work and he fixed it many times on the next update, but it wasnt always possible.

It seemed really important to me that everyones old scenes worked with Algodoo so all their work wasnt wasted. I still havent gone thru all my old scenes from v 4.22 to make them work with 5.28, I was waiting for Algodoo to be released to make them work with it.

I would like to see a feature that included 5.28 with Algodoo so that at scene start it would recognize the scene version and play it in the same version it was created in.

[KarateBrot]

woot woot wooooooot? o_O

[Kilinich]

Stop sobbing, I just don't like idea of joined phunbox/doobox.
Too many things stops working - all with k-probes, softwheels, everyting with springs, hinges now more stretchy... and that's annoying. I remember beta 5 out with less compatibility problems.

I'll check and update everything to Algodoo version.
If admins decide to separate phunbox, I can undelete scenes in any time.

[Torpedo]

You know i agree with that, there should be two seperate boxes for each peice of software if there are compatability issues.

[Wild Bill]

The scenes are marked with a yellow outer border for algodoo and grey for phun so you can tell them apart.

I wouldnt want to check two boxes each time I visit.

[Torpedo]

Whats the part with the issue anyway? I've found a few minor bugs in scenes running back or forward compatability, but nothing too major yet. Infact earlier i found one of mine i made in algodoo ran better in phun, strangely enough lol.

[Paradigm 29]

Whats the part with the issue anyway? I've found a few minor bugs in scenes running back or forward compatability, but nothing too major yet. Infact earlier i found one of mine i made in algodoo ran better in phun, strangely enough lol.

After seeing that kilinich deleted his scenes I ran the UAZ scene of his. I don't know how to put this other than that it's completely f***ed up. While most people notice nothing, Kilinich's scenes have huge amounts of thyme and the backward compatibility of Algodoo is shaky at best when it comes to thyme.

[Kilinich]

After seeing that kilinich deleted his scenes I ran the UAZ scene of his. I don't know how to put this other than that it's completely f***ed up. While most people notice nothing, Kilinich's scenes have huge amounts of thyme and the backward compatibility of Algodoo is shaky at best when it comes to thyme.

Well, in general, there is not much problems:
1) springs values reset (from Algodoo to phun)
2) e.normal reverse
3) hinges stretch (barely noticeable)
but I've use this features hard in almost every of my scenes so no point to keep it in doobox (which is primary for Algodoo).

[standardtoaster]

You could have just kept the scenes that did work. Like the circle gear creator. Besides, without that scene my circle rack creator has almost no purpose. :C

[Kilinich]

You could have just kept the scenes that did work. Like the circle gear creator. Besides, without that scene my circle rack creator has almost no purpose. :C

I'll check and put it all back, ok

[Rrobba]

So sad...why'd he do it?

[Dakta]

Ker bump...


JUst maybe to get some new action going with your stuff, I am going to be working on my Transmissions, and have posted the old topic here as well. I hope things can work out!


(Please remember that a lot of us hardcore Phunners have kept a copy of beta 5 just for this reason. Please don't assume that we can't use them anymore! There's a lot of great code in those that can be modded to work in Algodoo. Speaking of which, can e.angvel finally be read as a variable?)

[guyboy]

Omg the e.normal problem is extremely easy to fix just mass replace some text in your files... Someone might make software that does it. It may even be possible to make it work in phun and algodoo equally.
For the physics changes, i think you can change them back with a thyme command (?)

[RA2lover]

i've got an idea for that - the same method i used for the anti-algodoo device!

instead of one if-statement to do nothing, and other to exit, you could use it as a method of distinguishing algodoo from phun - and change the normal multiplication that way!

here comes the code

Code: Select all

(e)=>{{math.tobool(true)}?{algodoo's e.normal calculation}:{phun's e.normal calculation}}

[niffirg1]

So sad...why'd he do it?

Umm have read this topic?