XRGB-mini Framemeister

Fudoh · Post by **Fudoh** » Mon Jun 25, 2012 11:20 pm

So nothing has gotten any worse in the new Framemeister firmware as far as I can tell

480p output with scanlines is pretty much broken.
Scanlines for 480i and 480p sources stopped working when they introduced the A/B scanlines, but 240p input was still fine.

Now if I try to show a 240p source (with 480p output) the scanlines don't work properly. They show up, but they darken the whole image and the whole image gets heavily oversaturated with exploding reds and greens when I try to lower the scanline setting (= make the scanlines stronger). This is with a YUV 240p source.

Can you guys confirm this ? Is it different with a RGB source ?

I then used the "EDID get" option

why is this greyed out here on my Mini ? I think I never saw it being available so far (?)

Konsolkongen · Post by **Konsolkongen** » Mon Jun 25, 2012 11:38 pm

Didn't mean to sound like an ass, I completely forgot your post and was just concerned about my own problems, which somehow seems to have solved themselves, and I just wanted to let everyone know that it wasn't a firmware related issue. Sorry

480p output with scanlines work fine with a 240p RGB input (NGCD) and 240p with component (PS2 with ESPgaluda).

It looks pretty normal to me. Are you still using Meister mode for scanlines?

BuckoA51 · Post by **BuckoA51** » Mon Jun 25, 2012 11:46 pm

And with the 2x2 Wall mode I guess I need 4 displays and 4 Minis now

Heh, I was thinking about that, say you had an N64, Goldeneye, a 4 way RGB splitter, 4 minis and 4 tvs, plus some controller extension cables if needed, you could each have your own Goldeneye screen at full size on your display, it's what Goldeneye players have been waiting for all these years!

Who's that really rich gamer on Youtube, last gamer is it? We should e-mail him this idea

Fudoh · Post by **Fudoh** » Mon Jun 25, 2012 11:57 pm

480p output with scanlines work fine with a 240p RGB input (NGCD) and 240p with component (PS2 with ESPgaluda).
It looks pretty normal to me. Are you still using Meister mode for scanlines?

No, for 240p sources I use "picture" + V-Line On + scanline setting of about 75 (in 720p mode).

I'm perplexed that it looks normal to you. I used 480p output for my MVS a lot prior to the latest FW changes. When I now try to mimic my 720p settings on a 480p output I just can't get it right. The image is dull (because even the pixel lines not affected by the scanlines get darkned a lot), the scanlines don't really show until I go down as far as 20 on the scanline A setting and the saturation gets heavily boosted ... looking just weird. I'll take a few digicam shots tomorrow.

Zapf · Post by **Zapf** » Tue Jun 26, 2012 1:22 am

Konsolkongen wrote:
TV-Hotplug OFF/ON which is supposed to be the faster one?

I tried both with ram pack enabled resident evil 2 on the n64 - both appear to be 6-8 seconds of blank screen during the 240p/480i switching, which is completely unusable obv. I'm not sure if thats any faster than in 1.06 or below.

anticipating · Post by **anticipating** » Tue Jun 26, 2012 5:24 am

Zapf wrote:
Konsolkongen wrote:
TV-Hotplug OFF/ON which is supposed to be the faster one?
I tried both with ram pack enabled resident evil 2 on the n64 - both appear to be 6-8 seconds of blank screen during the 240p/480i switching, which is completely unusable obv. I'm not sure if thats any faster than in 1.06 or below.

Did you turn the unit off and on after changing when you tested? I think that, like the language change, changing that doesn't immediately take effect. I changed it to off and power cycled and didn't get any display at all, and had to reload the firmware. That might've been just my tv though.

Zapf · Post by **Zapf** » Tue Jun 26, 2012 5:46 am

Yes. hotplug is on by default, I switched and turned off / on. no improvement when set to off. I'll go back and forth some more, but would appreciated someone else's testing too

Konsolkongen · Post by **Konsolkongen** » Tue Jun 26, 2012 12:41 pm

Fudoh wrote:
I then used the "EDID get" option
why is this greyed out here on my Mini ? I think I never saw it being available so far (?)

It has always been available on my TV

Anyway I was playing around with the EDID files stored on the MicroSD and this what I got once they were decoded:

TV_EDID.DAT:

Code: Select all

konsolkongen@konsolkongen-desktop:~/Desktop$ edid-decode TV_EDID.DAT 
Extracted contents:
header:          00 ff ff ff ff ff ff 00
serial number:   34 a9 a7 a0 01 01 01 01 00 14
version:         01 03
basic params:    80 00 00 78 0a
chroma info:     da ff a3 58 4a a2 29 17 49 4b
established:     00 00 00
standard:        01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01
descriptor 1:    02 3a 80 d0 72 38 2d 40 10 2c 45 80 ba 88 21 00 00 1e
descriptor 2:    02 3a 80 18 71 38 2d 40 58 2c 45 00 ba 88 21 00 00 1e
descriptor 3:    00 00 00 fc 00 50 61 6e 61 73 6f 6e 69 63 2d 54 56 0a
descriptor 4:    00 00 00 fd 00 17 3d 0f 44 0f 00 0a 20 20 20 20 20 20
extensions:      01
checksum:        d0

Manufacturer: MEI Model a0a7 Serial Number 16843009
Made week 0 of 2010
EDID version: 1.3
Digital display
Image size is variable
Gamma: 2.20
Supported color formats: RGB 4:4:4, YCrCb 4:2:2
First detailed timing is preferred timing
Established timings supported:
Standard timings supported:
Detailed mode: Clock 148.500 MHz, 698 mm x 392 mm                                                                   
               1920 2448 2492 2640 hborder 0                                                                        
               1080 1084 1089 1125 vborder 0                                                                        
               +hsync +vsync                                                                                        
Detailed mode: Clock 148.500 MHz, 698 mm x 392 mm                                                                   
               1920 2008 2052 2200 hborder 0                                                                        
               1080 1084 1089 1125 vborder 0                                                                        
               +hsync +vsync                                                                                        
Monitor name: Panasonic-TV                                                                                          
Monitor ranges: 23-61HZ vertical, 15-68kHz horizontal, max dotclock 150MHz                                          
Has 1 extension blocks                                                                                              
Checksum: 0xd0                                                                                                      
                                                                                                                    
CEA extension block                                                                                                 
Extension version: 3                                                                                                
71 bytes of CEA data                                                                                                
  Video data block                                                                                                  
    VIC 31 (native)                                                                                                 
    VIC 16 (native)                                                                                                 
    VIC 20                                                                                                          
    VIC 05                                                                                                          
    VIC 32                                                                                                          
    VIC 19                                                                                                          
    VIC 04                                                                                                          
    VIC 18                                                                                                          
    VIC 03                                                                                                          
    VIC 17 
    VIC 02 
    VIC 22 
    VIC 07 
    VIC 21 
    VIC 06 
    VIC 01 
    VIC 10 
    VIC 11 
    VIC 14 
    VIC 35 
    VIC 15 
    VIC 36 
    VIC 25 
    VIC 26 
    VIC 29 
    VIC 37 
    VIC 30 
  Audio data block
  Vendor-specific data block, OUI 000c03 (HDMI)
    Source physical address 1.1.0.0
    Supports_AI
    DC_36bit
    DC_30bit
    DC_Y444
    Maximum TMDS clock: 190MHz
  Extended tag: Colorimetry data block
  Speaker allocation data block
Basic audio support
Supports YCbCr 4:4:4
Supports YCbCr 4:2:2
4 native detailed modes
Detailed mode: Clock 74.250 MHz, 698 mm x 392 mm
               1920 2448 2492 2640 hborder 0
                540  542  547  562 vborder 0
               +hsync +vsync interlaced
Detailed mode: Clock 74.250 MHz, 698 mm x 392 mm
               1920 2008 2052 2200 hborder 0
                540  542  547  562 vborder 0
               +hsync +vsync interlaced
Checksum: 0x63

Xm_EDID.bin:

Code: Select all

konsolkongen@konsolkongen-desktop:~/Desktop$ edid-decode Xm_EDID.bin 
Extracted contents:
header:          00 ff ff ff ff ff ff 00
serial number:   36 78 03 00 01 00 00 00 01 15
version:         01 03
basic params:    80 34 21 78 ee
chroma info:     ee 50 a3 54 4c 9b 26 0f 50 54
established:     a5 4b 00
standard:        d1 c0 90 c0 81 0f b3 00 01 01 01 01 01 01 01 01
descriptor 1:    02 3a 80 18 71 38 2d 40 58 2c 45 00 07 44 21 00 00 1e
descriptor 2:    00 00 00 ff 00 30 30 30 30 30 31 0a 0a 0a 0a 0a 0a 0a
descriptor 3:    00 00 00 fc 00 58 52 47 42 2d 6d 69 6e 69 0a 0a 0a 0a
descriptor 4:    00 00 00 fd 00 38 4c 1e 51 11 00 0a 20 20 20 20 20 20
extensions:      01
checksum:        4e

Manufacturer: MSX Model 3 Serial Number 1
Made week 1 of 2011
EDID version: 1.3
Digital display
Maximum image size: 52 cm x 33 cm
Gamma: 2.20
DPMS levels: Standby Suspend Off
Supported color formats: RGB 4:4:4, YCrCb 4:2:2
Default (sRGB) color space is primary color space
First detailed timing is preferred timing
Established timings supported:
  720x400@70Hz
  640x480@60Hz
  640x480@75Hz
  800x600@60Hz
  800x600@75Hz
  1024x768@60Hz
  1024x768@75Hz
  1280x1024@75Hz
Standard timings supported:
  1920x1152@60Hz
  1400x840@60Hz
  1280x800@75Hz
  1680x1050@60Hz
Detailed mode: Clock 148.500 MHz, 519 mm x 324 mm
               1920 2008 2052 2200 hborder 0
               1080 1084 1089 1125 vborder 0
               +hsync +vsync
Serial number: 000001






Monitor name: XRGB-mini



Monitor ranges: 56-76HZ vertical, 30-81kHz horizontal, max dotclock 170MHz
Has 1 extension blocks
Checksum: 0x4e

CEA extension block
Extension version: 3
34 bytes of CEA data
  Video data block
    VIC 16 (native)
    VIC 05 
    VIC 04 
    VIC 03 
    VIC 02 
    VIC 07 
    VIC 06 
  Audio data block
  Speaker allocation data block
  Extended tag: Colorimetry data block
  Vendor-specific data block, OUI 000c03 (HDMI)
    Source physical address 1.0.0.0
    Supports_AI
    Maximum TMDS clock: 150MHz
Basic audio support
Supports YCbCr 4:4:4
Supports YCbCr 4:2:2
1 native detailed modes
Detailed mode: Clock 74.250 MHz, 820 mm x 460 mm
               1920 2008 2052 2200 hborder 0
                540  542  547  562 vborder 0
               +hsync +vsync interlaced
Detailed mode: Clock 74.250 MHz, 820 mm x 460 mm
               1280 1390 1430 1650 hborder 0
                720  725  730  750 vborder 0
               +hsync +vsync
Detailed mode: Clock 27.000 MHz, 615 mm x 460 mm
                720  736  798  858 hborder 0
                480  489  495  525 vborder 0
               -hsync -vsync
Detailed mode: Clock 27.000 MHz, 615 mm x 460 mm
               1440 1478 1602 1716 hborder 0
                240  244  247  262 vborder 0
               -hsync -vsync interlaced
Checksum: 0x4f

Is it possible to read anything useful from this information? My TV doesn't seem to care that the MVS is weird and V-syncs perfectly with the Mini still (very slight stuttering still occurs), but I believe that Artemio's TV wouldn't V-sync with the MVS>Mini combo. Perhaps some of this information could be useful for people looking to buy a new TV, provided that someone else has posted the EDID information of that TV somewhere on the internet.

Fudoh · Post by **Fudoh** » Tue Jun 26, 2012 1:01 pm

I don't think so. The EDID is basically just there to limit output resolutions or frequencies (to prevent damage, e.g. from a BD player if the display can only handle 1080i) or to preset color spaces (RGB vs. YCbCr), but I can't imagine that it would have to do anything with micro stutter, especially since all the Framemeister output options are forced anyway.

Fudoh · Post by **Fudoh** » Tue Jun 26, 2012 1:22 pm

Here's a comparison (in terms of oversaturation which I see with 480p output and 240p input with scanlines):

And since the Mini has no White level control, it's really hard to compensate. I can drastically decrease the saturation, pump up the brightness. Add LOTS of contrast on the TV's side, but that's nerve wrecking if I want to switch from scanlined to non-scanlined from times to times. Very weird.

Also the brightness offsets for 240p/480i/480p are still widely off. Have to go +/-20 depending on the input signal.

Konsolkongen · Post by **Konsolkongen** » Tue Jun 26, 2012 2:42 pm

I can clearly see what you mean now. I will try again later tonight

ifog · Post by **ifog** » Tue Jun 26, 2012 8:15 pm

Just for information , Taito F3 display not fixed with firmware 1.07 .

Konsolkongen · Post by **Konsolkongen** » Tue Jun 26, 2012 10:15 pm

Konsolkongen wrote:I can clearly see what you mean now. I will try again later tonight

Okay I see it now too. The top of the score attack screen is supposed to be orange (when the clouds are gone) but when adding scanlines in 480p it becomes all red. Sorry that I didn't see it last night.

I tested with Picture mode and toggled V-lines on and off with the C button. Scanlines at 75 like yours (btw I thought you wanted to decrease the scanlines when the Mini came out?

).

EDIT: Why did you use 480p output again? 480p scaling on my TV is just awful. Thankfully 720p isn't

Fudoh · Post by **Fudoh** » Tue Jun 26, 2012 10:29 pm

Why did you use 480p output again? 480p scaling on my TV is just awful. Thankfully 720p isn't

just feel like it from time to time

Scanlined 720p is great - of course, but sometimes I enjoy the smoother 480p picture. I especially like the MVS picture with it.

On 720p output I use scanlines with 75-85. On the old Mini fw (without scanline adjustment) the 480p scanlines were ok as well, but now I have to strengthen the scanlines down to 25 or 30 to get some effect and by the time I do this the screen is dark and the colors way oversaturated.

We should really do a bug report sometime soon and compile the known bugs - I tend to forget about them otherwise

Konsolkongen · Post by **Konsolkongen** » Tue Jun 26, 2012 10:40 pm

Sounds like a good idea

I'm sure 480p output is great if my TV would do a better job upscaling it

Artemio · Post by **Artemio** » Tue Jun 26, 2012 11:00 pm

Konsolkongen wrote:My TV doesn't seem to care that the MVS is weird and V-syncs perfectly with the Mini still (very slight stuttering still occurs), but I believe that Artemio's TV wouldn't V-sync with the MVS>Mini combo.

It wouldn't sync with 1.05, I skipped 1.06 and just tested with 1.07. I works just as you say, really neat.

I have been using the 1080p output with scanlines with picture mode and smart x 2, and have been intrigued with the results. It uses a 3 pixels per line with 1 pixel per scanline pattern or perfect 4x pixel if no scanlines are used. This makes teh scanlines look too thin, very "digital" and not CRT like, but very well defined pixels. This mode would be great if two lines of pixels were darkened or shadowed, as in other cases.

When using 720p, after my TV scales the signal, It looks great with scanlines as we've all found out in the past. However, when examining the pixel pattern closely I get an alternating pixel density per line, sometimes of 4 or 3 pixels wide, not as well defined since the scaling is not exact.

I played with this since as you might remember after coding the lag test and using it on my set, I found out that I had around 7 frames of lag when using HDMI, however 0 frames when using DVI. Since 720p is not available throught DVI, I've been uexperimenting with these settings. What would you guys prefer? I'd love a pixel perfect mode that does look a bit more CRT like.

EDIT: Tested different Neo Geo MVS systems and all behaved properly (1F, 1C and 1B). BTW Konsolkongen, you don't need to set the V_WIDTH to 33 when using SmartX2, scanlines show the same way as any other 240p source eventhough it is recognized as 241. I know that it doens't fill teh screen completely, but I like the fact it is scaled in a linear fashion.

Konsolkongen · Post by **Konsolkongen** » Wed Jun 27, 2012 12:06 am

Artemio wrote: When using 720p, after my TV scales the signal, It looks great with scanlines as we've all found out in the past. However, when examining the pixel pattern closely I get an alternating pixel density per line, sometimes of 4 or 3 pixels wide, not as well defined since the scaling is not exact.

I get this too, but only on certain colors. Like light gray or light yellow/brownish colors. Is that the same for you?

Fudoh · Post by **Fudoh** » Wed Jun 27, 2012 6:21 am

I played with this since as you might remember after coding the lag test and using it on my set, I found out that I had around 7 frames of lag when using HDMI, however 0 frames when using DVI. Since 720p is not available throught DVI

how does your TV determine wether a HDMI or DVI signal comes in ? Can't you leave the Mini in HDMI mode and use some kind of double adapter cable (hdmi - dvi - dvi - hdmi) to mimic the DVI behaviour ? You can force the HDMI signal into RGB, so it doesn't matter on the Mini's side.

BuckoA51 · Post by **BuckoA51** » Wed Jun 27, 2012 11:20 am

We should really do a bug report sometime soon and compile the known bugs - I tend to forget about them otherwise

Yeah there's a bunch of information in this thread and picking through it can be time consuming, I think it's time that we put more information up on the wiki. I enjoy writing so I'm happy to put bits and pieces up there that I discover. I wager this discussion will go on longer than even the XRGB3 one has

Shining · Post by **Shining** » Wed Jun 27, 2012 12:31 pm

Shining wrote:
RGB32E wrote:
Shining wrote:And as for my PC Engine Duo-RX.. I bought it in 2007 from VideoGameImports.com and it's RGB modded. I get no picture whatsoever but i do get sound. I have never had any problems connecting it directly to my TV. What do you think might be the issue here?
You could always open up the system and share a photo to identify the particular RGB mod used?
I have finally been able to open up my Duo-RX. Please take a look at these pictures to have a look at the mod and the scart RGB cable being used: http://imgur.com/a/JzOgL#0

When using the original 8pin to SCART adapter shipped with the Mini i get neither picture nor audio, so it's safe to say the RGB cable being used is of the Euro model sort. When using Retro Accessoris Euro SCART to XRGB Mini 8 pin adapter(the first cheaper model) i do get audio, but no picture. I have just ordered the second version of the Euro SCART to XRGB Mini 8 pin adapter which takes its power from the power supply, hoping that it will solve the problem. If not, i really don't know what to do.

So, can you guys see any 'faults' in this mod looking at the pictures?

For those interested i recieved the new Euro SCART to XRGB Mini 8 pin adapter which takes its power from the power supply, and i now get both audio and video using my RGB modded Duo-RX! Happy times! The strange thing is, if i use 720p or above i get constant drop outs. Using 480P works pretty damn well with only minor sync issues. Maybe it is a cable issue. I'm just happy i got it working though

Oh, and i still haven't tried the new firmware. Should do that asap.

How about the 1CHIP-03, has it been confirmed/denied whether or not it has improved video quality compared to 1CHIP-01/02?

Konsolkongen · Post by **Konsolkongen** » Wed Jun 27, 2012 12:55 pm

Shining wrote: How about the 1CHIP-03, has it been confirmed/denied whether or not it has improved video quality compared to 1CHIP-01/02?

Nothing yet. em0ti0n is busy moving to a new apartment so it'll probably be a few weeks before he can test it.

BuckoA51 · Post by **BuckoA51** » Wed Jun 27, 2012 1:27 pm

Using the Retro console accessories Euro SCART to XRGB Mini 8 pin adapter has also cured my N64 problems as far as I can tell from a quick check. I get a bright noise free picture now compared to "no signal" before.

Artemio · Post by **Artemio** » Wed Jun 27, 2012 2:27 pm

Fudoh wrote:how does your TV determine wether a HDMI or DVI signal comes in ? Can't you leave the Mini in HDMI mode and use some kind of double adapter cable (hdmi - dvi - dvi - hdmi) to mimic the DVI behaviour ? You can force the HDMI signal into RGB, so it doesn't matter on the Mini's side.

I am not really sure, since the input on the TV is an HDMI port. At first I believed it to be the resolution, since most are exclusive to each mode. But, even in 1080p the TV refuses several settings while the Mini outputs in DVI mode and allows them while in HDMI mode. Will try to find out.

Konsolkongen · Post by **Konsolkongen** » Wed Jun 27, 2012 3:53 pm

My TV adds some extra options when I'm using a DVI to HDMI cable from the Gefen scaler too. Wonder if that means less lag for me too?

BuckoA51 · Post by **BuckoA51** » Wed Jun 27, 2012 6:20 pm

I decided to drag out my C128 to do some tests with the Mini, the results were outstanding! I'm using a C128D which is known as having the noisiest S-Video output but even so the jailbars on the picture were absolutely minimal, much less than transcoding to RGB then using the XRGB3. There were zero picture drop outs too, again unlike the XRGB3. By using screen_set -> LB you can zoom the C64 to full size, eliminating the big old borders. Of course zooming in the C64's already blocky graphics like this onto a huge display won't be to everyone's tastes, but there's nothing to stop you using normal or even smart x 1 mode instead.

The scaling was great as expected, in LB you can see its a tad uneven (some letters have bigger tops than others) but in game its very hard to spot. In Normal and smart x 1 its perfectly fine of course. Just a shame there's no scanlines for PAL just yet, that's certainly help the 64's rather blocky graphics on such a big display Oh almost forgot, the scrolling at all times was one hundred percent stutter free even most c64 emulators can't manage that. (click through the pictures to see them bigger)

mini-c64-pal-svideo-ledstorm-small by videogameperfection, on Flickr

mini-c64-pal-svideo-thingonaspring-small by videogameperfection, on Flickr

Forgot how much fun the C64 conversion of LED Storm was, I never did figure out why they put in a talking computer before each stage (the coin op does not feature this). One of gamings little mysteries.

Fudoh · Post by **Fudoh** » Wed Jun 27, 2012 6:26 pm

Two suggestions:

Comparable to the actual C64 screen size, I recently played of lot of GBA on the Mini (through the GB Player). Using the TV's zoom mode instead of the Mini LB modes I was able to keep perfectly aligned scanlines and zoom the GBA screen to nearly fullscreen. This might depend on the TV of course, but I think it's the better option compared to using the LB modes on the Mini.

I also tried a PAL PS2 game the other day (Gunbird collection was the only one I could find), PAL 288p scanlines didn't look too bad WITH THE OUTPUT SET TO 576p50. My TV does a worse job upscaling 576p compared to 480p, but to get scanlines on PAL sources this is currently the way to go. I wouldn't trust Micomsoft to get the 288p to 720p scaling right anytime soon.

BuckoA51 · Post by **BuckoA51** » Wed Jun 27, 2012 6:50 pm

You're right, scanlines do work on PAL material if you set the output to 576_50, fantastic find! Duely noted about picture zooming too, I've still got the Sony TV so it might work in a similar fashion to yours.

Edit - Ahh that's much nicer! 576_50 + scanlines and zoom on the TV, now the car is more the shape I remember (been so long I forgot)

mini-c64-pal-svideo-ledstorm-576p-small by videogameperfection, on Flickr

Really happy with this, thanks Fudoh!

Fudoh · Post by **Fudoh** » Wed Jun 27, 2012 7:36 pm

looking good! Glad it works fine for you. I guess some TVs might have problems with the zoom + upscaling, but on the Sonys it's quite nice looking.

Konsolkongen · Post by **Konsolkongen** » Wed Jun 27, 2012 7:40 pm

Damn that looks great BuckoA51! Congratulations

Konsolkongen wrote:
Artemio wrote: When using 720p, after my TV scales the signal, It looks great with scanlines as we've all found out in the past. However, when examining the pixel pattern closely I get an alternating pixel density per line, sometimes of 4 or 3 pixels wide, not as well defined since the scaling is not exact.
I get this too, but only on certain colors. Like light gray or light yellow/brownish colors. Is that the same for you?

Here is a picture showing the scanlines problem in 720p:
http://i40.photobucket.com/albums/e236/ ... C00507.jpg

As you can see some are a bit thicker than others. It's really strange, but this happened when I upscaled my XRGB-3 in B1 mode to 720p or 1080p on the Gefen too. It only happens on light colors like these. Otherwise it looks perfectly fine. When I set the Mini to 480p output it looks fine.

EDIT: The game is Soleil (Crusader of Centy/Ragnacenty) on the MegaDrive. Very early in the game.

BuckoA51 · Post by **BuckoA51** » Wed Jun 27, 2012 8:25 pm

Damn that looks great BuckoA51! Congratulations

Cheers, only problem now is I'm looking at C64 flash carts and I really shouldn't have bought the Mini let alone more stuff

Interesting bug, if you change from 240p (or 288p) to 480i on the fly, and you have the mini set to output 480p or 576p, the picture will trip out completely until you go in and set h-pos up or down a notch.

shmups.system11.org

XRGB-mini Framemeister

Re: XRGB-mini Framemeister (now available !)

Re: XRGB-mini Framemeister (now available !)

Re: XRGB-mini Framemeister (now available !)

Re: XRGB-mini Framemeister (now available !)

Re: XRGB-mini Framemeister (now available !)

Re: XRGB-mini Framemeister (now available !)

Re: XRGB-mini Framemeister (now available !)

Re: XRGB-mini Framemeister (now available !)

Re: XRGB-mini Framemeister (now available !)

Re: XRGB-mini Framemeister (now available !)

Re: XRGB-mini Framemeister (now available !)

Re: XRGB-mini Framemeister (now available !)

Re: XRGB-mini Framemeister (now available !)

Re: XRGB-mini Framemeister (now available !)

Re: XRGB-mini Framemeister (now available !)

Re: XRGB-mini Framemeister (now available !)

Re: XRGB-mini Framemeister (now available !)

Re: XRGB-mini Framemeister (now available !)

Re: XRGB-mini Framemeister (now available !)

Re: XRGB-mini Framemeister (now available !)

Re: XRGB-mini Framemeister (now available !)

Re: XRGB-mini Framemeister (now available !)

Re: XRGB-mini Framemeister (now available !)

Re: XRGB-mini Framemeister (now available !)

Re: XRGB-mini Framemeister (now available !)

Re: XRGB-mini Framemeister (now available !)

Re: XRGB-mini Framemeister (now available !)

Re: XRGB-mini Framemeister (now available !)

Re: XRGB-mini Framemeister (now available !)

Re: XRGB-mini Framemeister (now available !)