---

Forum » » Création-Développement » » AmiDARK Engine "news en vrac 2010.09.09"

---

Posté : 11-09-2010 09:05

@Crisot
Imho, all the problems in the Warp3D code (which are closed-source), but not in MiniGL. Dunno what do Rogue (author of Warp3D), but realisation of it suck very much by speed. I trying to talk with him in emails, and in general, he just not in high interest to fix speed problems of warp3d (or he just can't). His answers was "That slow because of p96 bottlneck". He also say, that warp3d for now use something which not should be used, and for now, better use radeon.resoruce for making warp3d works fast (before redeon.resource was not present at all). And , if someone will in interest to works on warp3d, he (rogue) can provide all the info on radeon.resource and so on.

MiniGL for us only utilizing that Warp3D crap, and as i know, MiniGL not add so much overhead (more of it, Hanz (main auhor) even remove some crap (like checking on present/un present active context) from MiniGL, just to make it a bit more faster).

Related to AmiDark, imho, Freddix right that use MiniGL (opengl). Because when mesa will be done (i hope someday), then engine can be easyly recompiled over it. But if he will use Warp3D directly, he will stuck forever on the slow realisation of it (which, can be never changes because of different factors).

We can of course a bit speedup even MiniGL : write functions for accelerated trasformation, lighting and clipping (i.e. do accelerated that, what Warp3D do in software). But that will be only "few fixes", because main problem - Warp3D code.

As rogue say also, that yes, Warp3D can be speeduped at last for 20% for sure, but, he is not in interest, because of blablablab and so on. If we can found anyone brave enough who will in interest to work on warp3d, i can try to contact with Rogue again.

---

Cet article provient de Le site des utilisateurs francophones actuels et futurs d'AmigaOS 4.x
https://amiga-ng.org/viewtopic.php?topic=834&forum=14