vred 2025 laggy

[cikho]

hello everyone.

we recently switched from vred design 2023 to 2025. some workstation also upgraded from design to pro.

no matter the version, the 2025 issues looks laggy as hell.

the viewport movents are smooth, it becomes laggy when you import new items, duplicate things, hide components in the scenegraph, assign new materials etc.

it gets worse with complex scenes.

when you make a change it appears in the view port in milliseconds and then the software freezes for a couple of seconds, it does not appear to be related to viewport complexity. this happens  when you change either simple parts or large assemblies.

it does not happen when manipulating items in the view port: scaling or moving has no impact.

I tryed to make a large assembly of cubes in vred, and up to 75k objects the issue does not seems to appear, otherwise with imported geometries (alias and catia) it's notable with 60k objects.

sometimes, if you have other software in the background vred  alt+tabs by itself.

having the task manager opened, it looks to cause some peak in processor activity on some cores, 10 to 15% processor load. no impact on gpu or network.

this problem looks similar to other we had in the past, that was crashing Vred2024:

https://forums.autodesk.com/t5/vred-forum/poor-scenegraph-performance-in-vred-2024-1-compared-to-202...

https://forums.autodesk.com/t5/vred-forum/perfomance-issue-vred-2023-3-1-and-2023-4/m-p/12011046#M10...

https://forums.autodesk.com/t5/vred-forum/vred-2023-crashing-when-opening-2022-files/m-p/11836859#M1...

[cikho]

another lag i've found is the selection of objects in large assemblies when the material editor is opened.

you click an object and the software freezes for a couple of seconds.

imho it still has something to do with UI performance..

it was not happening in 2023 versions..

[Christian_Garimberti]

Hi @cikho, just to exclude things...

Have you tried to turn off reference monitoring? Go to Edit, Preferences, Scene, References, tab Update Monitoring and disable it.

This could explain why, with tons of cube you don't have the issue and instead with CAD imported yes.

best

Chris

[cikho]

yes. no changes.

tryed to remove all reference from the file, to delete all meta data, no changes.

this happens on all our laptop machines setups

- intel i7- 11850H - 2.5Ghz_nvidia rtx A2000-4Gb_64Gb ram

- intel i7- 11850H - 2.5Ghz_nvidia rtx A3000-6Gb_32Gb ram

i still strongly believe this is due to UI decoupling and its performace.

[cikho]

additional testing:

hiding objects or deleting them with the scengraph closed works perfectly, with no lag.

as soon as you open the scenegraph, vred tries to update it and lags.

it defintely has something to do with UI performance, again... same issue as 2 years ago still not solved.. sometimes i ask myself why am I paying 5K for this 😐

[Christian_Garimberti]

Just to be sure.... have you installed the 2025 Beta on those laptop? There was a wrong preference import about the reference monitoring that could impact. If yes check the reference monitoring time option.

Have you tried to reset all the preferences?

I know your answer... but, i ask... could you share something to test?

I'm working on the 2025 from the release and i never had this issue.

if you want and if you can, you can write me a private message.

best

Chris

[cikho]

no, the version is the 2025 pro\design release available through desktop app.

tryed to change all the ref monitor parameters, but nothing changes.

maybe it has to do with processor performances, if you have a more powerfull cpu, with more single core performance than mine it might be possible that the lag decreases to the extent you cannot notice it.

unfortunately all my scenes are company IP, and contains quite sensible data, so i canno share them..

i might try to create a dedicated scene with random geometry and try to replicate the issue..

[Christian_Garimberti]

ok, if you can send something, i will try on my laptop (Intel(R) Core(TM) i7-9850H CPU @ 2.60GHz 2.59 GHz Quadro P2000 4Gb) to have a more or less equal test and on my Workstation to compare with something more powerful.

Best

Chris

[cikho]

attached a video test.

this was made by opening the sample genesis scene, duplicating geometry 32 times, reaching 27k + nodes.

isolating a single instance in order to keep framerate high.

take one object and hide it with ctrl+j while moving camera.

with graph opened it lags a few seconds, with graph closed it keeps consistent framerate.

no reference in the file.

the problem looks graph and complexity related..

it might be possible that some lines in the code asks a complete updated of the object tree every time something changes. if the tree is complex it takes more time..

it's fun because it works also with empty nodes.

tkae the genesis scene, create a random number of empty node with ctrl+g. group the empty nodes and duplicate the new group of  groups randomly. group these again and duplicate again. you esily reach 100k + empty nodes and you get the lag when doing ctrl+j while rotating camera.

[cikho]

@Christian_Garimberti 

here is a second test.

i'm using one of my usual file.. hope that showing a common helicopter tail won't get me to jail XD.

first part is vred design 2023.

as you see you actually get  a framrate drop when hiding\showing an objetc. but the drop is acceptable (less than 1sec) and not dependent on graph display.

second part (there is a small screen freeze right before the change) is vred pro 2025.

you see that the software freezes for something like 5 seconds, but only when the graph is opened.

when scenegraph is hidden framerate drop is comparable to 2023

[cikho]

just to recap the issue:

action	scenegraph	Material editor	lag
Hide an object	opened	opened	yes
Hide an object	Closed	Opened	No
Select an object	opened	opened	Yes
Select an object	opened	closed	No
Select an object	closed	opened	no
Select object through scengraph	opened	opened	No (material of selected object is not selected)
Assign a material	opened	opened	Yes
Assign a material	Closed	opened	yes
Move object in viewport	opened	opened	no

[Christian_Garimberti]

Hi, doing your test on Vred 2025 with the Automotive Genesis i see that on my laptop i got the same lag with the Scenegraph opened.

But i also see that with that scene i almost fill all my memories... RAM and VRAM

I also tried in Vred 2023.4 and i see the same lag, maybe more. i do not have older Vred installed to try...

Tomorrow i will try on my workstation, just for another test.

best

Chris

[Christian_Garimberti]

Hi @cikho i made tests also on my workstation and i got the same lag. No matter the more power of the pc.

In which version of Vred 2023 you see you are faster? in Vred 2023.4 i see the same lag.

Maybe Vred 2023.2? in Vred 2023.3 there is the new decoupled scenegraph...

Chris

[cikho]

@Christian_Garimberti the video comparison of the helo tail of the previous posts were made with 2023.0, without the UI decoupling.

as i told before, i really think this has to do with the decoupling, maybe with some data transfer between different parts of the software\code.

in the past it was making the nvidia driver crash badly on startup or as soon as you opened the scenegraph, probably flooding the VRAM or something like that.

now it looks like they got some workaround to improve performance enough to make the system stable, but the problem it's still there.

[Christian_Garimberti]

I suppose the same.

Maybe one of the Autodesk guys will take your report and test into account for the next release.

Best

Chris

[cikho]

@Christian_Garimberti 

made additional testing with my personal laptop:

i7 13705H

16Gb ram

nvidia rtx 4060 8Gb

i clearly see the lag here too..

the funny thing is that, having more control on my personal laptop than on my company pc, it's pretty clear that when the lag appears, the processor peaks up.

it even engages the turbo boost, peaking at 4.5Ghz (nominal is 2.4Ghz)

the usage % goes up at 100% only on 1 core (and, funny, not the same one)

[cikho]

i was wondering:

is there a way to display in a cmd console or similar the commands that vred runs for certain actions?

i showcase professional there was a way to run the software in console mode.

[Christian_Garimberti]

Yes, just add -console in your desktop icon at the end of the exe path

... bin\WIN64\VREDPro.exe" -console

But i don't think you will find something relevant for this problem...

Best

Chris

[cikho]

nice!

in showcase you could also run a plugin that displayed all the python calls.

[sinje_thiedemann]

Hi and thanks for taking the time to report this.

We're looking into it.

We identified the Scenegraph tags to be one part of the problem, especially when they are attached to many (thousands) of nodes. Currently there is no other workaround than either closing the Scenegraph module, or to delete the tags (if you don't need them). Tags are created during file import for some formats (e.g. Alias layers), so that can explain why you see the issue for some scenes but not for others with similar number of nodes.

This is a script that deletes all tags from nodes (not from materials):

tags = vrMetadataService.getAllTags()
for t in tags:
    objs = vrMetadataService.getObjectsWithTag(t)
    objs = [obj for obj in objs if obj.isType(vrdNode)]
    vrMetadataService.removeTags(objs, [t])

 Kind regards