|
Post by sogilbert on Dec 11, 2019 12:07:47 GMT
Is there an SDK or something? Because I like the CD audio in games. Thank you in advance.
|
|
|
Post by turboxray on Dec 11, 2019 21:04:35 GMT
What's your background/experience? C? Assembly? You have a few options depending on which approach you take (HuC or MKit). For Assembly, I think most of us just use the assembler (PCEAS) and write our own tool chain (I know I do for CD projects). There's definitely documentation on using the CD Bios routines (such as playing a CD track, etc), but I don't know if anyone centralized all the documentation floating around out there. But you're definitely welcome to ask plenty of questions (quite a few of us have CD app experience for PCECD).
|
|
|
Post by gredler on Dec 12, 2019 2:31:45 GMT
|
|
|
Post by DarkKobold on Dec 18, 2019 21:15:07 GMT
I ran into a lot of pitfalls when I first started trying to make a CD game. I was thinking of writing a basic tutorial. It wasn't clear to me that each overlay runs as its own program, starting from scratch almost.
|
|
|
Post by Arkhan on Dec 31, 2019 0:07:40 GMT
I ran into a lot of pitfalls when I first started trying to make a CD game. I was thinking of writing a basic tutorial. It wasn't clear to me that each overlay runs as its own program, starting from scratch almost. That concept is documented in the HuC documentation lol. Anyway to develop for the PCE: You drink these: While eating these: While crying in the dark. You need to be experienced with C, especially "C when shit doesn't work right", and also assembly language concepts, or you will have a rough time. The tools are all archaic/painful. everything is painful. It is not a walk in the park fun time like a Unity or Game Maker youtube tutorial and you need to be ready to deal with that, and looking at old documentation written in English from translated Japanese by non native English speakers, people who didn't finish documentation, or people who documented things wrong. It's fun, but you have to like pain and sadness.
|
|
|
Post by dshadoff on Dec 31, 2019 0:43:21 GMT
You have captured the essence of being a developer in the 1980's/90's... which is also about the time from which the tools originated.
Except donuts were an acceptable alternative snack, from the same basic food group.
|
|
|
Post by ndiddy on Jan 2, 2020 15:40:32 GMT
If you don't mind getting into assembly development, I think Elmer posted the source code to a CD based backup memory hex editor a while ago. You could easily comment out all the hex editor stuff and get started that way. Sorry that I can't find the link, maybe you'll have better luck than I did?
|
|
|
Post by elmer on Jan 6, 2020 4:45:24 GMT
Thanks for posting that, I don't even remember writing it! If someone were going to start an SCD project in assembly-language, then I'd say that the code that I posted in this thread might be a bit more interesting as a starting point for someone that still wanted to use some of the MagicKit assembly-language libraries that are embedded in HuC ... pcengine.proboards.com/post/3954/thread
|
|
|
Post by dshadoff on Jan 6, 2020 5:09:57 GMT
Indeed. Start with what’s already provided as libraries in HuC / PCEAS, and use what you need (but dispose of what you don’t). It’s commented; everybody should look at those comments, they give a lot more information about the system than otherwise existed when HuC was being written. Especially about boot sequence and hardware initialization.
It’s too bad that people don’t look at them more often.
|
|
|
Post by Arkhan on Jan 12, 2020 16:07:40 GMT
That stuff should all be ripped out into a separate document called READ THIS FIRST, ASSHOLE.txt, included with the release lol
|
|
|
Post by dshadoff on Jan 12, 2020 18:15:32 GMT
Do you think that would actually get more people to read them ?
|
|
|
Post by Arkhan on Jan 12, 2020 18:31:42 GMT
Probably. If I see something that obnoxiously titled next to an EXE, I would be inclined to click it and see what it is.
People are kinda lazy. When stuff is interleaved between scary looking assembly and such, they go NOPE NOT LOOKING and close everything and go back to hamfisting the keys.
At the very least, calling it IMPORTANT DEVELOPMENT INFORMATION TO READ BEFORE YOU DO ANYTHING.txt would be good.
and then add code to the compiler's .exe to launch notepad.exe with that file as the argument so whenever you compile your game, the documentation forcibly opens.
hell yeah lol
|
|
|
Post by dshadoff on Jan 12, 2020 20:49:07 GMT
Yeah, but... Long filenames were still pretty new back then, so 8.3 was still pretty much obligatory for support... And notepad was only on Windows systems - this was built for those on Linux and still using MS-DOS too.
|
|
|
Post by Arkhan on Jan 13, 2020 4:49:54 GMT
yeah you can check the running machine system and launch VIM instead, lol. or Edit! or just dump the whole thing straight to the console and make them go back in the short filename days: HEYASSHOLE might have worked!
|
|