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 15 posts - 1 through 15 (of 55 total)
  • Author
    Posts
  • in reply to: Basic material brings error #72288
    thomasup
    Customer

    i do not know what i did, but some weird combination of uninstalling, deleting, and reinstalling now has the sneak peek in the new version 4.6.0

    in reply to: Basic material brings error #72286
    thomasup
    Customer

    i am not running a project, i am just opening the default blender file, and clicking “sneak peek”.

    i tried reinstalling verge3d,

    and i tried to find out why the sneak peek player is loading an old version, but in C:\Users\user\Verge3D_for_Blender\build there is the new v3d.js version 4.6.0. so where does the server get the old 4.2.0 version from?

    in reply to: post process at higher resolution #64755
    thomasup
    Customer

    that looks interesting though! seems like you managed to scale them independently.
    how did you do the independent scaling?
    that would help me out already!

    in reply to: alpha blend mode / add shader compatbility #64643
    thomasup
    Customer

    very nice! we will put the additive blending to use!

    • This reply was modified 1 year, 4 months ago by thomasup.
    in reply to: export / loading fails with specific node setup #60980
    thomasup
    Customer

    true, that will fix the exports. but it is hard to fix all the nodes by hand.

    we will roll back the versions, and sticking to blender 3.3 as of now, and await the next verge release!

    in reply to: export / loading fails with specific node setup #60962
    thomasup
    Customer

    exporting from blender 3.3.4 LTS also does not work:

    v3d.WebGLProgram: shader error: 0 35715 false gl.getProgramInfoLog Fragment shader is not compiled.

    Edit: it does export correctly, when the file has not been opened with blender 3.4 before. so a “clean” 3.3 file works.

    in reply to: installer for 4.1.1 does not work #57418
    thomasup
    Customer

    ok, so i have a gotten a bit further:
    – 4.1.1 installs tp C:/Program Files/, instead of C:/Users/Username/
    – 3.9.1 remains there, and is still the version which opens when starting from the start menu
    – in C:/Program Files/verge3d, you can find the new plugin for blender
    – after copying the 4.1.1 plugin into blender 3.3 addon folder, it shows up with the new version number, but no quick preview button / verge panels
    – when trying to enable the addon, this error occurs:

    Traceback (most recent call last):
      File "C:\Program Files\Blender Foundation\Blender 3.3\3.3\scripts\modules\addon_utils.py", line 333, in enable
        mod = __import__(module_name)
      File "C:\Users\tp\AppData\Roaming\Blender Foundation\Blender\3.3\scripts\addons\verge3d\__init__.py", line 50, in <module>
        from pluginUtils.log import printLog
    ModuleNotFoundError: No module named 'pluginUtils'
    in reply to: installer for 4.1.1 does not work #57416
    thomasup
    Customer

    not sure what you mean by reinstalling in blender,

    but the plugin folder installed to C:\Users\Username\verge3d_blender\addons\verge3d is still the version 3.9.1, so i do not know where i would find the package for the blender install…

    in reply to: first person controls setup #43453
    thomasup
    Customer

    having it work now, the collision logic is a bit clunky:

    usually, when navigating towards a wall with an angle, you would expect to “slide off” to the side. instead the camera comes to a full stop. also, when the movement speed is higher, the camera will stop earlier. then, when the move speed decreases, it will inch closer towards the wall. which has the strange effect that it moves a bitt more after releasing a movement button.

    will have a bit more trialanderror here, but we might have to go with a custom solution here.

    in reply to: first person controls setup #43452
    thomasup
    Customer

    oh, so the collision mesh is expecting more of a navigation-mesh type thing. the camera will not collide with the mesh, but rather move on it.

    in reply to: 3D configurator of a sports equipment ”OnCourt” #43441
    thomasup
    Customer

    wow, really good image quality. the lighting is on point!
    i like it a lot.

    in reply to: Roadmap Verge3d #43440
    thomasup
    Customer

    +1 on the ambient occlusion and color management.

    we currently bake all AO, as the postAO is not good enough in quality.

    but, more importantly, we usually use the filmic + high contrast color profile in blender.
    currently, we have to fall back to standard, which bleeds and clips quite heavily. so that would be a huge improvement.

    in reply to: Verge3D 3.8 pre1 available! #43438
    thomasup
    Customer

    really appreciate the alpha hashed option! will have to give it a try.

    in reply to: Verge3D 3.8 pre2 available! #43437
    thomasup
    Customer

    wow, the runtime usdz export mustve been quite the challenge.
    also, the object node will be useful!
    nice update.

    in reply to: Portfolio Visualizer BASF #41524
    thomasup
    Customer

    we used the bind puzzle code, and modified it for our purposes:

    https://www.soft8soft.com/docs/manual/en/puzzles/HTML.html#bind_element

    the bubbles are generated by vuejs in a v-for loop, and we then have a rendercallback updating all of them, setting their positions.

    it is quite some code, so you will have to look into it

Viewing 15 posts - 1 through 15 (of 55 total)