There's a Readme.txt file included, that has a list of all the command line options.
No, the Linux version still uses OpenTK and will need "X" to run. Version 3 runs great on a Pi5 - though I've still to test of V4, but that should be better as well.
We hope to have an SD card image that boots directly into ZXNext's OS - that's the goal.
AV programs will do what they do. Since CSpect isn't a program that's used by huge numbers of people, they always flag it. Add to it that it's obfuscated, and I open files in share mode etc... they will pretty much always flag it.
While I could pay "hundreds" of pounds/dollars for a code signing certificate, they are of limited use anyway, and for a free product, I'm simply not willing to pay that expense.
I "might" see if I can put it on steam to download, as that skips the AV issues, however without a full UI, you lose that command line use, and it becomes harder to use...
okay... I see it. I'm not sure this is something I can do on my own. It would require the creator to debug the specific areas and let me know what's different. Otherwise.... I'd have to debug the whole game, and figure out the entire thing to even find the routines, never mind what'd wrong.
If they want to debug inside CSpect and figure out what's not working, I'll be happy to address it.... but without them, I'd be looking for a needle in a haystack. ☹️
okay - played it for a bit, didn't notice anything wrong.... going up ladders looked okay, and going to the console, the text came on as I thought it should. So not sure what you're seeing.....
Create an image of the 2.08 SD card, then use that on the command line. If you download the ZIP file, there's a program included that'll turn that into an image for you.
when the OS is running, it’ll return that properly, but if you run a .NEX file directly from the command line, it’ll return whatever value I’ve hacked in a while ago.
you can check nextreg 1 (or something) to see if it’s running under emulation or not.
I've no idea. From what I can tell, it's just the timers due to the way DMA clocks up used TStates. I have change the DMA a little to be more accurate, though it'll never be perfect - but that might help.
k - I can confirm it's not as per hardware... Not sure what the issue is, or how it works mechanically... tried a couple of combos without any luck, so will need confirmation from Alan on how they actually work - or someone that can read the VHDL.
I'm not sure. It's been in for a while, so I'm not sure what state it's in. One timer certainly works, but I'm unsure if anyone has used the cascading timers.... I'm also not sure what I used to test them, as I can't find any cascading demos...
If you have a simple example - with source, then I can take a look....
Sorry... not following. It dies at as soon as you run it? I'm running it on my VM and it seems fine here... Can you try the beast.nex demo? It's fine here. That command line is a little odd... CSpect -zxnext <file.nex> this is all you should need.
