Hyperion Entertainment Message Boards

@ChrisH I don't have exactly the same problem, but I believe the cause is the same: After my Sam440 finishes booting OS4.1u3, my KVM's mouse & keyboard simply don't work (or I only get Y-axis movement of mouse). I had similar (or possibly not so bad) problems with all earlier versions of OS4.1 t...

I'm also not sure what the -mppc option is supposed to be doing as ppc code should be the default for ppc-amigaos-as...

Finetuning for concrete CPUs.
https://sourceware.org/binutils/docs/as ... dOpts.html
Anyway, no idea why an SDK update would break / influence the cross-compiler setup.

For the most common "I want a pretty simple semi-transparent blit over other stuff" IGraphics->CompositeTags(COMPOSITE_Src_Over_Dest,...); is probably what you're looking for.

Ah, didn't know that it was open-source, thanks for that info.
However, I don't have free time left to fix every bug I run into on my own I'll leave that to the people already involved with it.

Fixed this, at least for R200 (cannot test others). Up to 2k x 2k now works with or without mip-mapping, no matter if 16/32 bit context, etc.
Programmers: don't forget to remove your workarounds / artificial limitations to below 2k x 2k when the driver gets updated

@Crisot I've seen in last Warp3D update there is a support for 16 bits ZBuffering with R200 driver. But I don't know how to enable it. I tryed with W3D_Hint(), but the precision is allways the same. Looks like I allways have 32 bits ZBuffer, but I'd like to try 16 bits to gain some speed where excel...

Fixed it. Also fixed some problems with the secondary color and interleaved arrays.
Programmers: take care to remove any workarounds in your code regarding this when the updated driver gets released

Fixed it. Will be in the next R200 update.

Hi, just stepped into two problems regarding clib2 and some wchar functions. Most likely there's more but so far I only tried to use those: In clib2/include/wchar.h: The prototype for vswprintf is wrong, the destination pointer is a simple char* while it should be a wchar_t*. It should be int vswpri...

I think what Karlos meant is that W3D_Query() can't tell you what the max texture dimensions are per texture-format. The destfmt parameter is for the render target, and not the texture's format. So, you can't ask "what's the max width for a 16-bit texture?" Indeed, that's absolutely true....