8,969
edits
Talk:Modifying an existing level: Difference between revisions
Talk:Modifying an existing level (view source)
Revision as of 08:15, 17 April 2026
, Friday at 08:15no edit summary
Paradox-01 (talk | contribs) mNo edit summary |
Paradox-01 (talk | contribs) mNo edit summary |
||
| Line 113: | Line 113: | ||
===XSI addon replacement?=== | ===XSI addon replacement?=== | ||
The general mechanisms - for floating menus and direct value rendering on objects - must be researched first, before this can be considered. | The general mechanisms - for floating menus and direct value rendering on objects - must be researched first, before this can be considered. | ||
Are attachable strings possible? According to documentation, it is [https://docs.blender.org/api/current/bpy.types.StringProperty.html possible for regular objects] and strings will be added to [https://developer.blender.org/docs/release_notes/5.2/geometry_nodes/ Geometry nodes in Blender 5.2]. | |||
===Asset panel?=== | ===Asset panel?=== | ||
| Line 202: | Line 204: | ||
====Dev notes==== | ====Dev notes==== | ||
On a general note: | On a general note: | ||
* Do simpler fixes first, so the more complex bug might get easier to fix if a few other | * Do simpler fixes first, so the more complex bug might get easier to fix if a few other interdependencies are already fixed. | ||
* In case of big pools of files with same subtype, use a limited amount of test files at once first. | * In case of big pools of files with same subtype, use a limited amount of test files at once first. | ||
* A complete dev env should contain files to test every possible conversion including options. | * A complete dev env should contain files to test every possible conversion including options. | ||
* Keep test data out of original AE directory. When debugging multiple codebases, you don't want | * Keep test data out of original AE directory. When debugging multiple codebases, you don't want them to crash into one another. | ||
=====Custom bot===== | =====Custom bot===== | ||
* Add notes about resources there. Like a downloaded Onisplit wiki page. | * Add notes about resources there. Like a downloaded Onisplit wiki page and what to expect from it. Commands and args. Be consistent using known terms, like "export" and "extract", in their proper use cases. | ||
* Add general working instructions like for reading and writing test data. | * Add general working instructions like for reading and writing test data. | ||
Example of an Agent.md; for "..." use your own start path. | |||
<pre> | |||
--- | |||
name: Oni-Ni-Kanabo | |||
description: Agent helps in creating Oni (Bungie, 2001) game related tools and data. | |||
--- | |||
# Oni-Ni-Kanabo | |||
When working with Onisplit (Onisplit.exe) then you can lookup commands and arguments from locally saved html webpage at %USERPROFILE%/.github/agents/ | |||
Read that helpful html when you start. | |||
c#-based Onisplit.exe is located at ...\OniSplit-src-net10\bin\Debug\net10.0-windows\Onisplit.exe | |||
c#-based Onisplit sorce code is located at ...\OniSplit-src-net10 | |||
Read test data from ...\Oni\AE\GameDataFolder if needed, but write outputs to github-ignoreable subfolders of the individual's local OniSplit codebase to avoid conflicts with the source code and to keep test outputs organized and separate from source files. | |||
Use .test-output for outputs and comparisons to reach hash-based conclusions about parity between c# and vb builds. | |||
When conversions with this vb-based application fail, test same command with the c#-based Onisplit.exe to check if the issue is vb-specific or shared. | |||
If shared, then it's not a parity issue and should be fixed in both builds together. Skip (but document) shared issues for now and focus on vb-only issues. | |||
If vb-specific, then it's a parity issue and should be fixed in the vb codebase to match the c# behavior. | |||
</pre> | |||
=====Session instruction example===== | =====Session instruction example===== | ||
| Line 227: | Line 252: | ||
====Notes on C# (.NET Framework 4) (Onisplit 0.9.99.0)==== | ====Notes on C# (.NET Framework 4) (Onisplit 0.9.99.0)==== | ||
Looks like the current OniSplit srouce on svn | Looks like the current OniSplit srouce on svn has a bug in XML/ParticleXmlImporter.cs | ||
// broken: string text = xml.ReadElementContentAsString(); | // broken: string text = xml.ReadElementContentAsString(); | ||
string text = xml.ReadContentAsString(); | string text = xml.ReadContentAsString(); | ||
| Line 237: | Line 262: | ||
Applied fix in C# .NET 10 build: | Applied fix in C# .NET 10 build: | ||
99+: pass | 99+: pass | ||
====Notes on C# (.NET 10)==== | ====Notes on C# (.NET 10)==== | ||
The idea was (and is) to translate the v0.9.99-codebase from C# to vb, but as minior bugs linger in v0.9.99 that route builds also mental load, permanent doubts that there could be something wrong which then affects the vb codebase as well. As for traslating the v0.9.95-codebase, you are permanently concerned that it will miss new features introduced in v0.9.99. | |||
New fixes for 0.9.99: | |||
* XML was first exported with slightly less accuracy: Floats are rounded to 6 instead of 7 digits after the decimal separator. The desired behavior was reimplemented by adding methods that mimic this quasi-legacy float-parsing. | * XML was first exported with slightly less accuracy: Floats are rounded to 6 instead of 7 digits after the decimal separator. The desired behavior was reimplemented by adding methods that mimic this quasi-legacy float-parsing. | ||
* TRAM needs double checking. | * TRAM needs double checking. | ||
| Line 261: | Line 289: | ||
XML imports needs a better test setup because of all the subformats. | XML imports needs a better test setup because of all the subformats. | ||
==( | ==(Another tool placeholder)== | ||