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.

thomasup

Forum Replies Created

Viewing 10 posts - 46 through 55 (of 55 total)
  • Author
    Posts
  • in reply to: normal quality in browser #34106
    thomasup
    Customer

    true, that sure is a contributing factor.

    we will try to narrow it down further

    in reply to: normal quality in browser #34073
    thomasup
    Customer

    image01 is in verge3d, image02 in blender.
    same camera, material and all.
    verge3d has this strange “z-shaped” reflection, which is not visible in blender.
    other spots are notably different, too.

    it could be some difference in normal interpolation, the falloff between verts seems more linear / abrupt in verge3d.

    or is there a different precision level used in v3d? high quality normals in blender are disabled.

    the differences are not huge, but since the imperfections are far less visible in blender, it is hard to adjust/fix them. most of them only become visible once exported.

    Edit: attached example blend file

    Edit2: also the normal interpolation seems to be different on the mirrored side.

    Attachments:
    You must be logged in to view attached files.
    in reply to: equivalent of app.controls.tween easing #33622
    thomasup
    Customer

    ah i found it out in the meantine, but thank you, Ivan!

    in reply to: equivalent of app.controls.tween easing #33617
    thomasup
    Customer

    thank you for the answer, but we looked into the puzzle but no option was fully synchronized.

    after quite some digging in the minified v3d code i found out that
    v3d.MathUtils.smootherstep
    is applied to the linear camera transition progress.

    this helped me solve the issue, now both movements are in sync, by applying the smootherstep to the secondary animation too.

    Edit: it is now silky smoooth. nice!

    in reply to: set domElement of orbit controls #29738
    thomasup
    Customer

    that works perfectly for us!

    thanks :good:

    in reply to: blender: tangent input does not work, tonemapping #29280
    thomasup
    Customer

    the tangent node now works in v3d 3.2. good job!

    in reply to: blender: tangent input does not work, tonemapping #27462
    thomasup
    Customer

    i attached a file with some oddities i found with shaders. they are no deal breaker though, and most can be worked around, if you know them.

    more tonemapping options would be a bigger improvement imo. especcially a non-clipping high contrast mode (p.e. filmic + High Contrast) or availability of the Color Management curves could improve the visuals the most.

    Attachments:
    You must be logged in to view attached files.
    in reply to: js programming capabilities vs puzzle capabilities #25234
    thomasup
    Customer

    nice. all those script references!

    looking at the teapot heater example logic helped me a lot. makes me confident that i will will find all needed features, and this engine would be viable.

    p.e. app.controls.tween does not appear in the documentation. also takes a mysterious 4th argument “doSlot”, which is mostly an empty function.
    but it is usable as is, so not really a problem.

    in reply to: js programming capabilities vs puzzle capabilities #25206
    thomasup
    Customer

    oh nice! that is very good to know. thank you

    in reply to: general starter questions about licenses etc #25183
    thomasup
    Customer

    thank you for the quick reply!
    this infomration helps a lot.

    minimizing:
    i think your response referes to the included “v3d.js” etc.
    but if we are to include our own js,css libraries, we will have to minify the complete package (into one js,css etc) ourselves, i assume.

    license: thank you for clarifying

    preloader:
    thank you for the link! i was looking for some kind of callback, as we need more control, but i will have a closer look

Viewing 10 posts - 46 through 55 (of 55 total)