No, it's not just you—most of us have this issue. It was reported several times and rejected. Initially, it started after a commit a few years ago, and I reported it immediately. However, it was incredibly difficult to explain repeatedly what was happening and where the bug was—even when I provided video evidence and explained it in various ways with different approaches. Yet, each time, it was dismissed as if nothing was wrong. Then others reported it, and I brought it up again. Nothing changed. More recently, some people on os4depot reported it, and I highlighted it once more—still no response.
Every report about this issue is treated as if we (or I) are attacking without reason, when it's simply a legitimate bug report that, for some unknown, irrational, and illogical reason, keeps being ignored.
I pointed to LiveForIt exactly which commits introduced the issue (I don’t remember the commit number now, but it’s in the old thread about uae-improvements on amigans). The proper approach would be to understand what was changed, create a test case, test it on different machines, and then implement the fix correctly. But that requires a willingness to acknowledge the issue and trace the root cause in the code that broke things.
In other words, don’t get your hopes up. I’m only writing about it again—and again—holding onto a faint hope that LiveForIt will finally accept that there’s a problem, instead of simply saying, “It works on my X1000,” and actually try to create a small test case or investigate where the issue lies.
Because if this is being done for users, shouldn’t bug reports be accepted? If it’s only for personal enjoyment, then why make it public and avoid reports?
you have talent to fix it your self, and the hardware with the issue.. why can't you fix it?
My hardware can’t reproduce issue.
In any case.. anyone can build SDL version, if they want that version of UAE, I’m not working on that version of UAE, its a different build, only few different compiler switches.
(NutsAboutAmiga)
Basilisk II for AmigaOS4 AmigaInputAnywhere Excalibur and other tools and apps.
First of all I’m not sure what color issue we are talking about, sense different color issues has been reported in the past, its not easy to know sense, people are not explicit about issues, and there no screenshots, no information about screen modes or anything, no logs from EUAE. I'm not a mind reader... no body is using the bug tracker on GitHub..
As for the issue I think most people are having... it might depend on the RGB mode used, your configuration and your graphic card. so it might not even show up on the same hardware.
(NutsAboutAmiga)
Basilisk II for AmigaOS4 AmigaInputAnywhere Excalibur and other tools and apps.
I'm not if this is what others are experiencing, but this is what I noticed:
Conditions:
1. uaegfx video mode set in emulation. .uaerc - gfx_fullscreen_picasso=yes gfxcard_size=32 2. Picasso screen mode in emulation (in my case AOS3.9) and E-UAE set to same color mode (say 32bit ARGB, ARGB32).
Result:
Colors that are, how to describe it? Wonky? Um almost like there's a purple multiplier filter applied to the entire application. Text is also blurry and almost impossible to read.
Workaround:
Set UAE to display video mode requester and set screen mode from the requester to ARGB32 and the emulated Picasso screen mode to 16bit. .uaerc - amiga.screen_type=ask
I don't know, maybe color channels getting swapped somehow?
If anyone can tell me how to create and post a screen shot of E-UAE I can try to do that.
As installing version 0.8.29 the color problem went away, I thought something could be wrong but not necessarily in the code. I understand that if you don't have the issue, it's not easy to understand/fix it.
I can do more tests and provide better understanding of the problem. Will do so over the week-end.
this should show all option, you should enable akiko, I have not.. some files need to edited, and configure script fails to sett correct sizes for LONG and LONG LONG and so on..
I think you need to edit makefile to enable bsdsocket, it might not be needed, if did not configure it correct.
(NutsAboutAmiga)
Basilisk II for AmigaOS4 AmigaInputAnywhere Excalibur and other tools and apps.
If I remember correctly, the EUAE amigfx version never supported Picasso96. His work made it work. There may be some problems, but... you can always build your own version or use older compilations. It is definitely not a replacement for RunInUAE (amigfx).