Very cool.
Posts by captain_zzap
Caution: Non registered users only see threads and messages in the currently selected language, which is determined by their browser. Please create an account and log in to see all content by default. This is a limitation of the forum software.
Also users that are not logged in can not create new threads. This is a, unfortunately needed, counter measure against spam. Please create an account and log in to start new threads.
Don't Panic. Please wash hands.
-
-
The quite horrible ghosting/smearing on the right side of objects are still there.
Sadly I can confirm this. This is 1600x1200@60Hz
But it varies from resolution to resolution: This is 800x600@50Hz, the shadows are not gone but way less visible, especially with other colors then blue on yellow.
But VC20 looks quite bad.
)-:
-
If you want to give it a try, here's a release candidate of version 2.4 of the ECSv2 config tool:
http://wiki.icomp.de/w/images/…divisionECSv2-2.4-rc1.lha
There are no FPGA changes yet, but chances are that this and some other issues may go away with this update.
Nice, the issue is solved, but did the config format change? I can't import my old settings.
-
Ahh, yes, forgot to mention, my default Workbench resolution is SuperPlus 800x300, which is ECS.
-
Here is my config. I have the very same effects, but these happen also, when I reset the Indivision to default settings.
This behavior really only occurs when I'm using the config/flash tool, not in normal operation/resolution switching. Also the black stripe disappears when adjusting other screen modes in the config tool.
My setup consists of a A500 Board rev 6, TF536, A500 Clockport+Silversurfer, AT-Bus clone and a PicoPSU 80W attached via checkmates Zorro/ATX board. And no, at the time, I have no original PSU to test.
-
Same issue here. It restores to normal, when testing another screen resolution in the Indivision config tool.
-
Live configuration is indeed very cool and solves quite some problems.
-
I don't know how to configure the MK3 but your calculation doesn't quite match reality. Pal is more like 288 lines and every game possibly can have the full resolution/overscan or something like a 200/256 line window within these 288 lines. And the position is not the same on every game, which makes integer scaling with a perfectly centered picture and the least amount of wasted space a bit more complicated.
-
I guess it pretty much depends on the video mode your indivsion is set to output. I would try to set some standard 60Hz mode to try and see, if you can get any picture at all. Note, I don’t mean your Amiga screenmode, but the vga videomode which is set to display your Amiga screenmode.
I just did a quick test with my equipment and the result is okay. You can see the mjpeg artifacts my capture device produces and sharpness could be better.
One tip, disable scanline effects. They pretty much always look bad when captured and uploaded to YouTube.
https://youtu.be/9kZArRRY-MA -
There are really cheap, zero latency adding vga2hdmi converters. With the right settings those should display a picture in 50Hz and 60Hz on any modern Hdmi capable TV. I think it would be worthwhile figure out how to achieve that and be able to recommend a path for an easy upgrade to Hdmi.
-
That’s great! Thank you.
-
VGA->HDMI conversion means digitalizing, so it will add latency to the system...
Not necessarily. The latency added by products like the ossc or retrotink measures in the range of a few scanlines, not frames, which is not humanly noticeable.
-
Isn’t it possible to disable dma on the 2091? Transfer would be terribly slow but it should work.
-
By the way, there exists a fpu software emu which could probably enable you to use the few software that requires an fpu to run, but actually doesn’t use it. Look for femu and try.
-
Yes the VDC properties are nice (though glitch-y), the rest of the 128 architecture is a bit of a mess unfortunately. Building a accurate replica with all the quirks will be a nightmare. And because the Chameleon hardware itself doesn't work on a C128, we kind of try to ignore this topic
How about instead of creating a c128 core, you could just implement a “c128 in C64 mode” core which would mean having vdc available in software like novaterm/striketerm. You wouldn’t create a new machine, but give 64 users the ability to have higher resolution/text.
-
So the Turbo Chameleon isn’t a retro product either?
-
I suppose it should work with this http://aminet.net/package/driver/moni/Native
-
You could also try to half the resolution of your Panel. I have a 1600x1200 Monitor and with a resolution of 800x600 and I can‘t spot any scaling artifacts/interpolation added by the monitor.
-
-
Yeah, DCTelnet needs an 68020 or higher.
As for Term, there is an executable in the mentioned archive, please look again.
I haven't done this myself, since I'm simply using a nullmodemcable, but it should work like this: tcpser configured in the right way, should create a virtual serial.device which actually serves as a gateway to a telnet connection. Term needs then to be configured to use this virtual serial.device.