Hi Confusednerd and welcome to PVB! Lesson 1: Ignore akumie 😀
There’s much more art guys than coders, and usually people create graphics for their games on their own, so it’s rather hard to find a coder. I think it would be best if you showed off what you have done before and see if someone is interested.
If you want to choose a more progressive approach, you could browse the development board, see who is actively coding and offer your help.
A price would depend on costs for cart shells. The PCB would be cheaper than a FlashBoy. I think it would be around 50 EUR for a game. But let’s not take over the thread. 😉
DogP schrieb:
Why would Bound High carts need custom parts?
Simply because I don’t have donor carts for that. 😉
Vaughanabe13 schrieb:
Although, wouldn’t there be some kind of legal issue with selling a cart that has a Nintendo ROM on it like that? Maybe he was talking about just making a cart for himself and not to sell.
Yeah I know he was.
I guess like 20 homemade Bound Highs would stay pretty much under the radar.
Yeah, a Bound High cart would be cool! I was thinking about making a run of carts with boxes and manuals, but it would not be possible without completely custom parts. Now it seems in reach! 🙂 Maybe I’ll finally get around to releasing BLOX 2 on cartridge?
BTW, how about making dust caps for that connector?
One year ago, I did a bit of work on the Mario VB code. Basically fixed all the sprites, added some new ones, remodeled the demo level and added Goombas. I was experimenting with several things like text boxes or screen transitions, but did not get those done – found it quite hard to fully understand how to use the engine.
I stopped working when I noticed that back layers are not scrolling smoothly. Told Jorge about the flawed calculation and he said there was not a simple solution. Instead he wanted to rewrite the entire engine since I also gave him a lot of other input. Unfortunately, it has been quiet since then.
Attached is my last version from May ’09, it also includes a compiled version in the output folder if you just want to have a quick look.
You’re totally right, we really need a good tutorial which helps beginners step-by-step. That’s what I wanted the “Getting Started” paragraph of the Dev Wiki to become. But as you see, nobody ever got around to. Shouldn’t take too much work to create a guide actually…
A) Using the older version as Vaughanabe13 described
B) Using newer version like the precompiled 2.95 NVC version
You should definitely go for the second option, because the newer gccVB version are much more advanced. The old one doesn’t support interrupts or bitstring instructions for example.
You only have to:
1) Install Cygwin
2) Download gccVB 2.95 prec., unpack it and copy the files to /c/cygwin/usr/
Then to build Mario VB, you only have to execute the following in Cygwin to trigger the make script included in the Mario VB source (for this example, the Mario VB source lies in C:/marioVB/):
cd /cygdrive/c/marioVB/ && make
(Everything from memory, might’ve missed a detail)
