|
Jobert on 10/11/10 - 08:31:05
When i first made my game using DirectQB. Everyting went well but the code is too confusing to improve so i decided to make another game with the same library but it went horribly wrong! I get random currupt graphics! I tried everything even when i used DOUBLE integers for the sprite arrays and still freaki'n the same! Can anyone help me? I would be happy if someone can.
Plasma on 10/15/10 - 17:48:26
Send me your code and any files needed and I will take a look at it.
My email is plasma -at- phatcode.net
Cyperium on 01/19/11 - 23:12:29
You need a image width that is divisable by 2 for DQBloadImage to work properly or was it DQBGet? Either way, make your image divisable by 2 and it should work proparly.
In my game Venture I use 12x10 images even though I only need 10x10 since 10x10 becomes corrupted. If you need dqb documentation I have it and can send it to you. Also use the latest version of DirectQB (1.61).
Jobert on 03/09/11 - 00:53:45
I fixed this problem months ago because at the time I posted this is when I was a total idiot about the use of DQBget and DQBput, VARSEG and VARPTR were reversed until I analyzed the documentation very well a month later.
I already made some finished games written with DirectQB with no sprite curruption at all unless I dimension arrays incorrectly. DQBget can store sprites that are not a power of 2 without data curruption in DirectQB 1.71.
Cyperium on 04/11/11 - 08:09:38
Reply to this message
Ok, I didn't realise that, the last version I used on Qb 4.5 was DQB 1.61 (the last official release), good to know that problem was fixed.
I'm doing a DQB wrapper for QB64 which obviously doesn't have any of those limitations either, there are some functions not supported yet though. |
|