User talk:Mai X: Difference between revisions

← Older edit

User talk:Mai X (view source)

Revision as of 18:43, 16 May 2025

5,137 bytes added , 16 May

→‎OBD updates

Iritscen

Bureaucrats, Interface administrators, Suppressors, Administrators

19,760

edits

@@ Line 13: / Line 13: @@
 I'm impressed too! Your work looks very promising. What sort of plans do you have for the future? P.S.: Wasn't Konoko HD Armor high-poly enough for you? --[[User:Iritscen|Iritscen]] ([[User talk:Iritscen|talk]]) 21:59, 28 November 2024 (UTC)
+:For now, my plan is just to have some rest... Plans for my updates: add better HDR support, implement Autodesk Scaleform for HUD and menus (instead of textures + 9-slice), add JPEG and PNG-ZIP texture compression support, implement GDF compression with LZMA-2... P.S.: Chief model has bundled normal maps with it, has over 60 000 polygons and has 4096x4096 uncompressed textures... HD Konoko is not so HQ as that model... --[[User:Mai X|Mai X]] ([[User talk:Mai X|talk]]) 07:28, 1 December 2024 (UTC)
+Today I found the time to watch the video you added. Great work!
+Unfortunately, the msVo encoded audio didn't play so for the fun of it, here's [http://paradox.oni2.net/wiki/user/Mai_X/talk/Mai_X_OniDemoChief_Mai_X_at_the_new_edge_of_modding.mp4 another version]. ^_^
+Like Iritscen said, hopefully you can add Mai (package 26000 [http://paradox.oni2.net/wiki/user/Mai_X/talk/26000_Konoko_HD_Armor.png Konoko HD Armor]) in another iteration of the scene. It's not super highpoly but for Oni's standards it's quite decent. You probably you really wanted to make a point about the high poly count with master chief. Though I cannot stop feeling he is still to much of an ''alien'' there. --[[User:Paradox-01|paradox-01]] ([[User talk:Paradox-01|talk]]) 19:12, 18 December 2024 (UTC)
+:The original music is called "Velta Theme" from Synergia OST... I've re-encoded it to MP3, so you can get it [http://konoko.oni2.net/%5bMusic%5d/Velta%20Theme.MP3 here]...
+:Your version is even better, than mine... Thank you... You've got the "atmosphere" of the video completely right...
+:I'll try to use that model of "HD" Konoko in my next video (featuring ManPlant level; info is on main page)... --[[User:Mai X|Mai X]] ([[User talk:Mai X|talk]]) 06:43, 6 May 2025 (UTC)
 ==Let us cheer you up*==
@@ Line 38: / Line 50: @@
 :::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==
+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.
+Anyway, I just have one question: are you planning to fill in those offsets where you added a new field but placed "----" for the address? --[[User:Iritscen|Iritscen]] ([[User talk:Iritscen|talk]]) 19:36, 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)
+::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)