Page 1 of 1

.phi as multiple-scene distributive

PostPosted: Wed Nov 03, 2010 8:02 pm
by Kilinich
.phi is good way to distribute multi-level game (with auto-next-scene load) but only one thing I feel it need - scene auto-run.

It will be perfect if:
after unzip, check \scenes\autorun.phz is inside .phi and if it valid, load scene.

Re: .phi as multiple-scene distributive

PostPosted: Wed Nov 03, 2010 8:36 pm
by tatt61880
Kilinich wrote:.phi is good way to distribute multi-level game (with auto-next-scene load) but only one thing I feel it need - scene auto-run.

It will be perfect if:
after unzip, check \scenes\autorun.phz is inside .phi and if it valid, load scene.

Support.

IMHO, phi-files should be handled without unzipping if the phi is used as a container for scenes.
And, the phi should be made by Algodoo.

NOTE: I used the phrase "the phi" as a container for scenes. The file type (.phi) can be used for installer for the other files (e.g.translation files), though.

Re: .phi as multiple-scene distributive

PostPosted: Wed Nov 03, 2010 10:20 pm
by electronicboy
support.
Would be useful.

@tatt: i agree, algodoo should have a built in or atleast bundled.
Also, algodoo should give the user the choice to install the phi file (only scene's) or to temporaly have a seperate area to load the contained scene files.

Re: .phi as multiple-scene distributive

PostPosted: Wed Nov 03, 2010 11:17 pm
by tatt61880
Game scenes in one phi-file will have use same textures.

Which is better?
[A] Texture-files are contained by each scene (phz-file) in phi-file.
[B] Texture-files are contained by phi file.

I thought [B] is better.

Re: .phi as multiple-scene distributive

PostPosted: Mon Nov 29, 2010 11:32 am
by Kutis 96
Good idea kilinich, absolute support. They could also add any tool to make .phi flies, becuz i dunno how... ill try to make a prog in VB later 8-)

Re: .phi as multiple-scene distributive

PostPosted: Tue Nov 30, 2010 3:17 pm
by RA2lover
a .phi file is just a .zip file which unpacks itself on the algodoo install folder when run by algodoo.

Re: .phi as multiple-scene distributive

PostPosted: Wed Dec 01, 2010 9:04 pm
by Rrobba
Support.

Re: .phi as multiple-scene distributive

PostPosted: Wed Jul 20, 2011 12:13 pm
by Ivan
Kilinich wrote:It will be perfect if:
after unzip, check \scenes\autorun.phz is inside .phi and if it valid, load scene.

It would really be perfect.

Re: .phi as multiple-scene distributive

PostPosted: Wed Jul 20, 2011 12:29 pm
by monstertje3
this is all really nice, but how would be the transitions between scenes, sceneload("scene2")?

Re: .phi as multiple-scene distributive

PostPosted: Wed Jul 20, 2011 1:09 pm
by TC42
Bump, and yes the code is scene.loadscene("examplescene")

Re: .phi as multiple-scene distributive

PostPosted: Wed Jul 20, 2011 1:19 pm
by electronicboy
TC42 wrote:Bump, and yes the code is scene.loadscene("examplescene")


that code is correct,

also, would be nice if devs. allowed to make a .PHI from algodoo (as suggested countless times mainly on this thread...)

also, would be nice if there was a way to run from the .PHI (no install) and if .phi files created subdirectories


e,g, scenes/<PHI NAME>/name.phz

Would be nice as it would help keep a users directory clean, but the method of scene.loadscene may have to be changed...

Re: .phi as multiple-scene distributive

PostPosted: Fri Jul 22, 2011 4:02 am
by Someone Else
Here's what I would support, as far as relevance to this thread goes:

Ability to create a PHI from within Algodoo (would allow checksums to be implanted in the PHI, for the same reason as checksums in the PHZs),

Ability to autorun a scene, if autorun.phz is present,

Option to install the PHI to a temp directory, which would be auto-deleted upon closing Algodoo,

Placing textures in the PHZs into the PHI instead of the individual PHZ, because the textures in the PHZs would probably overlap and it would reduce filesize,

[somewhat off-topic: put textures into the PHZ upon saving it- textures in scenes downloaded and run in 1.9.7 simply don't appear for me],

When creating a PHI via Algodoo, the default install directory would be in Algodoo/Scenes/example if all the files are PHZs and/or PHNs, otherwise, the default install folder would be Algodoo/example.

By this, I mean you would select some files and Algodoo asks what folder to install to. If all the files are Algodoo Scene Packages and Algodoo Scene Files, the directory would be Algodoo/Scenes/[whatever the name of the PHI is], so the PHI would include a Scenes folder, containing an Example folder, containing the scenes. You could, of course, change it to whatever you want.

If the prospective PHI contains any files other than Scene Files/Packages, the default directory as described above would be Algodoo/Example.

The simple mode for creating a PHI would allow you to set it up so the selected files install to the same directory. The advanced mode would allow you to install files to several different directories.

Re: .phi as multiple-scene distributive

PostPosted: Fri Jul 22, 2011 4:59 am
by TC42
Yeah, I agree that the whole Phi interface needs to be improved... there is great potential in it, but devs keep leaving it in the dark. I think that, like SE said, it should be simple to create a PHI, and I would add that there should be an option in the controller menu that will load the next scene when a button is pressed, or a collision occurs, for those who are new to algodoo and don't know about loadscene().

Re: .phi as multiple-scene distributive

PostPosted: Fri Jul 22, 2011 11:11 am
by Rrobba
Should be added ASAP. I could really use this for a current project.