Ihave a user that is unable to turn off raytracing - the option to do so is greyed out. GeForce RTX 3090. Updated drivers to current this afternoon. After driver update, he is able to toggle from CPU to GPU raytracing but unable to turn it off.
This happens when you run VRED on an unsupported GPU or outdated driver. VRED requires a NVidia or AMD GPU with fairly recent drivers to run properly. For Intel GPUs we forced VRED to run with CPU Raytracing in the past since the drivers were very unstable and would just cause constant crashes. With VRED 2023 we dont do this anymore if the driver supports the required extensions but so far the experience might still not be good.
Sorry, didnt read correctly it seems. Can you post the vred log file you get when starting up VRED? I assume this is a broken driver installation or it is indeed a broken driver. Are you using the studio driver or the game-ready driver? For applications like VRED you should always use the studio driver.
This sounds indeed very strange. What I would recommend: Completely uninstall the nvidia driver and then do a clean install (not the usual update install) of the driver again. Depending what driver was installed previously switching from a standard driver to a DCH driver (or worse the other way around) can sometimes cause issue in my experience.
Yeah, we uninstalled the wireless card and the issue went away. Reinstalled the wireless card and the issue comes back. We're trying to get some internal IT support to help troubleshoot this now that we have a better idea what is causing the issue. I'll try to remember to come back to post an update if we figure it out.
Update - my user reported that installing the studio driver instead of the game ready driver (and performing a clean install) resolved the issue. Hope this is helpful for anyone else with this issue in the future.
it's very slow to open the graph, complex scenes almost take 10sec to open it, and as soon as i try to edit the tree, like delete something, Vred crashes.
even the files that open properly makes the system unstable, with the UI freezing for a couple of seconds every time you use the graph.
tested another pc with A3000 instead of A2000 and vred 2023 with no updates, and everything runs smoothly there. no freezes, no crashes. i'm asking ict to install roll the pc back to 2023 with no updates on my pc to understand if the issue is related to the card or the software version
No you're not. We also fight heavily with it. Some scenes work and some don't. We also have crashes with 23.1 and 23.2 files to 23.3, so for sure it has something to do with the decoupling of the scenegraph.
Just working on a car interior project at the moment, first one in vred, and was wondering what I can expect render time wise on an interior shot, the kind of data that rtt prep, so high poly lots of objects but not rediculous,
Should I be using full GI for this? Could someone explain the difference between full gi and percomputed? Alot of the time I dont see much difference, I understand full gi mode is super brute force and calculates everything, would precomputed be similar to something like irradiance map in vray?
the "Precomputed..." modes use baked indirect illumination and, depending on mode, baked ambient occlusion on the geometries (needs to be calculated during scene preparation by the "Bake Light and Shadows" module).
The Render Quality presets (Draft ...Production Quality) just change the number of samples taken (the value in the General settings tab at the top, Image samples). Maybe you don't need 2048 samples (Production Interieur) in your scene; depends on how much noise you have.
the speedup you get from photonmapping with final gathering depends a lot on the scene and settings but something between faktor 1.5 and factor 3 faster rendering is not uncommon. It might even be more depending on your willingness to tweak and setup a proper lightportal to guide the photons to where they are needed.
- Triangle size: VRED is optimized for small triangles you usually find in car models. Large Triangles are hurting performance since the bounding boxes dont adjust well to the actuall geometry. Even worse are merged objects that are far appart. General rule of thumb: The more empty space a single object has the worse the performance will be.
How far would you go with triangle size, the triangles are quite small already, whats the best way of doing this in vred? and being a car interior there arnt many areas's of large triangles most are similar size no parts are merged,
Just for testing try to rename the vrRaytracingUtilsAVX.dll found in C:\Program Files\Autodesk\VREDPro-8.04\Bin\WIN64 to something else. This will disable AVX support and use SSE4 instead, maybe this increases your performance.
3a8082e126