19,760
edits
User talk:Mai X: Difference between revisions
→OBD updates
| (6 intermediate revisions by 2 users not shown) | |||
| 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 58: | Line 57: | ||
:I won't leave those "----" for addresses, of course... I'll re-calculate those addresses right after I'll finish cleaning up 0xDEADs and renaming not only paddings back to "padding", but also all "int" to "'''u'''int" where it's needed...--[[User:Mai X|Mai X]] ([[User talk:Mai X|talk]]) 21:51, 12 May 2025 (UTC) | :I won't leave those "----" for addresses, of course... I'll re-calculate those addresses right after I'll finish cleaning up 0xDEADs and renaming not only paddings back to "padding", but also all "int" to "'''u'''int" where it's needed...--[[User:Mai X|Mai X]] ([[User talk:Mai X|talk]]) 21:51, 12 May 2025 (UTC) | ||
::Okie. Don't over-work yourself :-) --[[User:Iritscen|Iritscen]] ([[User talk:Iritscen|talk]]) 21:56, 12 May 2025 (UTC) | ::Okie. Don't over-work yourself :-) --[[User:Iritscen|Iritscen]] ([[User talk:Iritscen|talk]]) 21:56, 12 May 2025 (UTC) | ||
::For the record, here are the pages with added fields that have "----" for addresses: OBD:Mtrl, OBD:Impt, OBD:ENVP, 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) | |||
::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) | |||
:::<code>ONI_Character.h, line 167</code>... It is stated in the dev's comment...--[[User:Mai X|Mai X]] ([[User talk:Mai X|talk]]) 21:29, 14 May 2025 (UTC) | |||
::::Oh, if only we could rely on developers' comments to be accurate ;-) You'll notice that the comment right above that one is misleading too, since not all ONCCs have a <code>turning_nimbleness</code> of 1.0 (see my note on that field on OBD:ONCC). Anyway, BWest's intention might have been to allow MELE to override the dazed fields, but it seems they never got around to it. --[[User:Iritscen|Iritscen]] ([[User talk:Iritscen|talk]]) 14:47, 15 May 2025 (UTC) | |||
:::::I'm sorry... I forgot to trace that field through the code, like I usually do with other fields...--[[User:Mai X|Mai X]] ([[User talk:Mai X|talk]]) 20:56, 15 May 2025 (UTC) | |||
::::::No problem. You were editing a lot of pages! I took the time to do a deep dive on ONCC because it's been long overdue. I'll need accurate info on the OBD pages for a project I'm working on soon, so your edits have been helpful. --[[User:Iritscen|Iritscen]] ([[User talk:Iritscen|talk]]) 18:43, 16 May 2025 (UTC) | |||