Weird info from p96GetModeIDAttr()

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.
  • It is correct and desired that the P96API call returns 24 bits per pixel. It's the number of bits that actually have an influence on colour. If you want to get the total number of bits per pixel, there is a tag called DEPTH (also mentioned in the API documentation). It is two separate things you need to keep in mind: Number of colours and encoding width may or may not be different, depending on screen mode and graphics card.


    For pixel formats with padding-data, you have a depth of 32 bits, but only 24 bits that have a meaning. So again, your output is expected and desired to describe reality in required detail.

  • It is correct and desired that the P96API call returns 24 bits per pixel. It's the number of bits that actually have an influence on colour. If you want to get the total number of bits per pixel, there is a tag called DEPTH (also mentioned in the API documentation). It is two separate things you need to keep in mind: Number of colours and encoding width may or may not be different, depending on screen mode and graphics card.


    For pixel formats with padding-data, you have a depth of 32 bits, but only 24 bits that have a meaning. So again, your output is expected and desired to describe reality in required detail.

    Thank you for answer

  • The last reply was more than 365 days ago, this thread is most likely obsolete. It is recommended to create a new thread instead.