Difference between revisions of "Talk:Xtf"
From xboxdevwiki
(→Add file format info: new section) |
(→Add file format info) |
||
| Line 9: | Line 9: | ||
from #xqemu irc channel | from #xqemu irc channel | ||
| − | JayFoxRox: I looked at the file, it seems to be a 2D mesh format, indices, followed by vertices | + | * JayFoxRox: I looked at the file, it seems to be a 2D mesh format, indices, followed by vertices |
| − | JayFoxRox: header is XTF0, then, then 4 bytes length for the following name of font [should be 32 bytes] | + | * JayFoxRox: header is XTF0, then, then 4 bytes length for the following name of font [should be 32 bytes] |
| − | JayFoxRox: seemingly this is used too: https://msdn.microsoft.com/en-us/library/dd144956(v=vs.85).aspx | + | * JayFoxRox: seemingly this is used too: https://msdn.microsoft.com/en-us/library/dd144956(v=vs.85).aspx |
| − | JayFoxRox: or at least there is a 4 byte length prefix again | + | * JayFoxRox: or at least there is a 4 byte length prefix again |
| − | JayFoxRox: near end of file it's very surely <code>u16 icount, u16 vcount, u16 indices[icount] { float x,y; }[vcount]</code> | + | * JayFoxRox: near end of file it's very surely <code>u16 icount, u16 vcount, u16 indices[icount] { float x,y; }[vcount]</code> |
| − | JayFoxRox: if there are any structures between those 2? no idea. | + | * JayFoxRox: if there are any structures between those 2? no idea. |
| − | JayFoxRox: apparently the last structure [with mesh data] keeps repeating towards the end, so it's probably each glyph seperately | + | * JayFoxRox: apparently the last structure [with mesh data] keeps repeating towards the end, so it's probably each glyph seperately |
| − | JayFoxRox: I don't have more time for doing this now - I already did more than I wanted by sourcing the Xbox.xtf and Xbox Book.xtf and looking at it with hexedit and googling for MS structures :P | + | * JayFoxRox: I don't have more time for doing this now - I already did more than I wanted by sourcing the Xbox.xtf and Xbox Book.xtf and looking at it with hexedit and googling for MS structures :P |
| − | JayFoxRox: I think there are degenerates, so looks like tri-strip | + | * JayFoxRox: I think there are degenerates, so looks like tri-strip |
--[[User:JayFoxRox|JayFoxRox]] ([[User talk:JayFoxRox|talk]]) 11:49, 22 August 2017 (PDT) | --[[User:JayFoxRox|JayFoxRox]] ([[User talk:JayFoxRox|talk]]) 11:49, 22 August 2017 (PDT) | ||
Revision as of 18:49, 22 August 2017
Merge with dashboard article
I think it makes sense to merge this with the dashboard article or even move such file format stuff to other wikis. However, I'm not sure how to integrate it best with the dashboard article, and I'm not aware of any wikis where this would fit. --JayFoxRox (talk) 11:45, 22 August 2017 (PDT)
Add file format info
from #xqemu irc channel
- JayFoxRox: I looked at the file, it seems to be a 2D mesh format, indices, followed by vertices
- JayFoxRox: header is XTF0, then, then 4 bytes length for the following name of font [should be 32 bytes]
- JayFoxRox: seemingly this is used too: https://msdn.microsoft.com/en-us/library/dd144956(v=vs.85).aspx
- JayFoxRox: or at least there is a 4 byte length prefix again
- JayFoxRox: near end of file it's very surely
u16 icount, u16 vcount, u16 indices[icount] { float x,y; }[vcount] - JayFoxRox: if there are any structures between those 2? no idea.
- JayFoxRox: apparently the last structure [with mesh data] keeps repeating towards the end, so it's probably each glyph seperately
- JayFoxRox: I don't have more time for doing this now - I already did more than I wanted by sourcing the Xbox.xtf and Xbox Book.xtf and looking at it with hexedit and googling for MS structures :P
- JayFoxRox: I think there are degenerates, so looks like tri-strip
