Jump to content

User talk:Mai X: Difference between revisions

→‎OBD updates: question on dazed fields
(→‎OBD updates: question on dazed fields)
Line 51: Line 51:
:::Okay, so starting at the same age as me then :-) I've been lucky; I've lost HDs but never any data that wasn't in another place too. These days I have redundant backups of all my data on local HDs and in the cloud. --[[User:Iritscen|Iritscen]] ([[User talk:Iritscen|talk]]) 22:28, 30 March 2023 (CEST)
:::Okay, so starting at the same age as me then :-) I've been lucky; I've lost HDs but never any data that wasn't in another place too. These days I have redundant backups of all my data on local HDs and in the cloud. --[[User:Iritscen|Iritscen]] ([[User talk:Iritscen|talk]]) 22:28, 30 March 2023 (CEST)


== OBD updates ==
==OBD updates==
 
Thanks for your work on those pages, you've made some good edits! I was surprised to see so many mistaken inclusions of 0xDEAD space at the ends of types, and had to investigate. It looks like confusion sometimes slipped in during the process of editing a page. For instance [[Special:Permalink/4457|this revision]] of ONCV listed the final bytes starting at 0x4C as 32-byte alignment filler, but the next edit by Ssg wiped out geyser's description and simply called them "unused". Perhaps Ssg and other editors knew what they were, but no editors thought to write "alignment padding" instead of "unused" for that range, which is misleading for the reader.
Thanks for your work on those pages, you've made some good edits! I was surprised to see so many mistaken inclusions of 0xDEAD space at the ends of types, and had to investigate. It looks like confusion sometimes slipped in during the process of editing a page. For instance [[Special:Permalink/4457|this revision]] of ONCV listed the final bytes starting at 0x4C as 32-byte alignment filler, but the next edit by Ssg wiped out geyser's description and simply called them "unused". Perhaps Ssg and other editors knew what they were, but no editors thought to write "alignment padding" instead of "unused" for that range, which is misleading for the reader.


Line 60: Line 59:
::For the record, here are the pages with added fields that have "----" for addresses: OBD:Mtrl, OBD:Impt, <strike>OBD:ENVP</strike>, OBD:AKEV. Maybe there are others, but those are the ones I noticed. --[[User:Iritscen|Iritscen]] ([[User talk:Iritscen|talk]]) 22:02, 13 May 2025 (UTC)
::For the record, here are the pages with added fields that have "----" for addresses: OBD:Mtrl, OBD:Impt, <strike>OBD:ENVP</strike>, OBD:AKEV. Maybe there are others, but those are the ones I noticed. --[[User:Iritscen|Iritscen]] ([[User talk:Iritscen|talk]]) 22:02, 13 May 2025 (UTC)
:::Update: I realized there was room for improvement/clarification on ENVP, so while I was working on that I filled in the offsets as well. --[[User:Iritscen|Iritscen]] ([[User talk:Iritscen|talk]]) 23:26, 13 May 2025 (UTC)
:::Update: I realized there was room for improvement/clarification on ENVP, so while I was working on that I filled in the offsets as well. --[[User:Iritscen|Iritscen]] ([[User talk:Iritscen|talk]]) 23:26, 13 May 2025 (UTC)
::As I'm looking over ONCC, I noticed the note "overridden by char's MELE profile if possible", but I'm not seeing that in the code. In fact it looks like the MELE's "dazed" fields are ignored by Oni entirely. There are various references to them in the editor and importer code, but I don't see where the game logic looks at them. --[[User:Iritscen|Iritscen]] ([[User talk:Iritscen|talk]]) 15:54, 14 May 2025 (UTC)