I dont see any difference. It is the same program after all.
That makes no sense. not everything is helped by gpu acceleration, with modern cpus some tasks are quicker to finish locally than sending the data to the gpu.
I donât see how or why the gpu would magically make more polygons, if it did that I would consider it extremely broken since it is not rendering what the programm asked it too.
Itâs nice to see that 3D opengl applications run, but donât expect 3D drivers to run them âbetterâ neccesarily, for glteapot the limit is clearly âit does what the programm asked and finished within 1s/60â anything above that is irrelevant as far as spinning a teapot is concerned.
LLVMpipe is clearly sufficient for this use ase, as is the driver beeing shown here.
For simple scenes, the overhead of trasferring instructions across a PCI type bus, waiting for a result, then copying the framebuffer back to integrated GPU is not exactly free. For simple scenes, doing software rendering may actually be faster.
Complex scenes are a different story.
Could be the old version of mesa just rendered poorly, butvthe light and surface looks better
The teapot is often modeled using parametric surfaces, so their tesselation into renderable fragments may very well depend on the gpu and the gl.
It is an hardcoded set of xyz coordinates which you can find here: https://git.haiku-os.org/haiku/tree/src/apps/glteapot/GLTeapot.rdef
I see. Usually the teapot is used to showcase the rendering of parametrics.
Can you test Godot Engine?
Some progress on RadeonGfx:
-
Fixed some small memory management bug in libdrm2 found when implementing Wine Vulkan support.
-
Added ability to change GPU frequency at runtime.
-
Added ability to register areas as GTT buffers with Vulkan VkImportMemoryHostPointerInfoEXT extension. Area must be created with locked physical memory (B_FULL_LOCK). Used in my WSI add-on.
-
Added ability to allocate VMIDs, so multiple processes that use GPU work faster and correctly. VMID is address space identifier that is used when executing GFX ring commands. Multiple address spaces can be used in parallel. Radeon GPU supports up to 15 VMIDs.
-
Added some stub PCI bus information in libdrm2 to test Vulkan GPU enumeration.
-
Implemented condition variable for SA Domains used in (4) to wait for free VMIDs.
If someone implements Vulkan HW for Haiku, would there need to be individual drivers for each Vulkan-supported graphics card, or is there same Vulkan API that would work for all newer Vulkan cards without needing to write extra drivers?
Nice, but that âcrysis demoâ icon looks intresting, have you been able to run it @X512 ?
WOW!!! it is great!!
wow, when can we get acess ?
@3deyes made game patches.
to the driver ?? or a complete image of OS with all needed patches ?
You have plans to release the RadeonGfx soon for test? it is looking very good.
@X512 I tested the vulkan demos with mesa lavapipe package available on haikudeport,they look good, is there a possibility to try zink on top of vulkan or is it still not working?
Is the zink library on haikudeport and I couldnât find it?
I would like to test the performance of blender, currently through llvm softpipe mesa opengl it is totally unusable, too slow, while the vulkan demos seem quite performing