Actually, you’re referring to the veGL project which makes the VB into a kind of “headache accelerator” for the PC (I kid, I kid!). It doesn’t just send video straight to the display (which is impossible without modifying the actual VB unit itself, and would take much more than a simple ADC) but instead commands the VB’s CPU to produce images on the VB’s display just as a VB game does.

It would be a fairly quick way to test graphics for a homebrew project, but since you need a cart, anyway, you may as well just start dev’ing your project and test on HW periodically.

I don’t want to dissuade you from making one, though. I’m sure Alberto would love some outside confirmation that the instructions can be followed successfully by someone other than himself. 😀

Hooray for simple, easy to fix errors! 😀

You’re the man, KR155E! It works exactly how one would expect, now! :thumpup:

Actually, I’ve wondered all along why it didn’t do an “and” search, but I only recently noticed the word “and” at the end of the search title thingy.

Eww, WMV… 😛

heh, j/k, thanks for posting!

EDIT: Yikes… That was painful to watch, even compared to other History/Discovery/TLC “reality” shows 😛

Also, notice that they didn’t set the focus or IPD, and that the “token dumb guy” still wanted to keep playing, even with the glitchy screen!

I had to cringe when the monkey was trying to get the thing on the stand! Seriously?! Do you know you’re on NATIONAL TV, dude? 😯

In case you do end up having to use multiple versions of the images with text in them, I’m working on a general-purpose compression system for VB (based on miniLZO; the fastest decompression you can get, last time I checked).

It will involve converting images to raw binary chars/maps (ie. as the VB wants them), compressing said binaries with a custom utility, and converting the compressed files into object, include, or .s files, as usual.

Loading will be practically identical to (if a tiny bit slower than) using memcpy to put chars, maps, etc. into the right part of the VB’s RAM.

I’m having problems with gritVB ignoring or misinterpreting my options right now, but I should have a demonstration up pretty soon.

@parasyte:

Have you seen this?

https://github.com/jsnyder/arm-eabi-toolchain

Might help you with ideas for converting your script to a makefile…

Wow! Nice screenies! BTW, I’m definitely on-board to help make a good English translation (if you want me to).

Another thing I’ve posted before (and another member here said it worked for him, too) it helps them come out easier if you ever so slightly tighten the screws first. You might give your modified driver one last try 😉 You can feel a little “click” when it works right, like the plastic that’s wedging the screw in is cracking loose (but nothing’s actually breaking, AFAICT, if you do it right).

Woot! Glad to hear there’s a new dev’r up and running!

I’m not sure what “versions” you’re talking about… If you mean compiling from source, I don’t think there’s a difference between 2.95 precompiled and building it yourself. Or do you mean the 4.x branch? AFAIK, it still has some kind of function calling bug, so I would stick with 2.95 as it seems to make “good enough” code (at least for my purposes). I don’t think you can even build 2.95 in current cygwin, without installing an older compiler (it currently ships with 4.3.4).

[X] 2.95 precompiled NVC version 2010/3/31

I don’t know how to find the cygwin version, but I just updated using the latest installer, version 2.738, and then rebuilt a VB ROM to make sure nothing broke.

[RunnerPack]

I think I know what the problem is now. It looks like you’re using this version but trying to run it with a batch-file from the regular Windows cmd shell.

That version is compiled with, and requires, the cygwin shell/environment to run properly. It’s also the source of the errors coming from libgccvb.h, since certain versions of that file are no longer compatible with this older (2.95) branch of gcc. You’re probably using one that works with the 3.x or 4.x branch of gcc (yes, the VB development situation is a bit of a mess, but it’s being worked on!).

In other words, it’s not your fault, since it’s not very clear (yet) what works with what on which system.

Basically, if you want to stick with cmd.exe and batch-files (which I don’t recommend) you need the older compiler. To use the version you have, you need to install cygwin (making sure that make and other development-related packages are installed; just look though and use your instincts, or ask about specifics) and extract the contents of that zip into c:\cygwin\usr (making sure directories are recreated properly; I recommend 7zip).

Then you will be able to use a makefile and building will be much quicker, more robust, and more easily customized. 😎 :thumpup:

• This reply was modified 15 years, 6 months ago by RunnerPack.

Wow, that’s cool! I wonder why they stopped at the dust cover… even if the black plastic takes the paint differently, it would still look better, IMO.

I might have to try this on my flash cart 🙂

If the meat tastes good (which I doubt, although it’s probably a tad less stringy/gamey than “free-range” lion) and it’s just going to waste otherwise (which is likely) then what’s the big deal? Meat’s meat.

If I was starving, and I could stand to slaughter them (I’m a bit squeamish around blood…), I’d even eat house cats. I’ve heard dogs are nutritionally worthless, though, plus they’re better pets than cats 😉

I’m not going to pay the same price (or, most likely, more money) for lion tacos when beef/chicken ones are cheaper, though. “Novelty” isn’t worth much to me.

Hey, welcome to the site, HollowedEmpire!

Don’t worry, we all need a little help sometimes… 🙂

Could you post some specific error messages? It would also help to see exactly how your environment is set up (paths, contents of the batch file, etc.). Speaking of paths, did you add the compiler’s “bin” folder to the PATH environment variable? That’s usually what’s wrong when an executable can’t be found (although I think the batch file takes care of this… it’s been quite a while since I used it :-P).

I hope we can get you set up and coding; the more coders the better, I always say (actually, that was the first time I’ve even written it ;-)).

w00t, the request went through! The ball’s in your court, now… 😉

#Nintendo-VB-Fans wrote:

Sorry, this group is no longer accepting new administrators.

#Nintendo-VB-Fans wrote:

Sorry! Join requests are closed at this time.

That’s just another symptom of the standard glitchy display cable syndrome. It’s caused by the fact that all signals are shared between both displays except for one “select” signal. When this signal glitches, it causes the mirroring you’re experiencing. Just fix the cables with one of the methods described on the site (or have someone else do it) and it’ll be perfectly playable again. :thumpup:

The OP hasn’t been here 6+ months or posted 10+ times 😛

[RunnerPack]

HorvatM wrote:

rubengar wrote:
interesting! if someone could give an example of code to make music or sounds would be great!!!!

Precisely. All I want is an example of how to program the VSU registers to generate tones and effects. I don’t care whether they freeze the game or not.

It really is as simple as writing to the VSU registers and RAM periodically (such as with the timer interrupt, as you said). But, if you want example code, just run the included example file (test.txt) through DogP’s Virtual Boy Sound Generator and tell it to output VB source along with the WAV file. You can even use it to experiment with the sound registers and hear what it sounds like without the full compile(/program cart)/run cycle.

After you get that, it’s pretty much just figuring out how all those registers and wave patterns affect the sound. Anyone familiar with how digital sound reproduction “works” (especially with regard to basic additive synthesizers like the VSU) and/or has some musical talent: feel free to write a tutorial on that topic for the wiki!

• This reply was modified 15 years, 7 months ago by RunnerPack.
• This reply was modified 15 years, 7 months ago by RunnerPack.

“<" and ">” are reserved characters in the command-line. The help for the program uses them to show the placeholders you replace with filenames. Just use your filename as-is, like:

wav2vb.exe ahh.wav ahh.h

Making sure, of course, that ahh.wav is in the same folder as the exe, or else specifying its full path like this:

wav2vb.exe c:\somefolder\ahh.wav c:\somefolder\ahh.h

And if there are spaces in the name or path, enclose it in double quotes (“).