I didn’t know the power socket was different between the U.S. and European SNES/SFC. On my VB, I use the Performance brand 3rd party AC adaptor, so I don’t even have a tap.
I guess you’ll either have to use a voltage/plug convertor, like Ben suggests, or cut the cable off of the SNES adaptor and wire it up to a German “trafo” that can supply the 6 to 13 volts @ 850mA the VB needs.
The “Trafo Mod” page right here on PlanetVB describes a similar idea. Except, instead of opening the controller, you just need to replace the wire on the trafo with the one from the SNES one, making sure to match the polarity.
That should work fine. The voltage is within the 6-13V range and 1.3A is plenty, since the VB seems to draw less than 850mA (0.85A) which is what my U.S. SNES adaptor supplies.
All you need is an adaptor that has a 6 to 13 volt DC output, negative tip, [Might have a picture like this on the back: (+)—(o—(-) ] and can supply at least 850mA of current. To my knowledge, every SNES adaptor in the world fits these requirements. The specifics of your adaptor should be on printed on the back.
You mean they have a stereo camera mounted on someone’s head?
And, on the projector, was it autostereoscopic? (3D without special glasses) If you did have to wear glasses, what kind? Polarized (like sunglasses) or LC shutter glasses?
1. The GBA’s screen is reflective, so it would be hard to get a good picture in an HMD.
2. It’s not higher resolution than a VB’s display. GBA: 240 x 160 VB: 384 x 224
3. Portability shouldn’t be a factor, anyway. Mostly due to what I like to call the “Wet Willy Principle” 😉
I think the VB2 should be a console (portable like a GC, not like a GBA) with a large, multi-user stereo display. HMDs have too many problems and restrictions.
lameboyadvance has his (ODD) and (EVEN) labels switched:
Data: 0123456789
Even: 02468
Odd: 13579
Notice that the two files are each 1/2 the size of the original. Thus, the chips should each be 1/2 the size of the file.
If the chip is larger, the file (either even or odd) must be either padded to size, or duplicated enough times to fill the chip.
E.g. for a 512KB chip and a 64KB file, the file is split into even/odd files that are 32KB each. Each chip must contain 16 copies of one of the 32KB files. (32 * 16 = 512)
Or, to save time burning EPROMs, you could use my program called “padromvb.exe” included in the gccVB distribution. It knows how to fit “0xFF” data (padding) in between the data and the “header” in a VB ROM. Since an empty EPROM is actually filled with 0xFF’s, the programmer can just skip the padding, saving a lot of time. (Obviously, you pad the ROM, then split it.) Because of the way it works, it will even work on commercial ROMs, which you shouldn’t even have, much less put into an EPROM cart 😉
BTW, the even bytes (0, 2, 4, etc.) go into the chip attached to VB pins D0-D7 and the odd bytes (1, 3, 5, etc.) go in the D8-D15 chip.
Like I said, I have been, but I still don’t have anything in there about framebuffer or sound. :/
The person to ask about framebuffer access is DogP. Or, you can consult his source-code at his website: Project: VB(Direct Link)
frostgiant is the only one who’s done much sound R-E’ing. He sorta dropped off the radar last fall, and he’s pretty hard to get in touch with… He said he almost had a sound document complete, but no-one’s ever seen more than excerpts. 🙁
“For more information on these and other exciting VB dev’ing topics, stay tuned to the PlanetVB Forums!” 😉
1) There are 4 shades of red onscreen at once. One is always Black, the other 3 are defined by the BRT registers (BRTA, BRTB and BRTC.)
There are four palettes from which an OBJ can choose, and another four from which a BGMap cell can choose. Each of the four entries in a palette points to one of the aforementioned four shades.
2) Positive parallax values move things away from the user’s eyes (i.e. “into the screen.”) Negative parallax values bring them nearer (i.e. “out of the screen.”)
If you have more Q’s, come into the channel!
IRC | EFnet | #virtualboy
When are you going to release your program? I can’t wait to see it! (And your source-code, of course 😉
Only 3 things wrong with the colors. The first two are caused by having one’s gamma adjusted properly. (Which also messes up the BG image, but I can live with that…)
1. The sickly pinkish color used for, e.g. the Subject line above each post. (Each occurance of #AF0A0A should be changed to #FF0000.)
2. Not enough contrast.
3. The idiot(s) who thought up CSS didn’t put color adjustment for all possible form controls. (I might have another go at fixing the checkboxes…)
Anyway, to reiterate what Fredde said: Great content!
Because writing a new engine from scratch would be a better use of time and produce far better end results. As evidenced by the YetiVB project (j/k, Dan! Blow the dust off that sucker and keep goin’! 😉
Plus, once the engine was created, the content from these or any number of other (inexplicably) popular games could be converted (relatively) easily, providing the same net effect. (Which would probably NOT be record numbers of VB fans…)
Actually, lameboy, there is no BIOS, nor any software that expects one, but I get your meaning…
To be more precise, the VB (or an external device, like a PIC) would have to either communicate with a floppy drive controller chip (such as the WD2797A) or control the drive directly.
Since it was done on a GB, it could be done as easily, if not easier, on the VB. But, like the GB one, you can’t run commercial games on it.
But, if you’re going to go to all the trouble, you might as well use an ATA HDD, which at least has it’s own onboard controller and a sane, well-documented bus/command structure. (Not to mention the size and speed benefits…)
Now, lets discuss replacing the clunky (and not even officially supported) link-port with ethernet or USB!
I think it’s safe to say you should just forget about the official kits. Any that aren’t already in the hands of VB fans have probably been returned to Nintendo and (probably) recycled/destroyed… *sniff*
Follow Parasyte’s advice and make a cart. The only thing restricting what ROMs you can put on it is the size, which is determined by the Flash chip(s) you use. There are (I think) 4 games that are 2MB, (16Mbit) but most are 1MB (8Mbit) or smaller. And, of course, most demos are only around 64KB (512KBit.)
What he forgot (or chose not) to mention, is that you also need a way of programming the chip(s.) For this, I recommend buying or making a Willem programmer (http://www.willem.org.)
Or, if you would rather take a small risk than spend the money, you can use the “BIOS swap trick” and an old PC. (You can find info on this on some XBox modding sites, or just Google it.)
If you want the cart to be physically small, you should use PLCC chips because, even socketed, they’re quite tiny. But, if you do, you’ll most likely have to get/make an adapter for the device programmer. (I got one with my Willem, since it was so cheap.)
Those look great, and that’s pure genius using the screw holes to mount it! I hope you sell them all. (If only to prove there are at least 4 VB fans in the world 😉
The binaries that will be released are Win32, but the v810 patches will be included, so it should be easy enough to compile for the average Linux geek 😉 The linker script and crt0 library should work the same, of course.
(NOTE: the patches are for gcc 2.95.2.)
[EDIT: Whoops! The patches didn’t get included, but the readme shows where to get them…]
Dan has re-enabled lighting and, along with the new screen-shots, he seems to cryptically allude to a speedup… Go check it out, now!!! (The link is in the first post of this thread.)
WOOT! Way to go Dan! 😀
Post Edited (01-26-04 22:02)
