Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Troxel v1 roadmap #31

Open
4 of 27 tasks
chrmoritz opened this issue Oct 1, 2015 · 6 comments
Open
4 of 27 tasks

Troxel v1 roadmap #31

chrmoritz opened this issue Oct 1, 2015 · 6 comments

Comments

@chrmoritz
Copy link
Owner

IO

  • Qubicle: Push warnings to an array and show it in the Linter
  • Quibble: don’t rely on same size of material maps, match material map position by the attachment point
  • move file system out of IO classes
  • add new merged model anchor format
  • base64: support for models larger than 256x256x256 (and limit export to: magica 126^3, voxel 127^3, )
  • WebWorker / multithreading WebWorkers / multithreading #3
  • Image (.png ...) to 1 voxel thick model (via dummy canvas + 2dcontext#getImageData())

Editor

libTroxel + merged models

  • rewrite for merge support (no object returning closure necessary, just only define window.Troxel with public api and use private functions around it, coffee script adds the closure)
  • Importer: import attachment point offsets
  • start Trove merged model list

Renderer

  • better material map support (tiled glass + non metal specular map types) Renderer improvements #21
  • three.js upgrade, Buffer-Geometry, chunked updates, reduce Material count by using color attribute where possible

GUI

  • GUI: rewrite (Angular.js) + redesign + advanced color picker + keyboard shortcuts GUI rewrite #9

Tests

Miscellaneous

Note: these are not blocking the v1 release but may be scheduled before other v1 task

  • Changelog app (open blueprint from selected older version + generate diff between two selected versions)
  • Fitting room app
  • Dungeon list app
  • Electron based Desktop Trove Modding Tools App
  • Blueprint: reverse engineer file format
  • TroveCreationsLinter: check for alpha values in non glass voxels/ specular values on non solid voxels
  • move Trove Blueprint json files + changelog to own repo with tags for dates
    • possibility to select date when opening Trove models
  • move Troxel project to its own github organisation
@chrmoritz
Copy link
Owner Author

  • TypeScript
  • Angular2
  • application cache => Service Workers
  • local storage (saved models + Trove.json) => indexedDB

@ChtiClem
Copy link

ChtiClem commented Feb 7, 2016

Hello,
I've a question. I'm using Troxel to verify my gun's mesh in order to submit it in the trove creation's reddit.
I've defined the 4 files : original, the type, the alpha and the specular.
In zoxel, it's working fine.
In Trove it's fine too.
But in Troxel, It warns me that I've put some alpha voxel on non existing one and some specular the same (and proposes me a correction).
The problem, is that the fix removes some glass voxels and fix some specular voxels (can't see any difference for this)
I've checked numerous times (and my gun doesn't have so much voxels). I've redone the t, a and s files but Troxel still warns me with the alpha and specular problems.
I provide you my files, just if you can check by yourself if you have the same message, please ?
Or to prove I'm completly dumb.
Thanks in advance (in both cases, ;) )

BugFiles.zip
ErrorsLog.txt

@chrmoritz
Copy link
Owner Author

You're missing the most important line in your logs:
z-axis orientation: 0 (0 for left, 1 for right handed (recommended))

Your main material map file (TwinsV3.qb) is exported with the right handed z-axis orientation format, but all other material maps (_a, _s and _t) are exported with the left handed z-axis orientation format, which is quite deprecated. Troxel's Qubicle Importer gets confused by your mix of z-axis orientation formats (it assumes that all files are in the same format).

Currently Zoxel is the only editor (which I know) using the left handed z-axis orientation format. I've opened chrmoritz/zoxel#12 to migrate Zoxel to use the right handed format too.

In summary the issue is caused by using multiple editors for the different material map files. To fix is just open the main file in Zoxel and save it in the old left handed format to be consistent with all other material maps (or convert all 3 material maps one by one to right handed using Troxel).

@chrmoritz
Copy link
Owner Author

This is fixed inside Troxel with 613aa50 now by throwing an error if trying to mix different z-axis orientation formats. I don't think it's worth backporting to the old site. It will most likely released with the migration to the new website. Thanks for reporting this.

@chrmoritz
Copy link
Owner Author

@ChtiClem The issues was fixed in Zoxel with chrmoritz/zoxel@c570967 by using the right handed z-axis orientation format when exporting models to .qb(Qubicle). A new version 0.6.1 with the fix was released at https://github.com/chrmoritz/zoxel/releases/tag/0.6.1. Try to update to this version and rexport all material maps.

@ChtiClem
Copy link

ChtiClem commented Feb 7, 2016

Thanks to you ^_^ I'll give a try either option : or in zoxel or in troxel.

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants