Replies: 2 comments 4 replies
-
|
Converting pngs to dds is a real pain, and also slow. Would be better to force the user to use dds honestly. |
Beta Was this translation helpful? Give feedback.
-
|
do we know how to combine dds? |
Beta Was this translation helpful? Give feedback.
-
|
Do we know how to convert png to dds properly without texconv? |
Beta Was this translation helpful? Give feedback.
-
|
problem with forcing dds is that dds has multiple compression types, so users have to make sure they use the right one, and certain programs export dds differently / plain wrong at times. |
Beta Was this translation helpful? Give feedback.
-
|
Hmmm, I wonder if we could add a parser to FlightCore or VTOL or something that can double check that and give instructions on how to fix if it's the wrong compression type. |
Beta Was this translation helpful? Give feedback.
-
|
Image for the idea itself (thanks github cdn) |
Beta Was this translation helpful? Give feedback.
-
Hello frens,
after long consideration i bring forth an idea on something that, sooner or later will need to be handled i think.
Something i call "RIA" - "Runtime Image Atlas"
In order to circumvent the Atlas limit we have.
A Unified image atlas built by Northstar at launch, using ressources from all mods that want to add to said atlas.
This small pitch aswell as thought experiment is structured into 3 parts
Usecases:
With smaller recent talks on stuff like persistence, rewrites and more people asking about how to mod certain ingame images that are packed into image atlases i believe a solution for the image atlas problem should be investigated.
Image Atlases are needed for:
UI (weapon icons on screen, ui elements)
Calling cards
other RUI stuff
It would allow easy access to custom icons for custom weapons/abilities/titans without having people build their own atlas in a long process which will just fill up a slot in our very limited space of atlases.
The HOW:
Mod authors would have to add each image as a field inside their mod.json, in a fashion somewhat to what is shown below.
On launch northstar would now do the following:
Check if a image atlas has been built before, if not > build
Building this Atlas would involve the following:
Get all mods that want to add to said atlas,
build the atlas image itself (the tiled image consisting of all other images)
converting it.
Authors would supply their images as PNG files, Northstar would convert the final imaget to the DDS file. and build the rpak for it.
Problems:
Investigate efficient tiling for the images (?preexisting tiling code from mrvn radiant?)
Max directX image size that is allowed? How big, how much before we hit it, what if we hit it?
Build straight to Memory, not even saving as RPAK. (idea: Blue) needs RE
Beta Was this translation helpful? Give feedback.
All reactions