@Rob

>>rename Wazp3D.library-ppc to Wasp3D.library & copy it to Libs
>>An Amiga novice could easily get stung by that typo.

Am I the only one thinking about a joke there?

Last edited by TheDaddy on 25-May-2012 at 11:20 AM.

_________________
www.loriano.pwp.blueyonder.co.uk

@NutsAboutAmiga

To add, such a simply parts like one or two libraries, one or two binaries, have no needs to have any kind of installer. Installers need for big fat projects with a lot of files, but not when you just need to copy one single library and one single prefs.

In end, users will ask to make installers for installers, to install installers which will install for them installers, just to have copy of one library in end.

_________________
aos4/aros/mos projects & articles

If you like any amiga related work i do, feel free to donate

@kas1e

lol. +1!

@amigasociety

I do hope you get this fixed because it does not work here either,,,, and
I have been around a long time.

Quote:

In dummy speak, explain how I check this rwed since I don't know how yet.

1.
Using Filer, 1 left click on the file, then right click and in the popup menu
use File > Information (up at the top). That should pop open a window and you
can see which bits are set. If you change any bits be sure to click the Save
button (or Cancel).

Where it says Version just click the question mark for that info.

2.
Double click the System partition.
Right click on the Workbench top bar while the System window is active.
Select Window - Show - All files.
Double click on the now visible Libs drawer.
Find the file your looking for then right click on it and select Information.

@wawa

I hate that kind of setup. The programmer has to give each e version a different name and the user has to rename their version. To reiterate an earlier point, this can be avoided at both ends by organising the file in their own directories. Like so:

68020 (dir)
....Libs (dir)
........ example.library
68040 (dir)
....Libs (dir)
........example.library

That way the user just has to go to their matching directory and drag the icon to the Workbench, Mac OS9 has a good feature where if you dragged a system file onto the System partition it moved it to the proper place. In the past I have thought AmigaOS needs a system like that.

This system also works across different Amiga platforms combined into one archive. As well as keeping different files separate and organised.

@thellier

AmigaDOS scripts are your friend. That's all you need.

For different versions you could do a version check. AmigaOS4 is >=50.

Or just supply a script for each organised like my above example.

In the WinUAE case it looks more complicated as things must be done on the host OS side. As Wazp3d is a software solution what does this provide? Native emulation on host CPU? IIRC WinUAE should also be able to provide host native execution via a hook.

The most important point is, the program works.

The real issue is having to rename 2 files, 3 if you install the prefs. If I can make a spelling mistake just explaining the install, then a user can do the same thing. For even a simple app like this, an installer would be a good thing, but thellier has stated he doesn't know how to make one, so he needs help with that.

In the time ppl have criticized everyone else, a simle install script could have been made instead.

_________________
X1000! Party on
Pure Gold
Hate tends to make you look stupid...

Update all..... I think it is working but rather poorly. Let me explain...

When I launch ScreenBlanker and select the BoingBall, and then click the Test Fullscreen button, the screen goes black.

This time rather that quitting it I let it run on black screen as I received a call and about 2 minutes later, a bouncing ball FINALLY shows on the screen. It is bouncing at the pace of a snail that took some sleeping meds but it did finally show up and a ball rather choppily moves on screen, maybe an inch movement every second or two.

So, how long is it taking your ball to show on screen once the Test Fullscreen button is clicked?

How fluid is your ball movement (did I just say that hehehe).

So it appears it may be working, just at such a slow rate that it takes 2 minutes just for the BoingBall to show on my screen and then it runs just soooooo slowwwww.

So install all this time appeared to work and I followed directions fine from the initial install to then re-installing again and again making sure I followed all your tips.

So yes install seems easy enough but signs are it just was not working yet maybe it is but...

tj

Last edited by amigasociety on 25-May-2012 at 07:48 PM.

@amigasociety

Should show it working in the small window, 1-2 seconds to show in blanker mode & about 3 seconds per bounce cycle. If that blanker works, then the install is correct, speeds not important with that one.

_________________
X1000! Party on
Pure Gold
Hate tends to make you look stupid...

I guess my speeds are just 100 slower than yours

Literally takes 2 minutes from click of my Test Fullscreen button for the black screen to switch to a bouncing ball.

Then the ball moves literally an inch every 2 seconds.

Sounds like your test screen comes up right away and the ball must be moving nicely if it cycles as quick as you say.

Maybe by tonight I will get one full bounce of the ball. grin.

Sounds like it is working though, just not the same as yours for whatever reason.

tj

@amigasociety

I suspect you installed the prefs file & have render mode set to compositing2d, this setting really slows the Boingball blanker down for me. Change render mode to SoftPPC to image & see if it speeds up. If you're not a game player, I would just leave the Wazp3D prefs file un-installed.

_________________
X1000! Party on
Pure Gold
Hate tends to make you look stupid...

@sundown

Thanks for the tip.

Funny thing I change the Compositing 2D to SoftPPC to Image, close the Prefs window, re-open, and it is back to Compositing 2D again. Does not want to store the new setting. After trying multiple times it finally appears to have saved but we will see after next boot.

Strange. Anyway..... Maybe I will wait for real 3D support for X1000 to come. hehehe

So SoftPPC to Image I don't even get the Full Screen Bouncing Ball anymore. Only shows on small screen in Prefs window. Once I click Full Screen, black for good and have been waiting minutes now for something to happen.

Now SoftPPC to Bit seems to be much better. I will try this one on for size.

Just for fun, I made a video of my speed with Compositing 2D so you can see how bad it was.

http://www.youtube.com/watch?v=ESMB-EJybCY

tj

Last edited by amigasociety on 25-May-2012 at 09:36 PM.
Last edited by amigasociety on 25-May-2012 at 09:35 PM.
Last edited by amigasociety on 25-May-2012 at 09:35 PM.
Last edited by amigasociety on 25-May-2012 at 09:33 PM.
Last edited by amigasociety on 25-May-2012 at 09:30 PM.

Ah, SoftPPC Bit does not work right either.

Oh well. Maybe this is just on the BoingBall as you mentioned.

I was just trying to get this Wazp3D installed so I could tinker with some games and some I wanted required this so.

I will tinker some more and see how things go in games that need this.

tj

Last edited by amigasociety on 25-May-2012 at 09:53 PM.

@amigasociety

Just remember that Compoiting2D should be always enabled in wazp3d prefs, or you will have slideshow and everything will be slow. But even with compositing you sometime will have bugs, so play with wazp3d prefs settings (i.e. if some gave didn't works normally with Compositing2D option, then play with all the other options one by one, and found what one are good one).

_________________
aos4/aros/mos projects & articles

If you like any amiga related work i do, feel free to donate

@amigasociety

Yup, I get the same speed with compositing2D set, just delete the prefs, re-boot & try again, that setting screws up blender as well. I did a search for the prefs config, but can't find any, has to save the setting somewhere. You didn't change the name of the prefs file did you? Should just be "Wazp3D"

You can install & play with the prefs settings after you're satisfied its working right.

Last edited by sundown on 25-May-2012 at 10:00 PM.

_________________
X1000! Party on
Pure Gold
Hate tends to make you look stupid...

@sundown

Nope, I left it alone name wise.

I have since left it on Compositing 2D and will just see what happens.

At least I know it is on now.

So, what negative effects will I have by leaving this newer Wazp3D Library in place with the pref on Compositing 2D?

Will I see negative speeds elsewhere?

I don't use Blender.... yet.

If this will make my OS 4 experience poor speed wise elsewhere other than this BoingBall not working, I will go back to what came stock on my X1000.

TJ

@amigasociety

Quote:

Will I see negative speeds elsewhere?

No idea, no one has reported any tests done with the x1000 that I know of, you just need try things & see. Any app that uses miniGL will be affected in some way.

_________________
X1000! Party on
Pure Gold
Hate tends to make you look stupid...

@amigasociety

I think there's some adjustments you can make to the rendering of the blanker itself that should speed it up considerably. Turning off shadows and such.

@all

Just keep in mind that now wazp3d save the current configuration when the 3dprog is closed
Then when the 3d prog is started again then wazp3d
reload his configuration again
This configuration is saved in wazp3d.cfg

so better is
go to boingballblanker drawer
erase wazp3d.cfg
start wazp3d-prefs
set renderer composite2d
Close wazp3d-prefs
start boingball