»

[takemehomegrandma]

This could have been an interesting thread, but then ikir and MikeB started to babble about trolls, flamewars, etc, pushing the focus away from the real issue and destroying the positive atmosphere. Pity! :-x

MOOODERAAATORS!!! ;-) :-P :-D

[Rogue]

Is this pure PPC/OS4 Warp3D?

Yes.

Presumably WOS Warp3D is a lot harder to get to run, because of the way OS4 is designed.

What makes you think so? I mean, not that it would be nesessary in this case anyway, but why do you think that getting WOS Warp3D would be so hard?

[Rogue]

on this screen shot is there hardware acceleration or software..

It's hardware.

[takemehomegrandma]

@ Rogue

I second bloodlines question: Are you guys doing the work yourselves on this one?

[Rogue]

Are you guys doing the work yourselves, or are there other devs working on Warp3D?

We're going to do that ourselves. And I'm really looking forward to it ;-)

Pixel Shaders are part of the OpenGL2.0 spec right?

Yes, although extensions already bring these to 1.x. The ARB pixel and vertex shader extensions are quite commonly accepted, although you need DX9-class hardware for that. The OpenGL 2.0 specs define their own high-level shader language, which is a definite step forward from the assembly-level register combiner langauges seen in DX8 and the ARB extensions (or ATI's extensions for the matter).

Problem is, OpenGL 2.0's HLSL is quite C-like and versatile, so a lot of cards will not be able to compile these shaders properly - they may even contain loops and subroutine calls that everything except the P-10 cannot do at the moment, at least not in the scope that the HLSL defines (DX9 also defines loops and subroutine calls, but as usual imposes hardware/vendor-Specific restrictions on them. A DX 9.1 release for the next-gen graphics cards is sure to happen).

[downix]

@Rogue

Good work to all involved.

[mikeymike]

What do pixel shaders actually do?

[Rogue]

But Warp3D does provide software routines to use if the Hardware isn't present right?

Stephane Guillard wrote a software-renderer for Warp3D. For the most part, however, a generic software renderer is slower than a specialized one. For example, you could theoretically run GLQuake on it (I tried running WipeoutXL on it once, and it was *almost* playable), but the original software Quake will be faster in every respect.

AROS has an OpenGL library, but it is totally software with no hardware aceleration at the moment.

Based on Mesa, I guess?

I thought that the current Warp3D drivers in OS4 might be at this level too, at the moment.

No, they're fully hardware accelerated (Voodoo 3 ATM, but I'm itching to start the radeon driver ;-) ). The drivers themselves use little to no system interaction (only reading a few ENV variables at startup to account for different settings etc), so the only real change required was to adapt to the new OS 4 library model.

This is a rather straight port, but in the near future I'd like to take advantage of a few points that the new library system provides. Unfortunately, this was a weekend project and priorities are elsewhere :-)

[downix]

@Mikeymike

It is a graphics function that calculates out effects on a per-pixel basis as opposed to per-vertex. It is great for creating ambience, giving materials and surfaces that little something to make it that much more realistic. So, using pixel shaders, you can give that 3D rendered face a bunch of zits or some stubble that looks more realistic than before.

[Rogue]

What do pixel shaders actually do?

They re-invent software rendering into the 3D graphics card :-)

Honestly, a pixel shader is a small program in a specialized language that is executed for every pixel in the primitive that the graphics chip wants to output. This way, you can control the appearance of your output at a very low level.

Doom 3 uses these for example to calculate per-pixel lightning based on normal maps. The result looks quite spectacular. Other uses include fresnal reflection on water (where you can see the sky being mirrored in the distance but can see through the surface right before you), dirty-mirrors effects, and much more.

[TheJackal]

Re: Picture of Warp3D Running Natively on AmigaOne
Poster: mikeymike Date: 2003/11/11 17:47:12

What do pixel shaders actually do?

Simply put you have vertex and pixel shaders.

[edit] Damn Roge whipped me to it! :-)[/edit]

both are "programs" which are executed for every vertex or pixel fragment that is processed by the card.

for instance your vertex shade would take in the vertex x,y,z colour etc of the vertex. And a transformation matrix. The code in the vertex shader would then apply the matrix to the vert, and write out the result to specified registers/vars.

Similar thing for pixel shaders, but you get texels from textures and so on instead of x,y,z... values.

This gives programmers freedom (within reason) to do stuff as they want compared to the old fixed function type pipelines.

I hope that made sense, if so Yay! for me! :-D

[Rogue]

@downix:

Good work to all involved.

Thanks ;-)

[sdesros]

Great work Hyperion Little time ago most of trolls say that OS4 won't never run Warp3D.

Umm... I don't think Warp3D was ever in question. I think people asked if OS4 will support PowerUP and WarpOS software.

And now the race is on... let's see which OS gets Warp3D support for Radeon first. :-P

P.S.
Good work.

[redrumloa]

Good work to all involved.

Agreed. I'm curious to see the finished product in action.

[downix]

@TheJackal

Hey, I beat ya both to it, so 8P