Posts by SID-6581

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.

    Hello Alastair,

    Thank you for your work! Here comes my report:


    The Picasso96 settings had to be changed so that 640x400x8 and 640x400x16 again produced perfect test images.


    When I gave 640x400x8 the same (new) settings of 640x400x16 again, the picture problem was exactly the same as in

    the photo above... wait ... the picture problem was not exactly the same. This time the scrambled data at the bottom was gone.


    After I changed the clock from 22.69 MHz to 25.21 MHz for 640x400x8, the "Back to the Amiga" image was displayed again

    without errors in PPAint 7.3c.


    It is noticeable that the problem only occurs when 640x400x8 and 640x400x16 have the same settings. :/

    Maybe you should do some research there.



    Cheers

    SID-6581



    PS: It's fantastic that your Core offers Midi and RTG! This is how your MinimigAGACore differs from all other ports. :love:

    You should clearly advertise this on your website for everyone to see. ;-)

    In my opinion, this must be a bug, because the test image is OK if I use 640x400x8 with the settings of 640x400x16. But as soon as I open a 640x400 picture in PPaint 7.3c, the error occurs. So the question is where the error is.

    I have not expressed myself precisely enough here. I don't think that the problem is with my monitor, as the test image is displayed correctly in 640x400x8 with the settings 640x400x16.

    The best thing to do is to take a look yourself.


    1. 640x400x8 with 640x400x8 settings:

    If I open the picture in PPaint 7.3c in 256 or 16 million colors it looks like this:





    2. 640x400x8 with 640x400x16 settings:

    If I open the picture in PPaint 7.3c in 256 or 16 million colors it looks like this:





    Cheers

    SID-6581



    PS: Above you can see the TC64V1 with the Docking Station 2, the Joystick VS-7000

    and the Cherry G80-3000 mechanical keyboard, which I can warmly recommend to everyone. :-)


    The Docking Station 2 has Midi-Ports. Will the MinimigAGACore support this one day?

    I'm not sure, however, whether it's a driver bug or a problem with the monitor misdetecting the screenmode.

    In my opinion, this must be a bug, because the test image is OK if I use 640x400x8 with the settings of 640x400x16. But as soon as I open a 640x400 picture in PPaint 7.3c, the error occurs. So the question is where the error is.

    Hi Alastair,


    Running 640x400x8 with the same values as 640x400x16 and unchecked vertical "SyncPolarity" had no effect. The error was the same.

    Running 640x400x8 with 640x400x8 settings and unchecked vertical "SyncPolarity" resulted in a black screen.


    So i left the settings as on the pictures above. I use the LG M2232D-PZ.


    Cheers

    SID-6581

    I can report that replacing

    Code
    1. If Exists C:LoadModule
    2. C:Version exec.library version 46 >NIL:
    3. If Warn
    4. C:LoadModule ROMUPDATE
    5. EndIf
    6. EndIf

    with

    Code
    1. C:LoadModule LIBS:intuition.library

    in the startup-sequence and renaming LIBS:intuition-v45.library to LIBS:intuition.library,

    results in the output of "version intuition.library" -> "intuition.library 45.13".


    Unfortunately, this does not affect the screen resolution error reported above.


    Cheers

    SID-6581

    I read the version with DirectoryOpus. There I clicked "Read". Many illegible symbols are then read out, but also "intuition.library intuition 45.13 (3.11.2018)". Why is that different than the version command issues ??? I also have both the intuition.library and the intuition-v45.library in the "libs" folder.

    Yeah, very strange! You did change the pixel clock to match? Anyhow, if what you're using works, that's fine - hopefully I'll be able to address the other issues in due course.

    Yes, both resolutions had exactly the same values as 640x400x16. Both gave a perfect test picture. In PPAint 7.3c, a 640x400 picture was then shifted. The menu bar was so high that it was no longer visible, but also shifted a bit to the left. It was as if the screen resolution was now 840x488 (see Settings) and not 640x400.

    Nice!

    So if both those timings work fine on your monitor, you may as well use the 15-bit timings for 8-bit too - since they make slightly lighter

    OK, I tried that. Although the test picture is without flaws, a 640x400 picture opened in PPaint is then displayed vertically shifted. Strange! I have therefore returned to the previous values.

    Edit: I've just tried to create a 640x400 screenmode, and my monitor refuses to identify it as such - it's detected as either 720x400 or 640x350. The picture's there but the quality's poor because the monitor's expecting the wrong number of pixels. Your monitor might play nicer with this resolution than mine, though. Specs here: http://tinyvga.com/vga-timing/640x400@70Hz

    Watch out for sync polarity - this mode should have negative hsync, positive vsync.


    Thanks for the hint. I was able to successfully realize the screen resolution 640x400 with the following data:




    Only missing 320x200, 640x512 and 320x256. ;-)


    Cheers

    SID-6581

    Thanks Alastair for the technical background information. I don't know to what extent an FPGA is comparable to an emulator in this respect, but "amiberry" for the Raspberry Pi solved the problem quite well. Therefore I suspect that there could be a software solution.


    Cheers

    SID-6581