Hyperion Entertainment Message Boards

My expectation is that 2K x 2K 32 bit textures on 32 bit render targets while OK now will probably fail if MIP Mapping is turned on. They need about 1.5x the memory again and that's going to end up as a 2K x 3K request in 53.11.

@Daytona Forgive me, maybe I'm a tad too harsh indeed. It's just that I'm pretty tired about the fact that almost every time I want to use a W3D or Compositing functionality it turns out that it's broken, at least on some systems. I suppose you know about all the bugs I reported so far (more to come...

That's what I meant when I said it wasn't "context" aware. I'd I had meant W3D_Context, I would have written W3D_Context. Nevertheless, most W3D_Query() implementations look only at dstfmt (and even then, usually only care if its RGB or CLUT) and return a static lookup value for the querie...

So, let's see where we are. Warp3D's allocator isn't actually broken per se, it's the limitation of the RTG system it sits on that causes the problem. You may disagree, but this is indeed the case. If a function existed that allowed you to basically AllocVec() VRAM fixed in place, the current hacky ...

Since the underlying problem is unlikely to be fixed any time soon and the W3D_Q_MAXTEXWIDTH/HEIGHT functions aren't context aware beyond what is potentially possible on 8-bit (deprecated) or RGB render targets, I propose the following: 1) Cause W3D_AllocTexObject() to fail when attempting to reserv...

@Daytona I'm not sure I appreciate your tone. I didn't write the allocator, I maintain it. I also fixed a significant number bugs and fragmentation issues that plagued lower end cards. The speculation that the allocator was unable to satisfy the request was ultimately correct, even if it wasn't a fr...

Indeed, on a 16 bit display it fails and on a 32 bit display it doesn't. So, what's the problem? Is your alloc-call failing on a 16bit screen because of that height > 4096 your calculations end up with? Is there a width/height limit on p96AllocBitmap you run into? Yes. As I suggested somewhere earl...

Hi, The height is being calculated on the basis of the linear size that was requested and a maximum allowed width of 2048. If the allocated bitmap is 32 bits deep then you are correct in asserting that it should be only ~2048 (plus alignment and any other required slop) tall. However, you cannot ass...

Can you please report the full version of all Warp3D | Picasso96 components in your installation and the serial / debugbuffer output obtained during the crash?

As the same driver works elsewhere and I don't have a comparable system to test on, there isn't a lot to go on here.

Early indications are that 53.11 fixes a similar issue reported here:

http://www.amigans.net/modules/xforum/v ... &start=620