Please June, come quick...
« Reply #15 on: May 04, 2010, 03:35:23 PM »
This forum is now archived!
- Welcome to the archive!
News:
The 3DRad community can be found at classdev.net.
- 3D Rad - Free 3D game maker - Forum >
- General Category >
- 3D Rad - User-created Sample Projects, Scripts, Tutorials >
- Save/Load System V2.0
Author
Topic: Save/Load System V2.0 (Read 5722 times)
System Specs: Win7 - Intel Core Duo 1.80GHz - 2gbRAM - 232gb
Molten Games - moltengames.webs.com
« Reply #16 on: May 22, 2010, 09:21:09 AM »
Hi Chebob69,
I've tested and found your project (SaveLoad2) great.
I thoroughly read the 2 scripts in it and understood most of them.
Could you explain the variables: counter,Max,Opacity,Wait,ArrowState ?
The most mysterious for me is "Wait".
I've tested and found your project (SaveLoad2) great.
I thoroughly read the 2 scripts in it and understood most of them.
Could you explain the variables: counter,Max,Opacity,Wait,ArrowState ?
The most mysterious for me is "Wait".
« Reply #17 on: May 22, 2010, 05:30:49 PM »
Yeah sure. And there's a more recent version here which I don't think many people noticed:
http://www.3drad.com/forum/index.php?topic=4313.0
this version scrapped the menu and focused on the saving/loading algorithm, making it far more efficient as no script is being constantly run.
Counter is used in the save/load script to count to 1 sec before hiding the textprint and setting the screenfade opacity to 0.
Max and Arrowstate are used on the initial menu to determine how many options are present (2 or 3) and which option the arrow is pointing to (respectively). Can't remember why I did it like this, not the neatest way really but n/m.
Opacity controls the slow change of the screenfade which is accomplished by having a black sprite which covers the entire screen.
Wait is used to aid in the control statements in the save/load script. It basically changes the 'state' of the script so only certain bits can be run at certain times.
http://www.3drad.com/forum/index.php?topic=4313.0
this version scrapped the menu and focused on the saving/loading algorithm, making it far more efficient as no script is being constantly run.
Counter is used in the save/load script to count to 1 sec before hiding the textprint and setting the screenfade opacity to 0.
Max and Arrowstate are used on the initial menu to determine how many options are present (2 or 3) and which option the arrow is pointing to (respectively). Can't remember why I did it like this, not the neatest way really but n/m.
Opacity controls the slow change of the screenfade which is accomplished by having a black sprite which covers the entire screen.
Wait is used to aid in the control statements in the save/load script. It basically changes the 'state' of the script so only certain bits can be run at certain times.
« Reply #18 on: May 23, 2010, 05:48:04 AM »
Thank you for explaining the variables,Chebob69. It's just clear.
I've downloaded v3.0 and I'm going to have a look at it.
I've downloaded v3.0 and I'm going to have a look at it.
« Reply #20 on: June 23, 2012, 10:35:21 AM »
You may want to read the last time somebody posted on this was over 2 years ago.
Pages: 1 [2]