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.
-
Thanks Jens. I'm seeing a Tooltype in the docs for SwitchType=JAVOSOFT that indicates a switch from graphic card to Amiga video. Not clear on the docs how this is working (or what result I should see).
Separately, I was remembering CGX allowed native Amiga NTSC mode. I went back to install CGX4 to see and indeed NTSC amiga video is available. I'm not sure how they achieved it....
-
Thanks Jens for the information -- for the 3.0 version that I downloaded 2-3 months ago, it doesn't have that information. I unfortunately can no longer download any recent one as my 1 year I think is up.
I'm somewhat disappointed as I have a second graphic card (ZZ9000) that has a good scan doubler and trying to see if I could use 2 monitors. With the FAKENATIVE, it seems like NTSC will not come to the Amiga output. Programs like VistaPro also doesn't show up well on the FAKENATIVE screens, unfortunately. This is just some feedback in case there is some possible future way for a safe workaround. I suppose OS4 CVisionPPC is doing it because it completely bypasses the P5 FW?
-
I have the FAKENATIVEMODES=No but screenmode prefs requester still lists these and the NTSC ones are removed from the screenmode list.
-
I'm getting "Could not create graphics board context for 'CVisionPPC', please check your Picasso96 installation." After I manually, copied the permedia chip file then driver got loaded okay. So seems like install script missing copying that file.
-
-
Another observation..:
1) From a P96 screenmode Workbench, I launch PDraw. It opens up an Amiga NTSC interlaced screenmode.and is flicker fixed on PIV. This is working fine.
2) I then go back to Workbench and launch the Toaster. It opens up its own Amiga screen. No corruption on Toaster screen when toggling between PDraw, Toaster, and P96 Workbench. However, the P96 RTG WB screen does get corrupted.
4) Then I close PDraw.
5) I go back to Toaster screen and it is then corrupted like the original screenshot above.
-
I tired the version on Aminet and also a 2.1 install version. In the 2.1 install, there is this readme that shows change log to 2.0. Both versions still see the corruption of screen when screen toggles between flickerfixer to RTG. Haven't found any version log from 2.0 to 2.2 yet.
I then tried cybergraphx4 and with that one it is working okay and I don't see screen corruption between toggles of Amiga NTSC flicerfixer output and RTG screenmode . So this does not look like a hardware issue/failure.
Another data point is that I saw this screen corruption on a ZZ9000 board as well. I need to put that card back in -- a much better flickerfixer experience on modern monitors!
-
Yes, 24-bit showing same as 16-bit. The pointer itself is okay and just the preview boxes. I tried cybergraphx4 and actually saw same issue. So looks like this is particular to the pointer prefs editor with RTG >8bit modes.
-
The flicker fixer on the PIV is able to sync with the toaster. The ToasterScreenAfterOpeningAmigaScreen.JPG screenshot is from the PIV flicker fixer -- though I had to start the toaster software from a Amiga NTSC Workbench screenmode.
The issue comes up when switching between P96 (RTG) screen mode and the flicker fixer. -- this is when the screen corruption happens.
If I have a chance will try an older version of the P96 software.
-
SOFTSPRITE tooltype looks better. I did notice a separate thing in the rendering in the pointer prefs menu. In the preview boxes when in 16bit PC or 24bit BGR modes, there are different colors being shown for the preview pointer.
-
Thanks Jen. I was taking a look at the change log and mentions this for the RetinaBLT/Draco only...
https://aminet.net/package/driver/video/Picasso96
- RetinaBLT Z3 and Draco Altais (NCR chip driver changes by Jürgen
Döffinger):
- small changes with masked blits (less overhead).
- implemented hardware support for BltPattern.
- hardware sprite uses color 3 as inverted color now (unlike all other
cards).
Once I have time, I will try the softsprite option
-
For that last screenshot, this was a 640x480 8-bit screen. I've tried other screenmodes like 800x600 24-bit BGR and see similar.
-
Thanks -- you are right -- shouldn't mix OS4 stuff with P96 for OS3.x. This is just a suggestion to include standard VESA timings in the Picasso96Settings file that is created during install. For example, these settings show up in a Dell Monitor monitor that have the basic preset modes that are VESA standards.
https://www.bhphotovideo.com/lit_files/280644.pdf
-
Hopefully, this picture is more clear. I used the pointer prefs to make a bigger pointer to show the affect of what is happening. Pointer color is suppose to be grey, red, black, tan.
As you can see there is some kind of alpha happen to pointer. The black text in the pointer prefs goes through the pointer and shows up white.
-
I'm having some issue in starting a Toaster screen when Workbench is a P96 screen. If I have Workbench in Amiga video, than Toaster works okay. This is with a PicassoIV card. Also, the P96 screen can get corrupted as well.
-
I'm attaching 2 photos of the mouse pointer that I've seen on both a PicassoIV card and a Cybervision64 card running with P96.
One image is the pointer over a grey background and is good. Once I hover the pointer over a white area of the screen the outer fringes of the pointer graphic disappear.
I have not set the SOFTSPRITE (so I assume that is "No" for default)
-
I was having some issues with the "picasso96Settings" that were setup for my graphic card that was done during the software installation. They were not working with the monitor I was using When I used the following standard VESA ones, it worked much better. Would be great to have this included in the package.
https://forum.hyperion-enterta….com/viewtopic.php?t=2008
-
Are these problems possible with an A4000T -- i have been experiencing artifacts but not sure if same issue or not. If I have a chance, I will try to post a picture of it.