Posts by Steve030

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.

    I reported it on their Github, the response was:


    Quote


    Emu68 does not hit any registers by itself, as Emu68 provides CPU emulation only. What is hitting registers is AmigaOS...


    Besides that - I tried another Web browser last night - Netsurf. Netsurf accessed all the SSL websites without any screen flickering. So perhaps your first theory about IBrowse disabling multitasking was correct.

    Yeah I don't mind. But today I was doing more Pistorm32 testing and found after applying the latest nightly emu68 build the AGA MK3 display seems to be doing this even on trivial things like opening / closing windows. Reverting to the older emu68 build returns the previous behaviour.


    So, I do not think this is a MK3 issue.. Jens I wonder, since you are an expert, how on earth can a CPU accelerator influence the Amigas display stability?

    Okay - I've been doing some testing on: HIGHGFX: Super-High res laced / Indivision mode: 1024x768 VESA - the results are very good in regards to keeping sync & looking good. In-fact I have been able to capture the odd behavior in IBrowse, I have recorded a video! It seems that whenever something 'processor intensive' is being done, the picture loses clarity, it goes blocky momentarily. My theory is that with nizce and myself, before when we were using higher resolutions, Ibrowse's strange blocky effect would actually knock the display off, probably due to the extra overhead of the resolution - but when I'm using a 1024x768 output resolution, we can see the strange behavior.


    Jens I've never played around with those clock/clk loading options in the indivision settings, is this something I should try to alleviate this? Any thoughts on the matter?


    Here is the video (it's currently processing, if not working straight away try later)

    https://drive.google.com/file/…Rwe-wTCb/view?usp=sharing

    By the way Jens I tried your recommended XTREME 1280x1024 with my EDID 1280x1024 and it displays beautifully! Except, such a high resolution uses all my chip memory and then programs like Ibrowse won't even load any more - do you have any advice around this chip memory issue when using high res?

    I just want to say: I have the same problem, specifically with Ibrowse! It makes my monitor lose sync. I am using AGA MK3 latest firmware. Running HIGHGFX: Super-High res laced / Indivision mode: Pre 1280x1024 vsync & auto res.

    Hi,


    I am just trying to get my monitors native resolution to work on my MK3, but as you can see it causes strange horizontal lines. I have tried different HDMI cables. Currently using a very high quality gold Belkin. I am sure it is something in my settings that must be causing it. I am using HDMI>DVI (no converter or adaptor, all one cable) & have made sure to tick 'pure DVI mode' in the settings. I also tried to set up on another monitor and was getting similar issues at the 1600x1200 edid on that one too (made sure to dl the new edid in the options etc). Not sure what is wrong...


    My main monitor for Amiga is an NEC Multisync LCD2170NX


    FYI I experienced the following issue with my Chinon FZ drive:

    * Drive stopped responding or reading disks with MK3 installed, also had 'sparkling' pixels on the display.

    To fix:

    I re-capped my floppy drive & moved the Mk3 ribbon cable further away from the floppy drive. Seemed to solve the problem. I also slacked off the floppy screws (the two on the outside of the case, under the back end) As having these tight caused friction between the motor spindle and bottom floppy shielding.


    I know MK3 is not to blame here. But for what ever reason I needed to service the floppy after the install.

    Okay I will test the DVI option and check.


    In regards to it not sensing resolution, I am still confused in one regard.

    Upon first installing, default settings, I had no idea what profile was being used for games. As I mentioned, I found out it was using the 800x600 profile as default for games (by looking at the OSD). This part I do not understand, could you elaborate? How did it choose 800x600 profile, why was this the chosen profile. Understanding this fact will help me understand the entire system and how it works (I have read the docs)


    Thank you,

    Steve

    Hi Jens, JamieV & me just suggested to specify where to find the firmware flash in the docs. Not to change your GUI. This is to reduce the stress of your users, and the stress of yourself when you have to answer questions in the forum. I hope you understand what we mean.

    Dear Icomp,


    Thank you for this device, it is absolutely sensational. The GUI is ok but can be quite confusing.


    Question:

    * When configuring game resolution settings, I found this process quite confusing -

    - I was not sure what resolution in the GUI related to game resolution, which is something like 320x400? So I loaded some games and noticed that in the indivision watermark area, it would tell me: 800x600 PAL - 800x600 VESA. So I am reading this as: Indivision is sensing the game resolution as 800x600 and is choosing the suitable 800x600 VESA profile?

    - Okay - that doesn't make sense to me, but okay, it thinks games are 800x600. I fine-tune the 800x600 VESA profile to my liking and get all games centered, but VSYNC doesn't work.

    - I experiment by choosing a higher res, 1280x1024 EDID, this works very well and looks even sharper for games. VSYNC also seems to be working.

    - I experiment with my monitor native res, 1600x1200 EDID, but the display cannot sync properly and keeps flashing on and off, although this is from the EDID? Strange.


    So why does the MK3 think the input resolution from games is 800x600, why not 320x240 etc? And is it possible to use my monitor native res of 1600x1200 with VSYNC, with display sync properly.


    Monitor is: NEC 2090UXi, using HDMI>DVI.


    Cheers.

    As feedback for developers I also suffered some frustration as I had no idea how to flash the firmware in the GUI. I used the shell method instead, which was a little more scary but worked. No where is there a mention of right click menu in the docs, it would have saved me some stress :)


    But overall thank you all for your hard work, I am exceptionally pleased and Icomp has never let me down (fairly new to Amigas, have 1233n Accel and now agamk3)