Skip to content
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

graphics display broken #25

Open
elapt1c opened this issue May 19, 2024 · 7 comments
Open

graphics display broken #25

elapt1c opened this issue May 19, 2024 · 7 comments

Comments

@elapt1c
Copy link

elapt1c commented May 19, 2024

it outputs vga fine but makes the sprites look like tv static. also how do i build a VGA version but with usb serial. i dont like having to constantly run *output 15 every time i make a typo. also, a clockspeed star command would be nice because some programs run too quickly.

@Memotech-Bill
Copy link
Owner

it outputs vga fine but makes the sprites look like tv static.

BBC BASIC does not have sprites

also how do i build a VGA version but with usb serial.

As per earlier issue or the README file

i dont like having to constantly run *output 15 every time i make a typo.

So include the star command in the program

also, a clockspeed star command would be nice because some programs run too quickly.

Use the BBC BASIC SYS command to call the C SDK routine to adjust the clock frequency

@elapt1c
Copy link
Author

elapt1c commented May 20, 2024

for sprits i mean custom tiles or whatever they are supposed to be in games. custom graphics. it doesn't render correctly. for the building thing, i meant like not console version but basically output 14 all the time where picocom is only for keypresses but picocom doesn't actually get anything returning such as text.basically a com port serial keyboard (when i say com port serial i mean picocom or regular com port stuff as a computer as a host.)

@Memotech-Bill
Copy link
Owner

for sprits i mean custom tiles or whatever they are supposed to be in games. custom graphics. it doesn't render correctly.

I still don't know what you mean. Give a short example of the code that you think does not work.

for the building thing, i meant like not console version but basically output 14 all the time where picocom is only for keypresses but picocom doesn't actually get anything returning such as text.basically a com port serial keyboard (when i say com port serial i mean picocom or regular com port stuff as a computer as a host.)

That is too specialist a requirement for me to implement. You will have to edit the source code yourself. I will advise that the *output command sets the value of optval, and that the output goes through routine xeqvdu in src/picocli.c. Edit that routine to call fbufvdu for VGA output or org_xeqvdu for console output.

@elapt1c
Copy link
Author

elapt1c commented May 20, 2024

image
what it should look like

image
what it looks like for unknown reasons

@elapt1c
Copy link
Author

elapt1c commented May 20, 2024

pretty much any game can find on https://www.bbcmicro.co.uk/ has that issue. also half of them have syntax errors or other things that shouldn't be happening. so maybe work on functionality and compatability? also, it would be difficult but running disassembly would be awesome for games becase so many games use it

@elapt1c
Copy link
Author

elapt1c commented May 20, 2024

(i recreated what it looks like with pixel art but it looks pretty much the same as the graphics issue)

@Memotech-Bill
Copy link
Owner

Memotech-Bill commented May 20, 2024

Until I know what BBC BASIC command you are executing, which is not having the desired effect, I cannot investigate.

At the very least, provide a link to a specific game that has the issue.

Any game using assembly is unlikely to work as the assembler in PicoBB is for ARMv6 instructions, not 6502 instructions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants