-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Broken gfx with modern Uzebox kernel #1
Comments
Adding -fno-toplevel-reorder to the CFLAGS in the Makefile fixes some of the graphical glitches. |
Thanks, have added that before I forget. Unfortunately my dev environment is woefully out of date so not tested it as yet. |
Thanks Steve! It'd be great if we can get Utype working properly again because not only is it one of the more advanced (scrolling) Uzebox games that has the source available, its the only horizontal shooter for the platform I'm aware of and its .uze file is missing from its Uzebox wiki page: http://uzebox.org/wiki/U-Type_(working_title) If you download the rom from that page, you actually get an incorrectly named Uze-a-move. In lieu of us getting the display bugs fixed in the source, have you got a working .uze or .hex file for U-Type without the graphical glitches? I've only just built my Uzebox (its still not fully finished) and now two of my friends are going to build one so its sloooowly gaining new users :) |
No, I did have a look but couldn't find any old files anywhere. I guess next best thing would be to build against a contemporary kernel, just to get it working. I don't think I published any images, nor for Uze-A-Move, because neither of them were anything like finished games. I don't know where the glitches come from either - AFAIK I didn't use anything other than the regular library functions. |
If we can fix it up I suppose its a bit more likely someone might finish it off if you don't? If nothing else, it would serve as a useful example of how to write a scrolling shooter for the Uzebox or something similar maybe, which is not something that can be said for R-Type and nearly all of its other clones. As I'm sure you've noticed, retro gaming has boomed in popularity over the last few years, and as more and more NES' and C64s die, the Uzebox only stands to become more popular. It was only a few days ago that I told the Commander X16 forums about the Uzebox. https://cx16forum.com/forum/viewtopic.php?t=6326 No-one had heard of it and this was on a forum of Commodore and retro computing enthusiasts. Uzebox hasn't done a good job of marketing itself as a project. Speaking of IDE's, its very fast to set up a Uzebox IDE under Linux. I realise how ridiculously long it takes to install the Atmel / Microchip Studio under Windows. Yuck! I've documented how I configure Kate as a Uzebox IDE on the wiki here: https://uzebox.org/wiki/Configuring_Kate_for_use_as_a_Uzebox_IDE Yesterday I updated the Getting Started on the Uzebox guide to cover installing the UB dev stuff (and link to my Kate guide): |
Have you seen or played Starduino, the Uzebox demake of Starfox, yet? |
Hi Steve I managed to find an early test build of Utype online but unfortunately there is only one level in it. There are four levels in the latest code right? You may want to add these working binaries to your repo until we get it fixed up? |
That's good you managed to find an old binary. There are tiles and maybe some map data for more levels but only the first one was "finished". I think flash space started to get tight after that. At the time there was some speak of having some kind of multi-load system to support more but I'm not sure anything ever came of it. |
Hi Steve
I was impressed that u-type still builds under a recent Linux using the latest Uzebox kernel, that's more than I can say for most open source UB games, but unfortunately its not really playable due to several graphical issues, as shown in the attached cuzebox screenshot.
The only warning output during build was:
Are there any working binaries anywhere?
Do you still have a Uzebox?
Thanks
The text was updated successfully, but these errors were encountered: