Login
Username:

Password:

Remember me



Lost Password?

Register now!

Sections

Who's Online
138 user(s) are online (87 user(s) are browsing Forums)

Members: 1
Guests: 137

FlynnTheAvatar, more...

Headlines

Forum Index


Board index » All Posts (Daytona675x)




Re: Tower 57, pixel art Chaos Engine homage, coming to OS4
Not too shy to talk
Not too shy to talk


@orgin
Right now it's about 10k short, but it's still 7 days to go. Yesterday's amount of pledges summed up to about 1500 according to Kicktraq stats, so it actually doesn't look bad at all
Of course only if yesterday's pledge level is being kept... therefore: continue to pledge

Go to top


Re: Warp3D and ARGB textures
Not too shy to talk
Not too shy to talk


@BSZili
Okay, fixed that but did not test anything. Please check your mail.

Go to top


Re: Warp3D and ARGB textures
Not too shy to talk
Not too shy to talk


GetTexFmtInfo?
Looks like this one has never been updated to return "okay" if you ask for the compressed formats (it also doesn't return okay for some other formats which are actually supported through internal conversion). Fixing However, texture creation should work nevertheless.

Go to top


Re: Warp3D and ARGB textures
Not too shy to talk
Not too shy to talk


@BSzili
Warp3D knows three compressed texture formats, namely:
W3D_COMPRESSED_R5G6B5, W3D_A4_COMPRESSED_R5G6B5, W3D_COMPRESSED_A8R5G6B5.

At least on the R200 (I'm only speeking for that one) those directly corespond to:
DXT1, DXT3, DXT5

And as far as I can see those pass right through (of course, that was the idea ).

Some notes (that shouldn't come as a surprise but anyway):
Make sure that you have automatic mipmap generation disabled since otherwise AllocTexObj will fail.
Also note that UpdateTexSubImage will fail on textures with that format.

Did I try it? No

Go to top


Re: Wings Battlefield
Not too shy to talk
Not too shy to talk


@ChrisH
The Compositing version is only meant for RadeonHD 4xxx, 5xxx, 6xxx.
Quote from the manual, page 25
Quote:
AOS4 with R200 Compositing
Don’t run the game! Use the Warp3D version instead! There
are quite some bugs with Compositing on such systems that
prevent the game from running correctly. However Warp3D
is the better choice on such systems anyway.


@SinanSam460
No, there won't be download versions.

@Nuder_Try
Thanks

@sicky
@328gts
Thanks
I will consider adding WAN support if it turns out to be worth the trouble (= if the game sells well in Amiga terms ).
WAN support requires quite some additional work compared to LAN support. For example a dedicated web server has to be implemented to manage sessions and for "negotiation" between session-starters and session-joiners. The UI needs to reflect that, of course. Additional code has to be added to compensate for lags. Testing all this isn't fun neither.
All in all: we'll see. Right now it looks quite promising regarding the game's success, so chances for WAN support grow


Go to top


Re: Wings Battlefield
Not too shy to talk
Not too shy to talk


@ChrisH
The Compositing version is only meant for RadeonHD 4xxx, 5xxx, 6xxx.
Quote from the manual, page 25
Quote:
AOS4 with R200 Compositing
Don’t run the game! Use the Warp3D version instead! There
are quite some bugs with Compositing on such systems that
prevent the game from running correctly. However Warp3D
is the better choice on such systems anyway.

Go to top


Re: Hello!
Not too shy to talk
Not too shy to talk


Thanks guys

Go to top


Re: Battle Squadron for AmigaOS 4.X
Not too shy to talk
Not too shy to talk


Actually it was no crash-log, it was the content of the debug-buffer - but there was nothing interesting in it

Go to top


Re: Battle Squadron for AmigaOS 4.X
Not too shy to talk
Not too shy to talk


@pseudaxos
Weird stuff with your freezes. Especially weird that they are completely gone now.
However, if that's happening again then please use

C:DumpDebugBuffer >RAM:freezeinfo.txt

after rebooting and p.m. or mail me the resulting freezeinfo.txt file. Maybe it contains something useful.
So far you're the only one I know of with such an issue and it seems to be specific to your setup but I'm pro enough to know that this doesn't have to mean that the game's code isn't faulty somewhere

Go to top


Re: Battle Squadron for AmigaOS 4.X
Not too shy to talk
Not too shy to talk


@pseudaxos
You should be served by now
To others with the same problem:

That black-screen issue happens because the HD 7xxx apparently doesn't directly support the Motorola-byte-order 16bit RGB565 bitmap format which Battle Squadron uses to draw the playfield.
Since the AOS4 driver lacks a "compatibility workaround" (= convert it to a Intel-byte-order bitmap internally and use that) this task is now done by BS itself.
Actually the new version contains two render paths now, because on HD 4xxx and 5xxx it's the other way around: there the Intel-byte-order variant doesn't work. The driver author promised to fix the latter soon though.

Alas the original Battle Squadron doesn't feature an auto-update mechanism. My plan is to release a special updater on os4depot soon. If you can't wait for that then please simply send me a mail to battlesquadron at goldencode dot de and attach the original AOS4 executable inside an LHA or ZIP or whatever. I'll send you the fresh version then.
Please don't use the cherry-darling mail address for this! Battle Squadron is no Cherry-Darling game! Instead mail me directly ( battlesquadron at goldencode dot de ).

Cheers,
Daniel


Edited by Daytona675x on 2015/6/14 10:51:12
Go to top


Hello!
Not too shy to talk
Not too shy to talk


Hi,

this is Daniel, 37, code-basher from Germany, main coder of the dev team Cherry-Darling.
Amigan since the old days, but with a huge pause from around 2000 to 2010 or so.
After my return I'm now primarily focusing on writing games for AOS4, MorphOS and AROS. I'm also part of the Amiga Future's translation team.

Cheers,
Daniel

Go to top



TopTop
« 1 ... 20 21 22 (23)




Powered by XOOPS 2.0 © 2001-2023 The XOOPS Project