Felipe Granado
Registered
Hello!
It's been a while since I created a topic here, but doing some research, I realized that it might be relevant to make some suggestions.
In conversation with ChatGPT to understand .DDS files:
Me: Hi.
Please tell me what are the rules for height and width when saving .DDS texture files.
GPT: .DDS (DirectDraw Surface) texture files are commonly used in game development and computer graphics due to their ability to store textures with both lossy and lossless compression. The height and width dimensions of a .DDS file can vary depending on the specific needs of your project and the hardware you intend to use it on. However, there are some general guidelines you can consider when saving .DDS texture files:
Me: So, according to answer 3, can I save dimensions of 2:1 and work for my software to read a maximum of 512x256 with high compression, to have little hardware consumption, right?
Assistant: Yes, you understood correctly. If you have a texture with a 2:1 aspect ratio, such as 1024x512 pixels, and want to minimize hardware consumption, you could compress that texture and limit its maximum resolution to 512x256 pixels.
By using high compression, such as the DXT1 or DXT5 format, you'll reduce the file size of the texture, which can help save video memory and improve the performance of your application or game. By limiting the maximum resolution to 512x256 pixels, you'll also further reduce hardware resource consumption, which can be beneficial, especially for devices with limited graphics capabilities.
Therefore, adjusting the resolution and compression of textures is a common strategy to optimize performance and ensure a smooth experience for users, especially on devices with limited resources. Just make sure to balance the desired visual quality with the performance constraints of the target hardware.
With that, I have a question: Would it be possible for rf2 itself to take the texture of the paintings we produce and create a .DDS texture-only file that can be used in the broadcasts overlay? It would save leagues, teams and drivers a lot of work in producing multiple images of multiple cars, minimizing errors and optimizing the software.
I imagine the sim having a 2d version of the car and could provide a template. The "new texture" could work with different resolutions, with good compression, leaving an option to configure the LODs in an .ini file, for example.
This way, the Overlay files would be ready to be used.
I sincerely hope that these questions can spark an interest in delving deeper into this topic with a view to improving it for all of us.
If you read this far and this made sense to you, could you like this post? We could get an idea from the community about this topic.
Best Regards,
It's been a while since I created a topic here, but doing some research, I realized that it might be relevant to make some suggestions.
In conversation with ChatGPT to understand .DDS files:
Me: Hi.
Please tell me what are the rules for height and width when saving .DDS texture files.
GPT: .DDS (DirectDraw Surface) texture files are commonly used in game development and computer graphics due to their ability to store textures with both lossy and lossless compression. The height and width dimensions of a .DDS file can vary depending on the specific needs of your project and the hardware you intend to use it on. However, there are some general guidelines you can consider when saving .DDS texture files:
- Power of Two: Often, textures in games and computer graphics have dimensions that are powers of two, such as 128x128, 256x256, 512x512, 1024x1024, etc. This is because many GPUs (Graphics Processing Units) operate more efficiently with textures that have power-of-two dimensions. However, many modern GPUs support textures with non-power-of-two dimensions, so this isn't as strict a restriction as it used to be.
- Hardware Compatibility: When creating textures for a specific game or application, it's important to consider the hardware limitations of your target audience. Some devices may have specific restrictions on the maximum dimensions of textures that can be efficiently loaded.
- Aspect Ratio: The aspect ratio of textures should be maintained to avoid distortion when applied to models or surfaces. For example, if a texture has a resolution of 1024x512 pixels, this means it has a 2:1 aspect ratio.
- Performance Considerations: Very large textures can consume a lot of video memory and impact application performance. Therefore, it's important to balance the desired visual quality with the performance limitations of the target hardware.
- Compression Format: The DDS format supports a variety of compression algorithms that can reduce file size and optimize performance, such as DXT1, DXT5, etc. The choice of compression format may also influence the maximum and minimum dimensions of the texture.
Me: So, according to answer 3, can I save dimensions of 2:1 and work for my software to read a maximum of 512x256 with high compression, to have little hardware consumption, right?
Assistant: Yes, you understood correctly. If you have a texture with a 2:1 aspect ratio, such as 1024x512 pixels, and want to minimize hardware consumption, you could compress that texture and limit its maximum resolution to 512x256 pixels.
By using high compression, such as the DXT1 or DXT5 format, you'll reduce the file size of the texture, which can help save video memory and improve the performance of your application or game. By limiting the maximum resolution to 512x256 pixels, you'll also further reduce hardware resource consumption, which can be beneficial, especially for devices with limited graphics capabilities.
Therefore, adjusting the resolution and compression of textures is a common strategy to optimize performance and ensure a smooth experience for users, especially on devices with limited resources. Just make sure to balance the desired visual quality with the performance constraints of the target hardware.
With that, I have a question: Would it be possible for rf2 itself to take the texture of the paintings we produce and create a .DDS texture-only file that can be used in the broadcasts overlay? It would save leagues, teams and drivers a lot of work in producing multiple images of multiple cars, minimizing errors and optimizing the software.
I imagine the sim having a 2d version of the car and could provide a template. The "new texture" could work with different resolutions, with good compression, leaving an option to configure the LODs in an .ini file, for example.
This way, the Overlay files would be ready to be used.
I sincerely hope that these questions can spark an interest in delving deeper into this topic with a view to improving it for all of us.
If you read this far and this made sense to you, could you like this post? We could get an idea from the community about this topic.
Best Regards,