What Needs Fixed In Huc?

[Arkhan]

screw that HuC 4.0 YourMom.  lol

[nodtveidt]

HuC 4.0 OnlyRoverWillUseThis

[Arkhan]

HuC 4.0 OnlyRoverWillUseThisAndAetherbyte,Obviously

lol.

I hope more people will.. but even with a great C compiler, the learning curve for the turbob is kind of steep.

[nodtveidt]

Yeah, it's kind of steep. I think it'll be easier for newcomers though... stepping down from the nearly unlimited "modern" C/C++ on the advanced systems of today can be a nightmare for people who have to adapt to the terribly limited system of the PC Engine. On the other hand... things like sprites are way easier here than on the PC since everything is handled by the hardware and you don't have to worry about blitting pixels like you do in a framebuffer environment.

[Arkhan]

but, blitting is the least of your worries really.  lol.

thats trivial business.

[nodtveidt]

True, but that was actually the biggest hurdle for me after being so used to direct access to the entire pixel array. Then again, experience with the Commodore 64 and its similar video hardware helped a ton. I feel sorry for anyone who has only ever used software blitting... and even worse for scrubs who've only ever used Direct3D. I was already very schooled in C by the time I got to coding the PC Engine, so adapting to the slightly different paradigm wasn't all that hard. Working without structs and having to use the old-style function prototypes wasn't that big a deal in the long run. C++ scrubs are gonna have a hard time though... no inheritance = "OH NOES WAT DO I DO NOW WAAH"

[Arkhan]

I like blitting but only for certain things.  There are times where I would kill for blitting on the PCE.

[mrhaboobi]

sounds like there is deffinately some scope for you old timers to write some how to docs and make life for us newbs a bit easier

[Arkhan]

I plan on writing docs.  I have been for awhile.  I liked writing the doc for Squirrel, and tried to keep it clear and simple.

I wouldn't mind writing more documents like that.  I think I am pretty good at it, but I may be wrong.

[nodtveidt]

Documentation has always been the real Achilles heel of PCE homebrew. Even the docs for HuC, which are some of the best ever done for PCE homebrew, are lacking and contain errors, not to mention entire functions left completely out (such as cd_fade(), which was such a critical function for MSR's presentation).

[spenoza]

I started with Apple Basic, did a little Pascal in high school, and Java in college, and I never did enough of any of them to do squat short of data organization. I would be less worried about graphics and program structure and tracking variables than I would enemy behavior. For me AI, even the most simple routines, is quite scary.

[Arkhan]

Documentation has always been the real Achilles heel of PCE homebrew. Even the docs for HuC, which are some of the best ever done for PCE homebrew, are lacking and contain errors, not to mention entire functions left completely out (such as cd_fade(), which was such a critical function for MSR's presentation).

Yeah I like how some parts of the doc say "Im too lazy to do this", or something, lol.


Not to toot my own horny horn, but Squirrel is probably the best document related to PCE.  lol.

some of the other hardware related ones are nice too, but not entirely helpful to someone trying to do basic C programming (AKA: Get a sprite to move on the screen)

[BigusSchmuck]

Ok gentlemen, where can I get the latest version of HuC and not the old one on Zeograd's Lair?
Also, is there Arcade Card support on this program or are we just limited system card 3.0 stuff?

[Arkhan]

Ok gentlemen, where can I get the latest version of HuC and not the old one on Zeograd's Lair?
Also, is there Arcade Card support on this program or are we just limited system card 3.0 stuff?

Just stick to the Zeograd one (3.21) for now.

The fixes won't matter to you until you get balls deep into a project.