Welcome, Guest. Please login or register.

Author Topic: Hardware accelerated 3d for amithlon. What would be the best way?  (Read 5778 times)

Description:

0 Members and 1 Guest are viewing this topic.

Offline woof

  • Jr. Member
  • **
  • Join Date: Feb 2003
  • Posts: 94
    • Show all replies
    • http://uae.is.free.fr
Hello

Wazp3D can use hardware in WinUAE (and also AROS) so certainly something similar can be done in Amithlon
In Wazp3D/WinUAE it works this way
Wazp3D.library implement the 88 functions from original  Warp3D
Those functions call an other (simpler) library i called soft3d.library
soft3d works at low-level: it is something like a 3d driver (23 functions only)

soft3d.library exists as 68k on WinUAE side (It can render as software 68k)
soft3d.dll exists as x86 on PC side (It can render as software x86)
This soft3d.dll can also use the PC opengl32.dll for hardware rendering :-)

a given function in soft3d.library jump to same function in soft3d.dll with the "winuaenative" special calls that allow to call x86 code from WinUAE
(BTW many thanks to quarktex author for this part of the code)

So for Amithlon
1) Find how to do something like the "winuaenative" special calls
2) wrap soft3d x86 to make it use an hardware renderer (OpenGL)

Alain Thellier

Note: having soft3d give the great advantage to have only 23 "winuaenative" special calls from 68k to x86
« Last Edit: September 21, 2011, 09:33:04 AM by woof »
 

Offline woof

  • Jr. Member
  • **
  • Join Date: Feb 2003
  • Posts: 94
    • Show all replies
    • http://uae.is.free.fr
Re: Hardware accelerated 3d for amithlon. What would be the best way?
« Reply #1 on: September 22, 2011, 09:33:47 AM »
Hello

Yesterday I maded some web searchs and I wasnt able to really found out : How can I call "native x86 code" within Amithlon ?
==> this is the most important thing to find out

So ... people that want a native Amithlon driver : just found the necessary docs and compilers to "call "native x86 code"
Especially usefull will be an example source and all the compiler/sdk stuff to rebuild it

@Karlos
About future legacy Warp3D for New Amigas I think the better/simpler  will be to have Wazp3D -> Mesa -> Gallium (like Aros do)
Of course to be efficient it will not be 1/1 calls (each Warp3D call -> an OpenGL call)
but something smarter that call OpenGL only when necessary (ie states changed)

Alain Thellier - WaZp3D Author
 

Offline woof

  • Jr. Member
  • **
  • Join Date: Feb 2003
  • Posts: 94
    • Show all replies
    • http://uae.is.free.fr
Re: Hardware accelerated 3d for amithlon. What would be the best way?
« Reply #2 on: September 22, 2011, 02:22:57 PM »
@laserback
I WROTE Wazp3D (and also use it almost every day) so believe me :
Wazp3D can use hardware in WinUAE since version 48
Wazp3D can use hardware in Aros since latest version 50
(You can use Aros port with Cow3D on Aminet)

BTW i have also quarktex sources : it dont seems to use directx but mostly opengl

@fishy_fiz
That is not enough to have soft3d compiled as x86 : What I need is calling several functions (23 functions in fact) with parameters in this soft3d-x86

What I need is something like "call an x86 function with parameters from inside a 68k program"

Alain Thellier
 

Offline woof

  • Jr. Member
  • **
  • Join Date: Feb 2003
  • Posts: 94
    • Show all replies
    • http://uae.is.free.fr
Re: Hardware accelerated 3d for amithlon. What would be the best way?
« Reply #3 on: September 22, 2011, 03:54:51 PM »
>with wazp3d the textures on blitzquake are not correct
textures ??? certainly you dont have installed Wazp3D correctly
See this image it is Wazp3d with hardware rendering
http://thellier.free.fr/quake-hard2.png

You must also set with Wazp3D-Prefs:
Renderer: hard
AntiAlias Image

Use Filtering


>ahi and povray. Would looking at the sources
just do it and if you find a "call to an x86 function with parameters from inside a 68k program" just let me know...

>v50 of wazp3d is working much better for me now
I told you ;-)

Alain