Exception "EAccessViolation": Access violation about view3dscene HOT 5 CLOSED

1. https://castle-engine.io/convert.php answering Conversion script failed (non-zero exit status): fixed. That is, we didn't display full error message, when you forget to upload glTF binary data. The error message will now appear OK. And you should upload additional binary data.

   You most likely uploaded the xxx.gltf file without the corresponding xxx.bin file (that contains vertex data). E.g. you uploaded gltf/punctual_lights/test_lights.gltf, but not gltf/punctual_lights/test_lights.bin . When a glTF model references additional binary files. you have to upload them too (as the comments under https://castle-engine.io/convert.php say, you can select multiple files by Ctrl in the open dialog box).

   Our error message did not communicate it. Now you will see

   Exception "EDownloadError":
   Error when downloading "file:///home/convert-to-x3d/test_lights.bin": Exception "EFOpenError":
   Unable to open file "/home/convert-to-x3d/test_lights.bin"
   Conversion script failed (non-zero exit status).
   

   In case of trouble, please provide more details about what do you do / which file you use. The first glTF I tested from https://castle-engine.io/demo_models.php was gltf/knight_size_test/knight_size_test.glb, and it worked :), as it contains glTF per-vertex data embedded. In general a glTF (with .gltf extension) file may reference additional binary files, but doesn't have to -- it depends on how it was exported. Only the glTF files with .glb extension are always self-contained.

   Also note that https://castle-engine.io/convert.php is actually using tovrmlx3d (additional binary bundled with view3dscene, and executes it like tovrmlx3d --encoding=xml input.xxx > output.x3d).

2. view3dscene making access violation: hm, I cannot reproduce it. I tested using --write-encoding locally, with

   • view3dscene stable from https://castle-engine.io/view3dscene.php
   • view3dscene snapshot from https://castle-engine.io/view3dscene.php
   • view3dscene built locally

   I tested like this:

   view3dscene ~/sources/castle-engine/demo-models/gltf/punctual_lights/test_lights.gltf --write --write-encoding=xml  > something.x3d
   

   and it goes OK. So

   • What exactly do you run, on which input file do you run it?

   • What OS do you use? I tested above now on Linux/x86_64.

Cosmetic for consistency: also suggest removing space character and adding period, "Classic VRML (x3dv extension)" to "ClassicVRML (.x3dv extension)"

I added a period. I didn't remove the space, I like it :), it separates 2 words, and various engine docs talk about classic VRML encoding, not ClassicVRML encoding. So I don't make ClassicVRML a single word.

from view3dscene.

@ricklentz Aha, we can improve the error in this case then :)

Done, instead of "EAccessViolation" you will now see clear

Standard output is not available. This most likely means you used --write option on Windows and you didn't redirect the output.

The proper usage from the command-line looks like "view3dscene input.gltf --write > output.x3d", see https://castle-engine.io/view3dscene.php#section_converting .

from view3dscene.

Cosmetic for consistency: also suggest removing space character and adding period, "Classic VRML (x3dv extension)" to "ClassicVRML (.x3dv extension)"

Am also adding menu item to X3D-Edit > Import Model from File > Castle Game Engine Convert to X3D to deploy in next published build.

from view3dscene.

@michaliskambi Thank you. Regarding #2 above, the exception can be triggered when running it without the pipe-to-file (' > something.x3d') portion of the command on Windows 10. It works perfectly when used with the output file pipe parameter. Thank you again!

from view3dscene.

The automatic "snapshot" build from https://castle-engine.io/view3dscene.php will soon contain this improvement.

from view3dscene.