We use cookies to ensure that we give you the best experience on our website. If you continue to use this site we will assume that you are happy with it.

Ok, I Agree

David Duperron

Forum Replies Created

Viewing 15 posts - 46 through 60 (of 155 total)
1 2 3 4 5 … 9 10 11
  • Author
    Posts
  • 2024-08-07 at 2:23 pm in reply to: Help with the Append Puzzle please! #76458
    David Duperron
    Customer

    Hi @david-yanez!
    It seems that I have a very similar issue today after updating to 4.7.1 version. I’m getting axactly the same error messagen and my imports fail.
    Did you manage to find a solution to the above problem??

    2024-08-07 at 1:26 pm in reply to: Cannot read properties of undefined (reading ‘morphAttributes’) – after update to 4.7.1 #76457
    David Duperron
    Customer

    As soon as the appendScene() function is called after initial loading, this behaviour appears.
    I use the appendScene() puzzle several times during the initial loading and it works correctly, no error message, and the objects are correctly imported.
    But if I try to import objects later, it fails with this message…
    Did anything change with this append scene puzzle?? Anyone has any clue??
    Please Help!!

    2024-08-07 at 7:59 am in reply to: 4.7.1 Update and Principled BSDF errors #76444
    David Duperron
    Customer

    To say it quick: it’s better to re-export everything (all gltf files) after the update, as I also realized that there was another issue with objects “morphattributes” that were not properly read on old gltf files. This is solved by re-exporting the gltf with the latest version.

    EDIT: no it’s not solved… still have the morphattribute not defined issue… :(

    2024-08-07 at 7:52 am in reply to: 4.7.1 Update and Principled BSDF errors #76443
    David Duperron
    Customer

    Thanks! I think I got it.
    I had some gltf imports in my main scene, and these gltf were not updated, which caused the errors.
    This material issue is solved now!

    2024-06-26 at 8:11 am in reply to: Measure tool for Verge3D #75586
    David Duperron
    Customer
    kdv wrote:

    you just need to change 5 to some other value.

    David Duperron wrote:

    How can I add these generated submeshes to the objects

    coding

    I created a procedure to extract the names (not 3D objects!) of submeshes and add them to the list of measurable objects, and now everything is as expected!

    Thanks for the help!

    2024-06-25 at 4:32 pm in reply to: Measure tool for Verge3D #75572
    David Duperron
    Customer

    Ok Got it thanks!
    Also it gave me the opportunity to tune your puzzle block to add a scale option fore these ends. Everything works fine now!

    2024-06-25 at 3:34 pm in reply to: Measure tool for Verge3D #75569
    David Duperron
    Customer
    kdv wrote:
        dimPointOne.onBeforeRender = function() {
      setObjectScale(this, 5);
    };

    I do not see where to put this code… dimPointOne is only defined within the enableMeasureTool function.

    2024-06-25 at 3:15 pm in reply to: Measure tool for Verge3D #75567
    David Duperron
    Customer

    Ok but there is no option for these line ends as there is for the labels… Do I have to hard code it in the puzzle code??

    2024-06-25 at 3:13 pm in reply to: Measure tool for Verge3D #75566
    David Duperron
    Customer

    And another one: it seems that there is an issue with multimaterial objects. In the puzzle object selector they are represented with an “empty” icon whereas the monomaterial objects are represented with a standard object icon.
    And it seems that the measure tool does not recognize these objects (as they are indeed “parent” object with children geometries attached to them).
    How can I add these generated submeshes to the objects to be taken into account for the measure tool?

    2024-06-25 at 2:28 pm in reply to: Measure tool for Verge3D #75564
    David Duperron
    Customer

    Ok Great! thanks
    We loose the “always on top” behaviour but that’s not a big issue for me…
    Another quick question: how to increase the scale of the dots and arrows at the lines end??
    Thanks!

    David

    2024-06-25 at 1:54 pm in reply to: Measure tool for Verge3D #75561
    David Duperron
    Customer

    Hi Kdv!
    I’m having an issue with your measure tool, more precisely with the line(s) material which seems incompatible with the material I am using.
    The consequence is that the lines are not visible when an object with my material is somewhere behind the measure lines.
    When the material has some transparency we can see the lines “through” the material (blue cube in my example), but as soon as there is a mesh with this material in “opaque” configuration the lines disapear (transparency is controlled by the material alpha attribute in my material).
    Any idea how I could fix this? Does this have to do with the renderOrder in some manner?
    Thanks for your help!
    The example is here:

    https://v3d.net/tjm

    2024-06-21 at 7:38 am in reply to: gtaoVisible #75109
    David Duperron
    Customer

    Thanks @kdv!
    The material on which I would like to activate gtao is not an emission shader.
    GTAO can actually be activated on it as I can do it manually by changing the gtaoVisible parameter in the .gltf file before loading the application.
    In fact this parameter is false by default because the material has a transparency (alpha blend) which can be controlled by the user. Most of the time the material is opaque, and then it looks much better with GTAO, and in some rare cases the transparency is used, and in those cases, the problems related to GTAO in use with transparency are not really an issue for me… so I would like to be able to change this gtaoVisible parameter for this material after loading of the gltf file, and be avle to see the result in the viewport.

    2024-06-20 at 2:10 pm in reply to: gtaoVisible #75093
    David Duperron
    Customer

    I’ve tried to enable it manually with js code. I managed to retrieve the correct material, and write the gtaoVisible parameter to “true” but I see no effect on the viewport… I used the following code:

    const material = v3d.SceneUtils.getMaterialByName(app, "NI_paint_vertex_color")
material.needsUpdate = true;
material.gtaoVisible = true;
console.log(material)

    I can see in the console that the parameter has been set to true, but no visual change…

    2024-06-20 at 2:07 pm in reply to: gtaoVisible #75092
    David Duperron
    Customer

    The easiest way would be to publish the App on the Verge3D network, but I have a 500:Internal server Error when I try to publish it. The Application folder is located outside the “normal” verge3D application folder and i use a symbolic link… any way to get it to upload properly??

    2024-06-20 at 11:42 am in reply to: gtaoVisible #75090
    David Duperron
    Customer

    Thanks Alex!
    I’ll try to pack something that reproduces this behaviour…
    And lastly, is it possible to change this gtaoVisible parameter after the scene loading? (from false to true) and to update the material in order to display with Ambient Occlusion?
    Thanks!

    David

  • Author
    Posts
Viewing 15 posts - 46 through 60 (of 155 total)
1 2 3 4 5 … 9 10 11