Import .vox bug about goxel

[guillaumechereau]

Hi TechnoPromotheus. Thanks for the email. It's true that I haven't been working on goxel for a while. I think what I need the most at the moment is users feedback, so I can get an idea of where I should take the project. For example: should I focus on improving the user interface, or the rendering quality?

For the import problem, can you send me an example .vox file that crash, so I can reproduce the bug?

[TechnoPrometheus]

Thank you! the Goxel interface is very intuitive, and the ability to generate voxel objects procedurally (script) is extremely cool! I would focus on the job:

Adding modeling capabilities
improve export models, with generation of textures? instead of the color palette and materials (such as MagicaVoxel).

Goxel only needs to be spread! It is a very nice tool, and made good (fantastic gui).

You have created a small jewel, do not underestimate your talent, with Goxel time it will be very popular.

Thanks for your kindness. The 3d models voxel public them on my short github account, so you have my little art to do testing.

[YarlBoro]

Today I've found out about Goxel (lucky me!) and one of the first things that I have tried was importing model from Qubicle.
.Vox format hangs program ("goxel quit unexpectedly"). When I tried Qubicle native formats (.qb & .qbcl), workspace stays empty after import without any communicate. IMHO interchangeability is one of most important aspects of any modeling/drawing/design app, especially when it's young and feature incomplete.

[guillaumechereau]

Hello YarlBoro, can you tell me what version of goxel you are using, and on what system (pc, mac or linux?). Also if you can send me a few samples of broken files that will help me to fix those bugs, since on my machine it seems to work.

[YarlBoro]

Hello! Thanks for quick reply. I'm using Goxel 0.3.0 (1). My system is Osx 10.10.5. I use it on two machines, Macbook Pro Early 2011 (8 gb of RAM, gpu is 6750M with 1 gb) and rock solid hackintosh, 16 gb ram and R9 380 4gb. MagicaVoxel opens those files without issues, so it's not problem of bad format or corrupt data. One file is relatively quite complex and big, the other one is very simple made just for testing. I can send You those files, just tell me how :) If I can provide any more feedback, like further testing stuff, checking console logs, mess with terminal, etc. just let me know.

I agree with TechnoPrometeus and many other folks, even in such early shape Goxel shows a lot of potential. Procedural stuff, no limits on model sizes (YES!!!), nice selection system, layers, customizable rendering system...It would be complete waste if Goxel wouldn't develop into full grown app. MagicaVoxel, Qubicle and VoxelShop are great voxel editors, but there is still space for another app that is doing it's own thing, IMO.

[guillaumechereau]

Thanks! You can send me any broken files you have at my email address: [email protected]. I'll have a look as soon as I can.

On Fri, 3 Feb 2017 at 02:22 YarlBoro ***@***.***> wrote: Hello! Thanks for quick reply. I'm using Goxel 0.3.0 (1). My system is Osx 10.10.5. I use it on two machines, Macbook Pro Early 2011 (8 gb of RAM, gpu is 6750M with 1 gb) and rock solid hackintosh, 16 gb ram and R9 380 4gb. MagicaVoxel opens those files without issues, so it's not problem of bad format or corrupt data. One file is relatively quite complex and big, the other one is very simple made just for testing. I can send You those files, just tell me how :) If I can provide any more feedback, like further testing stuff, checking console logs, mess with terminal, etc. just let me know. I agree with TechnoPrometeus and many other folks, even in such early shape Goxel shows a lot of potential. Procedural stuff, no limits on model sizes (YES!!!), nice selection system, layers, customizable rendering system...It would be complete waste if Goxel wouldn't develop into full grown app. MagicaVoxel, Qubicle and VoxelShop are great voxel editors, but there is still space for another app that is doing it's own thing, IMO. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#25 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAGkn1CAQAhb7yR-jQIdqC4Hcm5wFpwpks5rYhDMgaJpZM4LbHAc> .

-- Sent from my iPad.

[guillaumechereau]

I made a few changes on the code to fix a few issues with loading of vox and qubicle files. I will make a new release as soon as possible so that you can test the new binary.

[YarlBoro]

Great, thanks for letting me know! M

…

On 5 February 2017 at 10:33, Guillaume Chereau ***@***.***> wrote: I made a few changes on the code to fix a few issues with loading of vox and qubicle files. I will make a new release as soon as possible so that you can test the new binary. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#25 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AGtj8SDePZ_YAATPiGe81KGTZRA8BjHaks5rZZd0gaJpZM4LbHAc> .

[guillaumechereau]

OK the release 0.4.0 is out. I hope it fixes some of the export/import issues. Please try and let me know if there is any problem!

[YarlBoro]

Nice, I'll check it as soon I can and let You know if there are any issues. M

…

On Tue, 7 Feb 2017 at 15:57, Guillaume Chereau ***@***.***> wrote: OK the release 0.4.0 is out. I hope it fixes some of the export/import issues. Please try and let me know if there is any problem! — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#25 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AGtj8YWiBcmx1pIslgXNk8AhYAAuB8rdks5raIZngaJpZM4LbHAc> .

[zmei]

Sorry for posting here, but have the same issue with vox importing in 0.3.
Tried new release (binary rel 0.4), importing of vox works! Then tried importing another one in the same scene, still no problems, until I tried moving one of them, so that they're side by side. Sadly any attempt to move any one of them crashes goxel. Tried importing on different layers also with different models (all are 126³). Tested only on a laptop with intel core2duo 2.6ghz + 4gb ram on w10x86 video is nvidia gt240m. It's older, so lower spec and wondering if that might be the reason?
Goxel is amazing, it's the reason I joined github in the first place - to be updated on its dev progress :) Keep it up, lots of potential here, I'm surprised it hasn't brought so much attention it actually deserves. Cheers!

[guillaumechereau]

Thanks for the bug report. I actually never though of the use case of importing a file as a new layer, so I never tested it. I will see how to fix that!

…

On Thu, Feb 09, 2017 at 06:07:46AM -0800, zmei wrote: Sorry for posting here, but have the same issue with vox importing in 0.3. Tried new release (binary rel 0.4), importing of vox works! Then tried importing another one in the same scene, still no problems, until I tried moving one of them, so that they're side by side. Sadly any attempt to move any one of them crashes goxel. Tried importing on different layers also with different models (all are 126³). Tested only on a laptop with intel core2duo 2.6ghz + 4gb ram on w10x86 video is nvidia gt240m. It's older, so lower spec and wondering if that might be the reason? Goxel is amazing, it's the reason I joined github in the first place - to be updated on its dev progress :) Keep it up, lots of potential here, I'm surprised it hasn't brought so much attention it actually deserves. Cheers! -- You are receiving this because you commented. Reply to this email directly or view it on GitHub: #25 (comment)

[zmei]

Tried both on a new layer and on the same one -both import, can be edited, but moving voxels around crashes goxel. I think it might not be a layer related issue. Best regards!

[YarlBoro]

I checked Mac version 0.4, I tried it with same models that I have used before for consistent testing. First of all, mac release have wrong permissions set on app, so it can't run without fixing it with command: sudo chmod -R 755 /Applications/goxel.app Both of my simple test models ('ModelTest' and 'Autobus_vox_w1') are loading properly if .vox is used. When .qb format is used, some pixels are missing on second model. I provided screenshots in attachment, filenames suggest what is what. Problem with missing pixels after .qb import is even more prominent when larger models are used. I have attached model of bus ('FullBus'), with screenshots of how it suppose to look like, and what is missing after import. I have tried importing bus model in .vox format, but it crashes Goxel (crash log attached in text file).

[YarlBoro]

One more thing, it might make sense to support .qbt format instead of .qb. It is improved version of older format with some future-proofing for new things to come in Qubicle. I know It's easy to suggest various stuff, a lot harder to implement them...Just humble suggestion.
Here is explanation & documentation of this format:
http://minddesk.com/learn/article.php?id=47

[guillaumechereau]

YarlBoro, did you forget to attach the files?
I didn't know about qbt files, yes it would be good to support them as well (import/export). I'll try to add this before the next release.

[zmei]

Didn't know crashlogs are generated? Where to look for them?

…

On Fri, Feb 10, 2017, 06:16 Guillaume Chereau ***@***.***> wrote: YarlBoro, did you forget to attach the files? I didn't know about qbt files, yes it would be good to support them as well (import/export). I'll try to add this before the next release. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#25 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AFhGswGeRc1tk74NhFNHXywf643h1xn1ks5ra-SjgaJpZM4LbHAc> .

[guillaumechereau]

No I mean you mentioned that you attached some models (fullbus) and screenshots. I don't see them.

[zmei]

I jumped into middle of your conversation amd extremely sorry. Another user said that.

…

On Fri, Feb 10, 2017, 08:03 Guillaume Chereau ***@***.***> wrote: No I mean you mentioned that you attached some models (fullbus) and screenshots. I don't see them. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#25 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AFhGs6t1xvOjH85gv2vq99a9E1GwhT3Vks5ra_2qgaJpZM4LbHAc> .

[YarlBoro]

@guillaume Chereau

Yes, files were not attached - my mistake. I'll send them soon.

[guillaumechereau]

I just pushed two fixes for vox and qubicle import. A remaining problem is that after an import the model orientation doesn't seem to be correct. This is specially annoying since the rotation tool is currently way too slow for big models.

I'll make a minor release soon to try to address this.

[YarlBoro]

Much appreciated. What is best place to send or discus feature suggestions? Should I use 'issues' section?

…

On 11 February 2017 at 09:40, Guillaume Chereau ***@***.***> wrote: I just pushed too fixes for vox and qubicle import. A remaining problem is that after an import the model orientation doesn't seem to be correct. This is specially annoying since the rotation tool is currently way too slow for big models. I'll make a minor release soon to try to address this. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#25 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AGtj8Sq052PE_SIi_hBsbcuFIsAGvNgwks5rbXQOgaJpZM4LbHAc> .

[guillaumechereau]

Yes, you can create a new issue for each feature you would like to discuss.

On Sun, 12 Feb 2017 at 01:13 YarlBoro ***@***.***> wrote: Much appreciated. What is best place to send or discus feature suggestions? Should I use 'issues' section? On 11 February 2017 at 09:40, Guillaume Chereau ***@***.***> wrote: > I just pushed too fixes for vox and qubicle import. A remaining problem is > that after an import the model orientation doesn't seem to be correct. This > is specially annoying since the rotation tool is currently way too slow for > big models. > > I'll make a minor release soon to try to address this. > > — > You are receiving this because you commented. > Reply to this email directly, view it on GitHub > < #25 (comment) >, > or mute the thread > < https://github.com/notifications/unsubscribe-auth/AGtj8Sq052PE_SIi_hBsbcuFIsAGvNgwks5rbXQOgaJpZM4LbHAc > > . > — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#25 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAGkn_WuLLR225qHKzUilhGDBkO16j4Jks5rbew3gaJpZM4LbHAc> .

-- Sent from my iPad.