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

elk

Forum Replies Created

Viewing 15 posts - 121 through 135 (of 168 total)
1 2 3 … 8 9 10 11 12
  • Author
    Posts
  • 2019-03-14 at 11:56 pm in reply to: Lighting went away #12792
    elk
    Customer

    Looks like the Chrome update issue, check this blog post;

    Verge3D 2.11.1 Hotfix Available

    2019-03-14 at 10:13 pm in reply to: Shadows in 2.8beta #12786
    elk
    Customer

    So i did some more digging and managed to reproduce the bug in a new app/blend file (see attached).

    So the problem seems to be that both scenes are exported i guess, and what ever scene is the “dominant”/last(?) scene will dictate the settings. I guess things might just get overwritten so whatever is last in line will win.

    The file contains two scenes, almost identical. One is set to Basic and one to Soft PCF for map type, but no mater what scene i export the settings from one gets used ( the one called Basic in my example). Just copy it to a new app or set it up from scratch for yourself to try it out.

    I made an extrusion on the plane in one of the scenes, but objects and verts seem the same in the console log no matter what scene i export, this was what lead me to think that the whole file may be exported not just the active scene. I assume this is not the way it is meant to behave.

    So my workaround for now is setting the Verge3D render settings up in my Cycles Scene.

    I guess this might be tied to my otter issues with the exporter from this thread;

    Exporting scenes

    I know this might be tied in to the revamp of the whole outline sceneGraph thingi, but if there is any way to get export to respect scenes it would be really great.

    Really appreciate you taking a look at this, and please let me know if you need further details.

    Attachments:
    You must be logged in to view attached files.
    2019-03-14 at 6:56 pm in reply to: Material and shade #12783
    elk
    Customer

    If in 2.8 try using the eevee engine as render engine, then shadows will be affected by blenders own shadow settings for sun lamps for instance (se attached image). Havent tested Exponent and Bleed bias yet myself, but softness and bias should help you tune the problem i would think, also try the different “Map Side” settings in the Verge3D settings in render tab.

    Hopefully somone else can chime in if i missed somthing or if you got furter problems.

    2019-03-14 at 1:04 pm in reply to: Shadows in 2.8beta #12753
    elk
    Customer

    I will try to minimize the file and attach. I suspect it might be a blender beta issue, and the fact that the file has been through quite some versions of the beta by now.

    The “ERROR: Invalid count 0” did not give you a clue either ? <– this seems to be some of the cameras from the other scene, I just found out …

    I will try to have a file ready for you later tonight.

    2019-03-14 at 11:54 am in reply to: Shadows in 2.8beta #12739
    elk
    Customer

    Hello again.

    It seems I am not quite rid of this issue yet. I separated my file into two scenes, one for rendering and one for Verge3D, and when i appended just the Verge3D scene into a fresh .blend file of a newly created app it worked fine. But today i wanted to append my render scene to the same file (just to keep my entire workflow in one place), but that made the jagged shadows issue come back. Removing the just imported (rendering) scene fixed it again, so i checked the console log…

    Exporting with my verge scene active while the rendering scene also in the file would produce a lot more output in the console, I thought the export only would consider the current scene ? after all , only objects from the current selected scene seems to show up in the selectors in puzzles. And i don’t think anything should get linked back up when i append one scene at a time …

    Anyway, i noticed a error in the export when i have both scenes in the file, (se attached). Could this be some part of the problem? the error message is a bit non-descriptive …

    2019-03-14 at 11:05 am in reply to: Material and shade #12735
    elk
    Customer

    Try turning down the softness a bit, and you will get less “banding”. Also try connecting the two walls, or extending the small one back to reduce the “light leaks” between the objects. you might want to adjust your bias also if the shadow under the plant does not show up.

    Also there is a tutorial here; https://www.youtube.com/watch?v=BqK5ZK0W4xc

    Settings might need to be different to your project depending on the scale of your scene.

    Just been playing around with shadows for a couple of days so might be more settings you could play around with. Please add anyone if i missed something….

    2019-03-14 at 9:22 am in reply to: Chrome 73 blackout rendering fix #12714
    elk
    Customer

    :good:

    2019-03-13 at 10:55 pm in reply to: Shadows in 2.8beta #12680
    elk
    Customer

    Finally got around my soft shadows not working issue. Just thought I would leave a note if someone else gets a similar problem. My workaround after testing all sorts of things was to create a new project and then append my scene into the new application blend file from the old file, moved my textures over to the new folder and everything seems to work.

    2019-03-13 at 2:35 pm in reply to: Chrome update broke enviorment maps …. #12663
    elk
    Customer

    thanks Yuri :good:

    2019-03-13 at 1:18 pm in reply to: Chrome update broke enviorment maps …. #12648
    elk
    Customer

    My CPU was not happy when i turned of hardware, and i got like 1 frame every 2 seconds, but thanks for the tip PD. I think i got some optimization still to do on my project ;)

    2019-03-13 at 1:07 pm in reply to: Rendering Black Background #12646
    elk
    Customer

    Thanks Yuri. Also a bit of info on what was wrong would be nice once you get the update up. Did Chrome deprecate something, or was something wrong in in Verge3D implementation that made it break ? When “old” functionality breaks like this it could cause a lot of work (and potential loss of goodwill) for people with a lot of live projects. Thanks for taking action quickly tho :good:

    2019-03-13 at 9:36 am in reply to: Rendering Black Background #12632
    elk
    Customer

    Had the same issue, I think it is a Chrome update that caused the problem;

    Chrome update broke enviorment maps ….

    2019-03-12 at 3:18 pm in reply to: Verge3D 2.11 pre2 build available! #12614
    elk
    Customer

    No worries Yuri. As mentioned not a kritical featur for me yet, but good to know you put it in the tracker, then I know its on the horizon somwhere :good:

    2019-03-12 at 2:55 pm in reply to: Shadows in 2.8beta #12607
    elk
    Customer

    That seemed to work for the resolution, I should have tried that, but was just expecting to find it in the light settings like in 2.79.

    Edit: btw; had to change cascade size, could not find a “Map Size” …

    However i am still not getting the “blur” in the edges. I set up a new app from scratch, and using similar settings seems to be doing a good job even with smaller map size (see attached). But now i know where the settings are I can have a tweak to see if some of my settings are causing the problem. If you or anyone spot my mistake feel free to post a comment.

    Thanks for the quick reply Yuri :good:

    2019-03-11 at 4:25 pm in reply to: stats/profiler #12554
    elk
    Customer

    Good tip Gary, will check that out. Thanks :good:

  • Author
    Posts
Viewing 15 posts - 121 through 135 (of 168 total)
1 2 3 … 8 9 10 11 12