Welcome to the Picasso96 FAQ!

Please read the documentation, too!

1. Q: I have problems getting a small mode like 320x200 to work with my CyberVision 64. What can I do?
   A: The default modes might be too small for your card. Try to increase the horizontal and vertical totals by a few percent.
   
   
2. Q: It aint much but why is my mosepointer's colors being somekind of inverted when passing over colored areas of screens in almost any depth?
   A: That's a limitation of many VGA chips. They have only two real mouse colors and one inverting "color". On the PC, normally only two colors are needed so that's ok for them.
   You'll have to paint yourself a two colored mouse sprite, switch to software sprite or live with it. Sorry!
   
   
3. Q: I have problems using IFF pictures with FastIPrefs, WBPattern or Multiview. What can I do about it?
   A: You can improve the situation by running CPUBlit. If you want to use CPUBlit, put it in your Sys:S/Startup- Sequence before the monitors are started. The line must look like that: 'CPUBlit -a -b'.
   
   
4. Q: I already have a settings file for CyberGraphX or the old Village system which I want to use. What can I do?
   A: The PicassoModeTNG by Olaf Barthels can load those settings.
   
   
5. Q: Why are there some strange wrong colors on HiColor and TrueColor screens?
   A: Because Picasso96 currently does nothing about DisplayBeep() which changes the background color for some time which is not visible on Hi-/TrueColor screens but affects all rendering during that time. This will be fixed, soon.
   
   
6. Q: Why do all my icons flicker when moved around on a Picasso96 screens?
   A: With Picasso96 icons are not moved beamsyncronized. The icon is first cleared out at its current position and then redrawn at the new position.
   As a matter of fact, for a short amount of time the icon is not visible. This causes the flicker unless it happens in the vertical blanking period. Currently Picasso96 moves icons without waiting to be as fast as possible.
   
   
7. Q: Why does PhotoGenics display only a strange black-and-white screen when trying to open a HiColor screen?
   A: That's because PhotoGenics incorrectly tries to open a screen with depth=0... use a screen promotor and tell it to open with depth=16...
   
   
8. Q: Why is depth arranging of SMART_REFRESH windows slower than with other graphics board software?
   A: This is because we do not yet replace layers.library by custom code. But we are on the way to do that, too. Please, give us some time as layers.library is not easy to understand and reimplement. If the programmers of the layers.library had called SwapBitsClipRectRastPort() via its library vector offset, it would be just a matter of minutes to speed layers up, but the way they did it, it will take weeks... :-(((
   
   
9. Q: I don't like the settings supplied with Picasso96 because they do not use the bandwidth my monitor likes or I would like to get better modes. What can I do?
   A: There are two alternatives:
   1. Use Picasso96Mode and either create new modes or alter the pixel clock of the existing ones, test the modes, save and reboot.
   2. Look at the Picasso96Settings web page and look if there is one for you...
   
   
   
10. Q: Why is it that I can not use TrueColor modes with the CyberVision64?
    A: The cards supported by Picasso96 have different color formats:

    Cards and their supported color formats

    Card	Planar	Chunky	HiColor15	HiColor16	TrueColor	TrueAlpha
    CV64	-	+	+	+	-	+
    Domino	+	+	+	-	-	-
    Merlin	+	+	+	+	+	+
    oMniBus	+	+	+	(+)	(+)	(+)
    PicassoII(+)	+	+	+	+	+	-
    PicassoIV	-	+	+	+	+	-
    Piccolo	+	+	+	+	+	-
    PiccoloSD64	-	+	+	+	+	+
    Spectrum	+	+	+	+	+	-

    So, the CyberVision can not use 24 bit TrueColor modes but has 32 bit modes with an (unused) alpha channel.
    
    
11. Q: I defined my own display modes, but some of them seem to have problems with the hardware sprite (of my Cirrus based board). It either disappears at the right side of the display or there are some strange pixels when I move the mouse sprite to the top of the screen.
    A: The mode you created does not give the VGA chip enough time to fetch the sprite data during horizontal retrace. You will have to increase the horizontal totals by a few pixels and move the display to the left. You can check this in the edit and test screens of Picasso96Mode, too.
    
    
12. Q: Some of my pictures and images are not rendered correctly.
    A: Maybe some of your datatypes might be incompatible. We currently have tested and can advise the use of:
    • Matthias Scheler's datatypes:
      • ilbm.datatype 43.5 (c) 1995-1996 by Matthias Scheler
      • gif.datatype 43.12 (c) 1995-1996 by Matthias Scheler
      • jfif.datatype 43.8 (c) 1995-1996 by Matthias Scheler
      These can be found in the "util/dtype/PictDT43.lha" archive available on Aminet. The GIF datatype must not be distributed anymore due to licence problems with Unisys who own the patent for the algorithm!
    • Andreas Ralph Kleinert's datatypes:
      • akJFIF.datatype 43.24 (01.02.97)
      • akPNG.datatype 43.15 (05.02.97)
      • akSVG.datatype 43.14 (01.02.97)
      • akGIF.datatype 43.7 (07.12.96)
      These can be found in the "util/dtype" directory of Aminet. The GIF datatype must not be distributed anymore due to licence problems with Unisys who own the patent for the algorithm!
    
    
    
13. Q: The supplied v43 picture.datatype has a smaller revision number than the CyberGraphX picture.datatype. Which one should I use with Picasso96?
    A: The picture.datatype supplied with Picasso96 is completely different to the one supplied with CyberGraphX. The Picasso96 picture.datatype works with Picasso96 and CyberGraphX, but the CyberGraphX picture.datatype works only with CyberGraphX. So, you will have to use the Picasso96 picture.datatype.
    
    
14. Q: Why is it, that NewIcons icons are rendered incorrect when I use the option RTG?
    A: This mode is not compatible with Picasso96.
    
    
15. Q: Why is there no screen dragging with Picasso96?
    A: Hmmm, the sad thing is: VGA chips do not have the features the Amiga Copper offers. There are too many restrictions:
    • you can do split screen, but you can only show two screens at the same time,
    • the screen width and RGB formats have to be the same, or it will look very strange,
    • if both screens are chunky they should use the same palette or it will...
    • the base address of the second screen must be 0 (ZERO), i.e. when this is not the case, then you will have to move the screen to that position. But this interferes with the memory management of Picasso96...
    
    
    
16. Q: Which programs are known not to work with Picasso96?
    A: Currently, these seem to be:
    • DPaintV crashes due to the fact that it manipulates the bitmap itself, ignoring that the display might be on a chunky screen. The only solution is to create or activate planar modes and use DPaint with at most 16 colors.
    • ImageFX (may lock up).
    • HippoPlayer seems to crash on various installations.
    
    Please tell me what to add... :-\
    
    
17. Q: Will there be support for the Retina Z2 or the Retina BLT Z3?
    A: Yes, support for the Retina BLT Z3 is on the way (nothing to test yet, though). Support for the Retina Z2 is planned and will be started as soon as we support segmented boards.
    
    
18. Q: My mouse pointer looks trashed. Why?
    A: You might have set the sprite resolution to hires in the Pointer preferences. This is not compatible yet. Does not make sense for Picasso96 either... Will be supported in the future.
    
    
19. Q: How can I create new resolutions for Picasso96?
    A: You'll have to use Picasso96Mode. Here is how:
    • start Picasso96Mode,
    • click on the top left gadget (the "New object" gadget) and you will see a new object attached to your mouse sprite,
    • drop this new object into the resolution list (lower left part of the display), once the name of the object changed to "New resolution",
    • change the resolution size to 640x400 or whatever you like,
    • get another new object (see above), drop it in the modes list (upper right part of the display),
    • click "Test",
    • if not satisfied, click "Edit" and change the mode (no, this was never meant to be really easy... :-))
    • if you want similar modes for Hi- and TrueColor, copy the mode you just created and change the depth cycle, re-test and so on...
    • save and reboot.
    
    
    
20. Q: How can I copy resolutions or modes for Picasso96?
    A: You'll have to use Picasso96Mode. Here is how:
    • click on the list item you want to copy,
    • move the mouse to the left or right while still pressing the left mouse button (!!!). Don't be too slow or it won't work! You should see an object attached to your mouse sprite,
    • drop the object over the third of the top-left gadgets (the copy gadget) and you'll see a copy of the object appear in the list view where you took the first object.
    
    
    
21. Q: How can I delete resolutions or modes for Picasso96?
    A: You'll have to use Picasso96Mode. Here is how:
    • same as copy, just use the fourth top-left gadget. WARNING: there is no "Undo" button!
    
    
    
22. Q: Picasso96Mode: how can I activate or deactivate a mode or resolution?
    A: Double click the list entry.
    
    
23. Q: Some of my old Village drivers are behaving strangely or crash. Why?
    A: We really suggest that you get rid of them. The old Village API is a pile of ... :-(
    Please use the Picasso96 drivers or try the CyberGraphX ones!
    
    
24. Q: The documentation says, KickStart 3.1 is needed for Picasso96. Why?
    A: Because KickStart 3.1 offers some basic RTG functionality not available under KickStart 3.0. This results in less patches and a higher level of compatibility.
    
    
25. Q: How can I tell the version of Picasso96 I currently have?
    A: In the root directory of the archive or disk you got is a file called version. From a shell window, do "version <path>Version" or simply "type" this file. This file does not exists on the November 96 demo disk, but on all later releases.
    
    
26. Q: I installed Picasso96, but I don't get any screen modes. What's wrong?
    A: The settings files which are currently supplied assume a PicassoIV board. If you have another one, start Picasso96Mode, select the menu "Attach setting to" and choose your board (should be the last line of the menu. If your board does not appear, the monitor file has not been started or is misconfigured (check tool types of Sys:Devs/Monitors/<YourBoardName>).
    
    
27. Q: Why are screens with up to 16 colors so slow on fast Amigas?
    A: Because on most cards, these screens are planar. If you want to speed them up, disable the planar modes with Picasso96Mode.
    
    
28. Q: Why is the scrolling speed of the Picasso II, Piccolo or Spectrum less than under the old Picasso, CyberGraphX or EGS software?
    A: This is because the Picasso96 software normally respects the rastport and blit masks which requires multiple blits to be performed. If you want to speed up blitting, add a tool type "IgnoreMask=Yes" in your Devs:Monitors/PicassoII, Piccolo or Spectrum icon. Be warned though that this mode may result in incorrect rendering.