@ChrisH

I never had problems with Aquaria, but I don't use either X1000 nor Wazp3D.

_________________

@

In the Warpz3D archive are the StormMesa libraries which allow you to run the StormMesa demos from cli by clicking on programs in the exe drawers.
cool .

_________________
Sam460ex : Radeon Rx550 Single slot Video Card : SIL3112 SATA card

OK, I was wrong. I updated to the latest Wazp3D, and it's Prefs program STILL forgets my (global) settings after a reboot. This makes Wazp3D very annoying, because it means I must remember to set "Render=Compositing2D" before using any new 3D app, otherwise it will be extremely slow... or won't even work at all.

Last edited by ChrisH on 02-Sep-2012 at 10:49 AM.

_________________
Author of the PortablE programming language.
It is pitch black. You are likely to be eaten by a grue...

@ChrisH

The prefs work for me. Saving a Wazp3D.cfg in each individual program directory.are you sure you updated the Wazp3d-prefs ? Version is 53.2 ,

From the readme :

It is recommended to use Wazp3D-Prefs BEFORE starting your-3d-program for the first time
you can also use Wazp3D-Prefs when your-3d-program is running (so impossible with screen-blankers)
But as Wazp3D now save/read the Prefs you may encouter problems if the settings were not good
when your-3d-program was first started (typically using a too slow "renderer:soft to bitmap" option)
In this case the better is to delete the file Waz3D.cfg in your-3d-program directory
Then start Wazp3D-Prefs. Set your favorite settings. Close Wazp3D-Prefs. Start your-3d-program
In Wazp3D-Prefs all options with a '+' like "+Renderer:hard" are intended to be setted
BEFORE starting your-3d-program for the first time
If you change such an option during play then it will only have effect next time
(ie when modified Waz3D.cfg will be read )


Quote:

ChrisH wrote: OK, I was wrong. I updated to the latest Wazp3D, and it's Prefs program STILL forgets my (global) settings after a reboot. This makes Wazp3D very annoying, because it means I must remember to set "Render=Compositing2D" before using any new 3D app, otherwise it will be extremely slow... or won't even work at all.

Last edited by Spectre660 on 02-Sep-2012 at 12:24 PM.

_________________
Sam460ex : Radeon Rx550 Single slot Video Card : SIL3112 SATA card

@Spectre660
I am NOT talking about "per program" settings, I am talking about the initial "global" settings of Wazp3D, before any program has been run.

(Note: It seems that those settings maybe aren't really "global", but it would still be damn useful to specify some sensible Wazp3D "defaults" for use after each reboot by any new 3D programs I try.)

Last edited by ChrisH on 02-Sep-2012 at 12:50 PM.

_________________
Author of the PortablE programming language.
It is pitch black. You are likely to be eaten by a grue...

@ChrisH

I think that that is the problem. There seems to be no global settings.
So our perception of what it should do may be wrong.

From the Changelog .
I would think that "local" means individual for each program in this context.


Beta 52.1
o Now automatically write/read Wazp3D-Prefs settings in a local Wazp3D.cfg file

_________________
Sam460ex : Radeon Rx550 Single slot Video Card : SIL3112 SATA card

Place a Wazp3D.cfg file in the same drawer than its prefs program.
Each time you run a 3d program, this config file will be used.

Regards,
Petrol.

@petrol


You just beat me to it. while I was rebooting to try this. .
There is something very consistent in the way Amiga software functons .


Quote:

petrol wrote: Place a Wazp3D.cfg file in the same drawer than its prefs program. Each time you run a 3d program, this config file will be used. Regards, Petrol.

_________________
Sam460ex : Radeon Rx550 Single slot Video Card : SIL3112 SATA card

@Spectre660
>I must remember to set "Render=Compositing2D" before using any new 3D app

1) Just load ANY 3D program that is well configured (ie that have Wazp3D.cfg file in his local directory ) then those settings will be used for "any new 3D app"
(as a new app dont have yet a Wazp3D.cfg So it will just inherit the current settings loaded with the first program....)

2) You can also get a working Wazp3D.cfg somewhere and just copy it to to the "new 3D app" directory before starting it

BTW default is set to "renderer:soft to bitmap" because it is the MORE Warp3D-compatible option (but too slow on a ppc Amiga)


Alain Thellier - Wazp3D Author

@thellier

Thanks for the response. Should be directed at ChrisH who is huffing and puffing .
The way Wazp3D config files work makes a lot of sense and is a good way to enable per programs settings.

Quote:

thellier wrote: @Spectre660 >I must remember to set "Render=Compositing2D" before using any new 3D app 1) Just load ANY 3D program that is well configured (ie that have Wazp3D.cfg file in his local directory ) then those settings will be used for "any new 3D app" (as a new app dont have yet a Wazp3D.cfg So it will just inherit the current settings loaded with the first program....) 2) You can also get a working Wazp3D.cfg somewhere and just copy it to to the "new 3D app" directory before starting it BTW default is set to "renderer:soft to bitmap" because it is the MORE Warp3D-compatible option (but too slow on a ppc Amiga) Alain Thellier - Wazp3D Author

_________________
Sam460ex : Radeon Rx550 Single slot Video Card : SIL3112 SATA card

@thellier Quote:

You can also get a working Wazp3D.cfg somewhere and just copy it to to the "new 3D app" directory before starting it

I am afraid you are missing my point. I don't want to have to go to the trouble of having to remember which 3D apps I have not yet configured, and then go to the trouble of copying settings (or setting it up).

Wazp3D clearly has some initial (aka default) settings it uses when there is no wazp3d.cfg file found. What I want to be able to do is have different defaults (that tend to work for me).

Basically I would like it to work more like how RunInUAE handles game configuration.

Last edited by ChrisH on 03-Sep-2012 at 07:04 PM.
Last edited by ChrisH on 03-Sep-2012 at 07:02 PM.

_________________
Author of the PortablE programming language.
It is pitch black. You are likely to be eaten by a grue...