P96 v3.0

Le nostre news in homepage

P96 v3.0

Messaggioda AMIGASYSTEM » mar ott 27, 2020 8:56 am

Immagine



P96 3.0: Nuova versione del pacchetto software RTG per Amiga "Picasso96" ora solo "P96". Trattasi ora di un software commerciale, tra le tante novità che trovate in elenco, il trascinamento dello schermo, compreso l a discesa dell'intero schermo con la possibilità di visualizzare un secondo schermo, aggiunti driver per CyberVision con compatibilità API Warp3D

Tutte le novità di P96 3.0:

- This is a BIG change. This release provides one new (important) feature, and that is screen dragging. It requires support from the chipset, namely the VGA line compare register, and updated drivers to include the new API.
- Drivers for the Cirrus chips, the S3 chips, the NCR chip and the Tseng chipset have been updated accordingly to provide the new API.
- Note that screen dragging has certain restrictions that all stem from the limitation of the VGA chips and the corresponding boards:
- There must be enough memory to hold at least two screens in the graphics card memory.
- The two screens must share the same pixel layout (i.e. truecolor, hicolor or indexed colors)
- The colors of the topmost screen will not be correct for indexed screens as VGA chipsets do not include a copper, hence only one palette can be loaded at a time.
- Autoscroll screens that allow horizontal panning cannot be dragged. Thisis a limitation of the VGA panning mechanism.
- Planar screens (16 colors planar) can only be dragged if the depth is
identical.
- At most two screen can be displayed at once, with the top most screen being aligned to the top of the monitor.
- Memory management is completely new. In particular, P96 attempts to keep screen on the board if possible. The older code could have erraneously removed special features from the board without deactivating them first.
- Memory management for planar modes was completely broken. It always allocated 4 times as much memory as requested. Instead, it should have limited the memory to the available legacy VGA max memory of 256K.
- Updated the chip API to allow signalling of max planar memory.
- Bitmap allocation and management was cleaned up a lot, going now through a unified allocator, and modularized functions quite a bit.
- In case bitmap allocation failed, a proper error code is now reported back to intuition V47.
- Intuition V47 communicates now colors into P96 which allows proper backfilling of true color and hi-color bitmaps, without peeking into private intuition structures.
- Bitmap on- and offloading had a bug and failed to safe back bitmaps to be off-loaded in some cases. In particular, the bitmap allocation and offload checking could have disagreed, removing a bitmap from the board even if not necessary.
- Memory mode handling was fixed. The old code could have attempted to fill a bitmap with a color with the previous mode still active, causing defects when switching from planar to chunky or reverse.
- Undersized true-color screens are now filled with the background color to reflect what palette modes would do.
- Cursor drawing on undersized bitmaps was fixed. The cursor can now enter the out-of-bitmap areas, except for planar bitmaps. This allows proper scrolling of the upper screen in split-screen arrangements.
- Pixel aspect ratio computation was always assuming a 4:3 screen, eventhough VGA knows other aspects, such as 5:4, or (today) 16:9 and 16:10. This release tries to be smart and guess the right monitor screen ratioto create "nice" pixel aspect ratios.
- Aligned bitmaps are now aligned to MMU page sizes (not necessarily 4K), and waste less memory.
- Flood fill failed on rastports larger than 1024x1024 pixels. It was also optimized a bit.
- Disabling the Amiga blitter unfortunately also disabled native VSprites, even though Bobs remained working. Now VSprites operate indepedent of Bobs.
- Made some minor improvements in BltPattern and Area functionst to use proper rounding. This cuts the code size down a bit.
- Palette update for planar modes was partially broken and could overwrite
some colors.
- If the depth of a planar mode was changed, it could happen that the code forgot to update the sprite colors.
- The Cirrus542x and Cirrus5446 drivers did not enable the double vertical flag correctly. If double scan is set, the critical limit
is already at 512 lines, not 1024 lines. The Cirrus5434 driver did this correctly already.
- The S3Virge and S3Trio chip drivers now support overclocking. To enable this feature, add the OVERCLOCK=yes tooltype to the monitor icon.
Beware! Overclocking may result in artefacts, pixel noise and potentially reduced life time of the graphics chips due to overheating. No warranty, and use at your own risk.
- The pixel clock adjustment functions for the Tseng-chips are now set to no-ops instead of letting the CPU run into a crash when the rtg.lib attempts to use them.
- In case an overly large sprite is requested, the sprite height is now clamped before attempting to load it into the hardware.
- As LoadRGB32() and SetRGB32() are implemented over the VecTable anyhow, both functions do not require patching, thus the superfluous patch was removed. Also, some programs called SetRGB32() or LoadRGB32() incorrectly within an interrupt. The rtg.library includes now precautions to ignore such calls instead of crashing.
- The CyberVision driver forgot to remove the int server again in case no memory was found on the board.
- New chips and card drivers are included in this release. The CVisionPPC and 3DLabsPermedia2 drivers are new in this release.
- DisplayAlert() did not remove the hardware sprite from the display and did not time the alert properly. The alert could be gone so fast that you could not read it.
- CalculcateBytesPerRow() can now return 0, indicating a failure. This may be used to indicate that a bitmap is too wide for a particular chip. For example, the Cirrus chips cannot take bitmaps wider than
4096 bytes (not pixels!)
- The computation of the P96 video mode pixel sizes is now a lot smarter and not only uses the width and height of the video mode, but tries to guess the target monitor aspect ratio (5:4,4:3,16:9 to name some of the candidates). Provided your monitor is adjusted correctly, this would give more reliable results.
- As intuition privates changed in Os 3.2, the hires sprite pointer is no longer available in this version of the Os. Also, you should not attempt to drag screens with the right Amiga key as this may leave intuition in a confused state. Works ok in 3.1.4 and below.
- Added the mntmn graphics cards to P96Mode and the board info name enumeration.
- Fixed a MuForce hit when a user attempts to attach board to a non- existing settings in P96Mode.
- Added mntmn graphics cards to P96Mode.

I want to thank all the people that contributed to make this possible, all the testers, and in particular to Harald "Rotzlöffel" for lending me his CVisionPPC equipped A1200 without which the CVisionPPC driver could not have been completed.
Allegati
Picasso96.jpg
Immagine - AfA One - AfA One PPC - AROS One x86 - AROS One 68K - WinUAE OS 4.1 -

Miei AMIGA
Amiga 4000/Cyberstorm MK II/060/Picasso RAM 6MB Kick 3.1
Amiga 1200/030 Ram 16 Mega HD 500 MB
Amiga 1200/040 Ram 32 Mega HD 500 MB
Amiga 600 HD 20 MB
Amiga 600 Doppio Kickstart 2.05-1.3
Amiga 500 Plus Doppio Kickstart 204-1.3
Amiga 500
CD32/SX-32 MK1 RAM 8 MB HD 4G
CD32 Standard
Avatar utente
AMIGASYSTEM

Staff
 
Messaggi: 3974
Iscritto il: ven lug 25, 2008 8:39 pm
Località: Brindisi

Re: P96 v3.0

Messaggioda AMIGASYSTEM » ven nov 13, 2020 10:02 am

Qualcuno ha utilizzato questa nuova libreria? una delle caratteristiche è quella di poter abbassare lo schermo anche su schermi RTG come mostrato QUI
Immagine - AfA One - AfA One PPC - AROS One x86 - AROS One 68K - WinUAE OS 4.1 -

Miei AMIGA
Amiga 4000/Cyberstorm MK II/060/Picasso RAM 6MB Kick 3.1
Amiga 1200/030 Ram 16 Mega HD 500 MB
Amiga 1200/040 Ram 32 Mega HD 500 MB
Amiga 600 HD 20 MB
Amiga 600 Doppio Kickstart 2.05-1.3
Amiga 500 Plus Doppio Kickstart 204-1.3
Amiga 500
CD32/SX-32 MK1 RAM 8 MB HD 4G
CD32 Standard
Avatar utente
AMIGASYSTEM

Staff
 
Messaggi: 3974
Iscritto il: ven lug 25, 2008 8:39 pm
Località: Brindisi

Re: P96 v3.0

Messaggioda Seiya » ven nov 13, 2020 2:04 pm

da un prodotto commerciale mi aspetto una compatibilità migliore e prestazioni più elevate rispetto alla versione 2.x e anche una migliore interazione con Warp3D e WarpOS.
Abbassare lo schermo è solo una caratteristica per impressionare le folle e i media, ma utilità zero se i driver 2D e 3D sono a livello amatoriale.
Seiya

Supremo
 
Messaggi: 3393
Iscritto il: sab lug 04, 2009 11:22 pm

Re: P96 v3.0

Messaggioda AMIGASYSTEM » ven nov 13, 2020 5:51 pm

Si ci sono anche altre incompatibilità come su Shapeshifter e pare anche con la sheda video SAGA dove sembra non si possa abbassare lo schermo.
Io sto utilizzando la versione 2.4.6 dove non è possibile abbassare lo schermo e dove ho riscontrato un piccolo artefatto su AmiStart, risolto sostituendo una libreria con una precedente.
Immagine - AfA One - AfA One PPC - AROS One x86 - AROS One 68K - WinUAE OS 4.1 -

Miei AMIGA
Amiga 4000/Cyberstorm MK II/060/Picasso RAM 6MB Kick 3.1
Amiga 1200/030 Ram 16 Mega HD 500 MB
Amiga 1200/040 Ram 32 Mega HD 500 MB
Amiga 600 HD 20 MB
Amiga 600 Doppio Kickstart 2.05-1.3
Amiga 500 Plus Doppio Kickstart 204-1.3
Amiga 500
CD32/SX-32 MK1 RAM 8 MB HD 4G
CD32 Standard
Avatar utente
AMIGASYSTEM

Staff
 
Messaggi: 3974
Iscritto il: ven lug 25, 2008 8:39 pm
Località: Brindisi


Torna a News e rumors

Chi c’è in linea

Visitano il forum: Google Feedfetcher e 11 ospiti

cron