Hello
I have just uploaded those packages to Aminet that should appears tomorrow

Microbe3D.library, demos and SDK release on Aminet tomorrow
=====================================================
What is Microbe3D ?
Microbe3D is a layer above Warp3D: with Microbe3D programming in 3D has never been so easy
Microbe3D is a small engine that displays directly Wavefront .OBJ 3D files.
MICROBE3D means "MICRo. OBj Engine for warp3D"
http://www.youtube.com/watch?v=2OC9dQoTXWs

Now with the SDK and Microbe3D.library you can start to develop your own 3D programs with ease

Package include 8 simple examples + sources
From simple to more complicated:
demo-simpler: Simple turning Amiga-Logo but with a cube mapping (reflection) effect
demo-window: The same but using an user window
demo-clock: Clock that use Instances (axis)
demo-harm: Articulated robot-harm using hierarchical Instances (axis) with Material gold affected to two Instances
demo-map: Creating a simple 3D map
demo-boing: Creating an "hand maded" new-look boing ball with a custom Material as background
demo-map-heli: Creating a 2D map + object + movement
demo-view: A complete 3D-Object Viewer using all the Microbe3D functions from menus and keyboard keys


Also included: fonctions documentation in french & english, screen grabs, various 3D objects, SDK & include
Microbe3D also works with WaZp3D


Wazp3D.library 54 release on Aminet tomorrow
========================================
Wazp3D is a library compatible with Warp3D for people without 3D drivers

Version 54 :
WARNING: v54 has been reported to be buggy with Hurrican...
o Now also bufferize DrawTriFan/DrawTriStrip/DrawLineStrip/DrawLineLoop/DrawTriangleV/DrawTriFanV/DrawTriStripV/DrawArray/DrawElements
so badly (typically old OpenGL demos) written apps that call those draw functions for few triangles are faster now
So now ALL 12 drawing operations are bufferized and converted to W3D_PRIMITIVE_TRIANGLES/LINES/POINTS
o You can define global default settings in Prefs:Env-Archive/Wazp3D.cfg (be carefull)
o Option "Renderer:Hard" + "Do Mipmaps" works now (WinUAE & Aros)
o Bug fix about scissor (Frogatto)
o Bug fix about p96LockBitMap causing freeze for renderer:Compositing2D
o Faster W3D_UpdateTexImage for renderer:Compositing2D for OS4 (Mame,etc...)
o Frogatto & Mame config files for renderer:Compositing2D
COPY Wazp3D.cfg-frogatto TO frogatto/Wazp3D.cfg


StormMesa2010 2.5b beta release on Aminet tomorrow
===============================================
StormMesa2010 is a recompiled version of original StormMesa with some bug fixes
Using StormMesa2010 may allow some old 68k programs to works on 68k+Warp3D machines or PPC+Warp3D machines or WinUAE+Wazp3D machines

This package only release the latest sources and binary from the 14 september 2012

New in v2.5: if LibBase in A6 is lost then try to find it again with GetTaskLibBase();
New in v2.4: StormMesa2010-Prefs is now OS-friendly
New in v2.3: Mipmapping is fixed (was crashing in Cube). Default setting is LOCKMODE2 + VERYFAST so faster
New in v2.2: Option "Use DrawArrray"


Alain Thellier - Wazp3D Author

@thellier

thank you very much

i will test it tomorrow and include all three in the next version of my distribution

I would like to help you with Stormmesa where possible because I had the idea to update it to MESA 7.5 or 9.0. Would that be very much?

@OlafS25

weve been looking into it few years ago together with bernd and alain, and neither of us had skill, motivation and time altogether. ive been probably the one who pushed most being the biggest noob around. however, today having aros mesa avaliable for 68k i see no point.

id rather prefer aros mesa being fixed to run actually on 68k. while i guess aros mesa is broken altogether on aros v1, but would have to check myself. anybody x86 can confirm?

Last edited by wawa on 19-Apr-2013 at 02:07 PM.

@thellier

btw thanks alain, long time i tried cube on my a4k ;D

@wawa

"mesa being fixed"

nice wish, the problem is who does it. Jason has no time and it is no priority or of any interest to him

And even if it would be slow propably. Stormmesa+Wazp3D is fast like hell now (at least on my test configuration).

Last edited by OlafS25 on 19-Apr-2013 at 02:11 PM.

@thellier

Does the new Wazp3D need any special setting for Aquaria ?

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

@wawa

btw I got the sources for the zlib and have given it to Wanderer. There will be a new version soon hopefully.

@OlafS25

Quote:

"mesa being fixed" nice wish, the problem is who does it. Jason has no time and it is no priority or of any interest to him

the one who fixes mesa for the whole v1 i guess. maybe deadwood.
and do you really think fixing a ready implementation to work again is a harder task than porting mesa all from the scratch? remember the new port will have to be debugged anyway and it would be 68k platform dependant, so even hader to find a maintainer. also the initial result would hardly render as much as aros mesa does already on 68k, i guess there are some minor pointer format issues or so.
i can tell you that ive looked at mesa sources up to 7 and a lot has changed, even in the hierarchy. it wouldnt be just updating some glue files.

Quote:

And even if it would be slow propably. Stormmesa+Wazp3D is fast like hell now (at least on my test configuration).

hard to tell before we have it available for testing. if up to date aros mesa is slow, then a new 68k port would be slow as well. why should it be faster. its the new features that slow it down. and besides storm mesa being warp3d dependant should be potentially slower, as it introduces an artificial bottleneck, that aros mesa does not have. also aros mesa can talk to hardware via gallium.

@thellier

The packages are available now:

http://aminet.net/

@wawa

deadwood perhaps (if we ask him very nicely ). That it "might" be slow is my guess because AROS is up to now not that much optimized for slower hardware. But my test environment is definitely faster now (including the MESA Demos I could test) and Magellan is much faster than Wanderer.

@cgutjahr

thanx

@OlafS25

Hello

I have readed the talk on www.amigacoding.de about that

Certainly the better way would be

1) compile the latest AROS-Mesa with gallium software rendering on 68k

2) then implement software-gallium upside Warp3D : both are low level renderer
of course Warp3D cant do as much things as Gallium (ie shaders) but those parts may be still software implemented (light shaders,vertex shaders) or ignored (pixels shader) or partially implemented (pixels shader that implement classic effect like GL_MODULATE)... (*)

3) make a StormMesa -> AROS-Mesa wrapper (there are both OpenGL implementations so will be mainly doing register to stack calls)
for legacy 68k stormmesa apps

the 2) is MUCH works


>I would like to help you with Stormmesa
I will no more code on StormMesa : this is a too much boring code to explore with hundreds of GL functions :-/
You can ask me for expertise/help but I wont code that myself
I prefer my Microbe3D code it is more funny and nice (only 35 functions).

Alain Thellier

(*) About Gallium: here it is all the driver fonctions
http://dri.freedesktop.org/doxygen/gallium/structpipe__context.html
Typically you use functions like
create_blend_state() to define how you will draw (say transparent)
then call bind_blend_state() for selecting this draw mode
then call draw_arrays() for really drawing triangles (it is almost the same function in Warp3D)

@OlafS25

anyway mesa is a huge project. there is no justification to start it for 68k, except aros version.

@thellier

thanx for answer. I already feared that it might be a huge amount of work (too much). It would be nice to have a common gaming API that is available on all platforms for 3D and perhaps even 2D games and not dependent on the different implementations. In some cases it could be only a wrapper. And your combination of Stormmesa/Wazp3D would be a good candidate for it. For that "full Mesa" is certainly not necessary (would have been nice of course)

Last edited by OlafS25 on 19-Apr-2013 at 02:56 PM.

Frogatto works now well on my X1000

_________________
Amiga600/Vampire2/PrismaMegaMix

@thellier

Quote:

1) compile the latest AROS-Mesa with gallium software rendering on 68k

aros68k mesa is compiled along with some basic examples, actually much like those on storm mesa. currently only softpipe enabled, pci bridges arent working under aros68k as of today.

the examples opened windows last time i looked, gave continous debug output via sashimi like reporting the framerate and the like. there was few elements being actually rendered, some text or raytracing (?) but not much. so its not far from working in software mode imho. of course it will be slow.

@all
Thanks for good feedback

>Does the new Wazp3D need any special setting for Aquaria ?
Dont remenber exactly but Aquaria was working with Wazp3D : I tried it a long time ago...
You can copy Wazp3D.cfg-giddy to Aquaria /Wazp3D.cfg it should works as it is a very safe config (but that use more memory for textures)

Alain

@thellier

No luck with Aquaria.

I use it as a test for Warpz on both my machines.
It worked with the older version of Warpz,

Quote:

thellier wrote: @all Thanks for good feedback >Does the new Wazp3D need any special setting for Aquaria ? Dont remenber exactly but Aquaria was working with Wazp3D : I tried it a long time ago... You can copy Wazp3D.cfg-giddy to Aquaria /Wazp3D.cfg it should works as it is a very safe config (but that use more memory for textures) Alain

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

@wawa

Once aros68k-mesa will works in software mode then a very easy step will be to start a basic Warp3D prog in a window then wrap soft-gallium to (also) call W3D_DrawArray() when it call gallium's DrawArray()

I mean let the aros68k-mesa prog run on his GL-window and draw also in a War/zD window (even as flat faces) ==> It will be a good POC

So we still need
1) make aros68k-mesa works with gallium's soft-pipe

The same apply to an eventual aros-mesa port to os4 ...

Alain

@thellier

Alain, thank you.

I am pleased to report that in Blender on my X1000 the new Wazp3D now shows particles in wireframe animation mode. With previous versions, the particles did not appear. (Of course they have always appeared in final renderings.) This helps during these days while we wait for hardware acceleration.

Last edited by mbrantley on 20-Apr-2013 at 12:41 AM.

_________________