Richard Haseltine said:

ArtRoulade said:

Richard Haseltine said:

RustyBln said:

Richard Haseltine said:

ArtRoulade said:

RustyBln said:

Richard Haseltine said:

yonashald said:

Richard Haseltine said:

yonashald said:

Falco said:

I ended up downgrading from the 5090 back to my 3090 so i could use 4.24 again, being able to work more quickly/smoothly in the viewport for production outweighed the 3x faster render times since I can queue those.  $3000 paperweight sitting on my desk until things hopefully improve .  

 

It is seriously embarassing how long this has been a problem that hasn't been fixed yet. 

Whata re you meaning? DS 4 will never be able to use 50x0 cards, nVidia changed the way they compile the render engne and that cannot be used with DS 4. The only way to itengrate the iray versions required for 50x0 card support is to make changes that break compatibility with DS 4, in other words a full new version. Fortunately DS 6 was already in development and can use the versions of Iray required for 50x0 support.

What I'm refeering to is how insanely bad the viewport on the BETA is compared to DS 4, you can act like it isn't but it is, it laggs/stutters way more than DS4, and considering that is the only real option for people with newer graphic cards, and yeah its a "beta" but I would expect that they would be able to do something about it within a year, but I guess I was wrong.

No one is acting like it isn't so, but it does eem to vary from user to user - which makes it much harder to figure out what is happening and how to address it.

 

As far as I can see it almost every user here with a 5090 card reported that issue with the BETA. I'm one of them. Just test your own software with a 5090 card and a bigger scene and you should immediately notice the bad viewport performance compared to 4.24. Can't be that difficult. 

For example using a scene in Daz Studio 6.25 with New York Stores | Daz 3D on a 5090 the camera movement becomes sluggish even without characters.

In DZ 4.24 with a 4090 everything runs smooth using the same scene. 1st pc - AMD 9800X3D + NVidia 5090; 2nd pc - AMD 5900X + NVidia 4090.

In which mode? I have a 5090 here, Texture Shaded seemed fine, Iray of coursedrops duriing movement but settled down as soon as I stopped, Filament also seems fine.

Basically every mode is barely usable. So you're saying the viewport performance with the BETA is the same as with 4.24 on your PC? I'm sorry to say that, but that's really hard to believe. I tried the DAZ BETA on different PCs, with a fresh installed Win11 and a clean driver installation. It was always the same. Viewport performance on 4.24 was perfectly fine while it's unusable with the BETA. 

Certainly it seems pretty mucxh the same, and perfectly adequate. I didn't time it in FPS, the non-Iray modes (including Universal) are responsive in realtime, as far as I can tell.

Don't get me wrong, but you've got a HUGE problem here, and if it isn't fixed, I can easily imagine that, over time, MANY users will switch to other software like Blender, because as it stands now, DAZ 26 is simply unusable for everyday work. 

Please load two storefronts into a scene for further testing and move the camera while in universal or texture-shaded mode. I’m not writing this out of boredom. The same problem also occurs on a third system with an AMD 7940HS and a 4090 Mobile.

I did have two copies of the scene loaded, well the two different files under Environment which is what I thought was meant.

There are scenes where the camera movements works fluently but in other scenes I have the same problem as mentioned.

New York Stores | Daz 3D

Exactly those two different storefronts.

I just installed the new preview windows update KB5089573 and my problem seems fixed. I'll have to test it on my other systems.  

ArtRoulade said:

Richard Haseltine said:

RustyBln said:

Richard Haseltine said:

ArtRoulade said:

RustyBln said:

Richard Haseltine said:

yonashald said:

Richard Haseltine said:

yonashald said:

Falco said:

I ended up downgrading from the 5090 back to my 3090 so i could use 4.24 again, being able to work more quickly/smoothly in the viewport for production outweighed the 3x faster render times since I can queue those.  $3000 paperweight sitting on my desk until things hopefully improve .  

 

It is seriously embarassing how long this has been a problem that hasn't been fixed yet. 

Whata re you meaning? DS 4 will never be able to use 50x0 cards, nVidia changed the way they compile the render engne and that cannot be used with DS 4. The only way to itengrate the iray versions required for 50x0 card support is to make changes that break compatibility with DS 4, in other words a full new version. Fortunately DS 6 was already in development and can use the versions of Iray required for 50x0 support.

What I'm refeering to is how insanely bad the viewport on the BETA is compared to DS 4, you can act like it isn't but it is, it laggs/stutters way more than DS4, and considering that is the only real option for people with newer graphic cards, and yeah its a "beta" but I would expect that they would be able to do something about it within a year, but I guess I was wrong.

No one is acting like it isn't so, but it does eem to vary from user to user - which makes it much harder to figure out what is happening and how to address it.

 

As far as I can see it almost every user here with a 5090 card reported that issue with the BETA. I'm one of them. Just test your own software with a 5090 card and a bigger scene and you should immediately notice the bad viewport performance compared to 4.24. Can't be that difficult. 

For example using a scene in Daz Studio 6.25 with New York Stores | Daz 3D on a 5090 the camera movement becomes sluggish even without characters.

In DZ 4.24 with a 4090 everything runs smooth using the same scene. 1st pc - AMD 9800X3D + NVidia 5090; 2nd pc - AMD 5900X + NVidia 4090.

In which mode? I have a 5090 here, Texture Shaded seemed fine, Iray of coursedrops duriing movement but settled down as soon as I stopped, Filament also seems fine.

Basically every mode is barely usable. So you're saying the viewport performance with the BETA is the same as with 4.24 on your PC? I'm sorry to say that, but that's really hard to believe. I tried the DAZ BETA on different PCs, with a fresh installed Win11 and a clean driver installation. It was always the same. Viewport performance on 4.24 was perfectly fine while it's unusable with the BETA. 

Certainly it seems pretty mucxh the same, and perfectly adequate. I didn't time it in FPS, the non-Iray modes (including Universal) are responsive in realtime, as far as I can tell.

Don't get me wrong, but you've got a HUGE problem here, and if it isn't fixed, I can easily imagine that, over time, MANY users will switch to other software like Blender, because as it stands now, DAZ 26 is simply unusable for everyday work. 

Please load two storefronts into a scene for further testing and move the camera while in universal or texture-shaded mode. I’m not writing this out of boredom. The same problem also occurs on a third system with an AMD 7940HS and a 4090 Mobile.

I did have two copies of the scene loaded, well the two different files under Environment which is what I thought was meant.

There are scenes where the camera movements works fluently but in other scenes I have the same problem as mentioned.

New York Stores | Daz 3D

jmucchiello said:

NorthOf45 said:

Yes, the supplied scenes use a lot of instancing, but is surprisingly light on the memory load. The templates with grass (2 of the 4)  use thousands of grass patch instances, but, again, surprisingly light on the memory. Everything shows, but you can't see all of them at the same time (360 degree environment). The Filament view looks off, so some tweaking will be needed.

Light? If I turn on IRAY with any of the default scenes, I may as well kill Daz from task manager immediately. And I have a 4090 and a i9 CPU.

 

I was running DS 4.23 beta at the time, and it was a little sluggish with my 1080, but totally useable. Now I have an RTX 4000 Ada Generation, and it is smooth panning around with Iray, on the same 4.23 beta. On DS 6.25, though, it is a different story. Slow as molasses in January, uphill, in any drawing mode. Not sure why, but I have never seen such a drastic speed difference. All render settings are identical in both versions.

jmucchiello said:

NorthOf45 said:

Yes, the supplied scenes use a lot of instancing, but is surprisingly light on the memory load. The templates with grass (2 of the 4)  use thousands of grass patch instances, but, again, surprisingly light on the memory. Everything shows, but you can't see all of them at the same time (360 degree environment). The Filament view looks off, so some tweaking will be needed.

Light? If I turn on IRAY with any of the default scenes, I may as well kill Daz from task manager immediately. And I have a 4090 and a i9 CPU.

 

I was running DS 4.23 beta at the time, and it was a little luggish with my 1080, but totally useable. Now I have an RTX 400 Ada Generation, and it is smooth panning around with Iray, on the same 4.23 beta. On DS 6.25, though, it is a different story. Slow as molasses in January, uphill, in any drawing mode. Not sure why, but I have never seen such a drastic speed differnce. All render settings are identical in both versions.

Filament only has an issue with collapsed instances as used in Ultrascenery and by some PAs

normal instances no matter how many are fine

NorthOf45 said:

Yes, the supplied scenes use a lot of instancing, but is surprisingly light on the memory load. The templates with grass (2 of the 4)  use thousands of grass patch instances, but, again, surprisingly light on the memory. Everything shows, but you can't see all of them at the same time (360 degree environment). The Filament view looks off, so some tweaking will be needed.

Light? If I turn on IRAY with any of the default scenes, I may as well kill Daz from task manager immediately. And I have a 4090 and a i9 CPU.

Richard Haseltine said:

RustyBln said:

Richard Haseltine said:

ArtRoulade said:

RustyBln said:

Richard Haseltine said:

yonashald said:

Richard Haseltine said:

yonashald said:

Falco said:

I ended up downgrading from the 5090 back to my 3090 so i could use 4.24 again, being able to work more quickly/smoothly in the viewport for production outweighed the 3x faster render times since I can queue those.  $3000 paperweight sitting on my desk until things hopefully improve .  

 

It is seriously embarassing how long this has been a problem that hasn't been fixed yet. 

Whata re you meaning? DS 4 will never be able to use 50x0 cards, nVidia changed the way they compile the render engne and that cannot be used with DS 4. The only way to itengrate the iray versions required for 50x0 card support is to make changes that break compatibility with DS 4, in other words a full new version. Fortunately DS 6 was already in development and can use the versions of Iray required for 50x0 support.

What I'm refeering to is how insanely bad the viewport on the BETA is compared to DS 4, you can act like it isn't but it is, it laggs/stutters way more than DS4, and considering that is the only real option for people with newer graphic cards, and yeah its a "beta" but I would expect that they would be able to do something about it within a year, but I guess I was wrong.

No one is acting like it isn't so, but it does eem to vary from user to user - which makes it much harder to figure out what is happening and how to address it.

 

As far as I can see it almost every user here with a 5090 card reported that issue with the BETA. I'm one of them. Just test your own software with a 5090 card and a bigger scene and you should immediately notice the bad viewport performance compared to 4.24. Can't be that difficult. 

For example using a scene in Daz Studio 6.25 with New York Stores | Daz 3D on a 5090 the camera movement becomes sluggish even without characters.

In DZ 4.24 with a 4090 everything runs smooth using the same scene. 1st pc - AMD 9800X3D + NVidia 5090; 2nd pc - AMD 5900X + NVidia 4090.

In which mode? I have a 5090 here, Texture Shaded seemed fine, Iray of coursedrops duriing movement but settled down as soon as I stopped, Filament also seems fine.

Basically every mode is barely usable. So you're saying the viewport performance with the BETA is the same as with 4.24 on your PC? I'm sorry to say that, but that's really hard to believe. I tried the DAZ BETA on different PCs, with a fresh installed Win11 and a clean driver installation. It was always the same. Viewport performance on 4.24 was perfectly fine while it's unusable with the BETA. 

Certainly it seems pretty mucxh the same, and perfectly adequate. I didn't time it in FPS, the non-Iray modes (including Universal) are responsive in realtime, as far as I can tell.

Don't get me wrong, but you've got a HUGE problem here, and if it isn't fixed, I can easily imagine that, over time, MANY users will switch to other software like Blender, because as it stands now, DAZ 26 is simply unusable for everyday work. 

Please load two storefronts into a scene for further testing and move the camera while in universal or texture-shaded mode. I’m not writing this out of boredom. The same problem also occurs on a third system with an AMD 7940HS and a 4090 Mobile.

There are scenes where the camera movements works fluently but in other scenes I have the same problem as mentioned.

New York Stores | Daz 3D

RustyBln said:

Richard Haseltine said:

ArtRoulade said:

RustyBln said:

Richard Haseltine said:

yonashald said:

Richard Haseltine said:

yonashald said:

Falco said:

I ended up downgrading from the 5090 back to my 3090 so i could use 4.24 again, being able to work more quickly/smoothly in the viewport for production outweighed the 3x faster render times since I can queue those.  $3000 paperweight sitting on my desk until things hopefully improve .  

 

It is seriously embarassing how long this has been a problem that hasn't been fixed yet. 

Whata re you meaning? DS 4 will never be able to use 50x0 cards, nVidia changed the way they compile the render engne and that cannot be used with DS 4. The only way to itengrate the iray versions required for 50x0 card support is to make changes that break compatibility with DS 4, in other words a full new version. Fortunately DS 6 was already in development and can use the versions of Iray required for 50x0 support.

What I'm refeering to is how insanely bad the viewport on the BETA is compared to DS 4, you can act like it isn't but it is, it laggs/stutters way more than DS4, and considering that is the only real option for people with newer graphic cards, and yeah its a "beta" but I would expect that they would be able to do something about it within a year, but I guess I was wrong.

No one is acting like it isn't so, but it does eem to vary from user to user - which makes it much harder to figure out what is happening and how to address it.

 

As far as I can see it almost every user here with a 5090 card reported that issue with the BETA. I'm one of them. Just test your own software with a 5090 card and a bigger scene and you should immediately notice the bad viewport performance compared to 4.24. Can't be that difficult. 

For example using a scene in Daz Studio 6.25 with New York Stores | Daz 3D on a 5090 the camera movement becomes sluggish even without characters.

In DZ 4.24 with a 4090 everything runs smooth using the same scene. 1st pc - AMD 9800X3D + NVidia 5090; 2nd pc - AMD 5900X + NVidia 4090.

In which mode? I have a 5090 here, Texture Shaded seemed fine, Iray of coursedrops duriing movement but settled down as soon as I stopped, Filament also seems fine.

Basically every mode is barely usable. So you're saying the viewport performance with the BETA is the same as with 4.24 on your PC? I'm sorry to say that, but that's really hard to believe. I tried the DAZ BETA on different PCs, with a fresh installed Win11 and a clean driver installation. It was always the same. Viewport performance on 4.24 was perfectly fine while it's unusable with the BETA. 

Certainly it seems pretty mucxh the same, and perfectly adequate. I didn't time it in FPS, the non-Iray modes (including Universal) are responsive in realtime, as far as I can tell.

Don't get me wrong, but you've got a HUGE problem here, and if it isn't fixed, I can easily imagine that, over time, MANY users will switch to other software like Blender, because as it stands now, DAZ 26 is simply unusable for everyday work. 

Richard Haseltine said:

ArtRoulade said:

RustyBln said:

Richard Haseltine said:

yonashald said:

Richard Haseltine said:

yonashald said:

Falco said:

I ended up downgrading from the 5090 back to my 3090 so i could use 4.24 again, being able to work more quickly/smoothly in the viewport for production outweighed the 3x faster render times since I can queue those.  $3000 paperweight sitting on my desk until things hopefully improve .  

 

It is seriously embarassing how long this has been a problem that hasn't been fixed yet. 

Whata re you meaning? DS 4 will never be able to use 50x0 cards, nVidia changed the way they compile the render engne and that cannot be used with DS 4. The only way to itengrate the iray versions required for 50x0 card support is to make changes that break compatibility with DS 4, in other words a full new version. Fortunately DS 6 was already in development and can use the versions of Iray required for 50x0 support.

What I'm refeering to is how insanely bad the viewport on the BETA is compared to DS 4, you can act like it isn't but it is, it laggs/stutters way more than DS4, and considering that is the only real option for people with newer graphic cards, and yeah its a "beta" but I would expect that they would be able to do something about it within a year, but I guess I was wrong.

No one is acting like it isn't so, but it does eem to vary from user to user - which makes it much harder to figure out what is happening and how to address it.

 

As far as I can see it almost every user here with a 5090 card reported that issue with the BETA. I'm one of them. Just test your own software with a 5090 card and a bigger scene and you should immediately notice the bad viewport performance compared to 4.24. Can't be that difficult. 

For example using a scene in Daz Studio 6.25 with New York Stores | Daz 3D on a 5090 the camera movement becomes sluggish even without characters.

In DZ 4.24 with a 4090 everything runs smooth using the same scene. 1st pc - AMD 9800X3D + NVidia 5090; 2nd pc - AMD 5900X + NVidia 4090.

In which mode? I have a 5090 here, Texture Shaded seemed fine, Iray of coursedrops duriing movement but settled down as soon as I stopped, Filament also seems fine.

Basically every mode is barely usable. So you're saying the viewport performance with the BETA is the same as with 4.24 on your PC? I'm sorry to say that, but that's really hard to believe. I tried the DAZ BETA on different PCs, with a fresh installed Win11 and a clean driver installation. It was always the same. Viewport performance on 4.24 was perfectly fine while it's unusable with the BETA. 
Don't get me wrong, but you've got a HUGE problem here, and if it isn't fixed, I can easily imagine that, over time, MANY users will switch to other software like Blender, because as it stands now, DAZ 26 is simply unusable for everyday work. 

Richard Haseltine said:

ArtRoulade said:

RustyBln said:

Richard Haseltine said:

yonashald said:

Richard Haseltine said:

yonashald said:

Falco said:

I ended up downgrading from the 5090 back to my 3090 so i could use 4.24 again, being able to work more quickly/smoothly in the viewport for production outweighed the 3x faster render times since I can queue those.  $3000 paperweight sitting on my desk until things hopefully improve .  

 

It is seriously embarassing how long this has been a problem that hasn't been fixed yet. 

Whata re you meaning? DS 4 will never be able to use 50x0 cards, nVidia changed the way they compile the render engne and that cannot be used with DS 4. The only way to itengrate the iray versions required for 50x0 card support is to make changes that break compatibility with DS 4, in other words a full new version. Fortunately DS 6 was already in development and can use the versions of Iray required for 50x0 support.

What I'm refeering to is how insanely bad the viewport on the BETA is compared to DS 4, you can act like it isn't but it is, it laggs/stutters way more than DS4, and considering that is the only real option for people with newer graphic cards, and yeah its a "beta" but I would expect that they would be able to do something about it within a year, but I guess I was wrong.

No one is acting like it isn't so, but it does eem to vary from user to user - which makes it much harder to figure out what is happening and how to address it.

 

As far as I can see it almost every user here with a 5090 card reported that issue with the BETA. I'm one of them. Just test your own software with a 5090 card and a bigger scene and you should immediately notice the bad viewport performance compared to 4.24. Can't be that difficult. 

For example using a scene in Daz Studio 6.25 with New York Stores | Daz 3D on a 5090 the camera movement becomes sluggish even without characters.

In DZ 4.24 with a 4090 everything runs smooth using the same scene. 1st pc - AMD 9800X3D + NVidia 5090; 2nd pc - AMD 5900X + NVidia 4090.

In which mode? I have a 5090 here, Texture Shaded seemed fine, Iray of coursedrops duriing movement but settled down as soon as I stopped, Filament also seems fine.

In texture shaded mode it is real sluggish espically when displaying both storefronts. It's less chucky in universal mode but also not usable. Same problem for the 4090 in DZ 6.25

Testing the same scene in Daz 4.24 everything runs smoothly.

Richard Haseltine said:

ArtRoulade said:

RustyBln said:

Richard Haseltine said:

yonashald said:

Richard Haseltine said:

yonashald said:

Falco said:

I ended up downgrading from the 5090 back to my 3090 so i could use 4.24 again, being able to work more quickly/smoothly in the viewport for production outweighed the 3x faster render times since I can queue those.  $3000 paperweight sitting on my desk until things hopefully improve .  

 

It is seriously embarassing how long this has been a problem that hasn't been fixed yet. 

Whata re you meaning? DS 4 will never be able to use 50x0 cards, nVidia changed the way they compile the render engne and that cannot be used with DS 4. The only way to itengrate the iray versions required for 50x0 card support is to make changes that break compatibility with DS 4, in other words a full new version. Fortunately DS 6 was already in development and can use the versions of Iray required for 50x0 support.

What I'm refeering to is how insanely bad the viewport on the BETA is compared to DS 4, you can act like it isn't but it is, it laggs/stutters way more than DS4, and considering that is the only real option for people with newer graphic cards, and yeah its a "beta" but I would expect that they would be able to do something about it within a year, but I guess I was wrong.

No one is acting like it isn't so, but it does eem to vary from user to user - which makes it much harder to figure out what is happening and how to address it.

 

As far as I can see it almost every user here with a 5090 card reported that issue with the BETA. I'm one of them. Just test your own software with a 5090 card and a bigger scene and you should immediately notice the bad viewport performance compared to 4.24. Can't be that difficult. 

For example using a scene in Daz Studio 6.25 with New York Stores | Daz 3D on a 5090 the camera movement becomes sluggish even without characters.

In DZ 4.24 with a 4090 everything runs smooth using the same scene. 1st pc - AMD 9800X3D + NVidia 5090; 2nd pc - AMD 5900X + NVidia 4090.

In which mode? I have a 5090 here, Texture Shaded seemed fine, Iray of coursedrops duriing movement but settled down as soon as I stopped, Filament also seems fine.

So you alleging that for you, the viewport of 4.24 and the BETA are pretty much the same with regards to lag/stutter? because if so, I would love to see video proof of that.

>> is DAZ adding emission?

Hi Wendy! Nice to see you here. ^__^

Nope, no emission map used. For the record, this happens even with just the diffuse map and nothing else. 

In the attached image, I show the wireframe and the I-ray render just to show the artifacts around the red areas are not even in the geometry - they are just in the texture, so it's not even related to the geometry. Then I thought - it must be the bump map, but it happens with or without it. Then I thought - it must be the subdivision, but it happens without it. 

Whatever this is, it only happens in I-ray, which is why I am asking in this thread. I am using DS 4.24. It shows perfectly clean in OpenGL previews in both Blender (EEVEE) and DS Filament. It also shows fine in Cycles renders in both Blender and Poser. It only shows blotched in DS4 if rendered in I-Ray. Very odd.

Dartanbeck said:

It's really neat how the promos in this new set could easily be used as conceptual artwork for the story I'm working on right freaking Now!!! :)

Is Rosie taking a hike to China? ;)
-
To reproduce the other part of my lost post ...
Thanks to everyone pointing out Filament/FilaToon to me.
I toyed around with it for a while, it seems a bit buggy but quite fun to use.
I´ll keep it in mind for future releases, but I am not sure yet what can be done on the creator side ... it seems to mostly work with Iray sets.

Well, speaking of which...
As happy as I was about compressed HDRIs working with Iray again, they don´t with Filament. :(
So I have submitted an update for Wuxia Mountains to Daz, which will switch it back to uncompressed HDRIs.
Compatibility over file-size I guess. ;)

Hi everyone,

Just a quick question. I am having an odd issue with I-ray, and I wonder if I am doing something wrong. I made this new shoe in Blender, and the PBR textures render fine in EEVEE, in Cycles and also in DS Filament, but renders jagged in I-Ray (see example below). I first thought it could be caused by subdivision, but the same happens without it. I have also tried with and without the bump map or without converting to SubDiv, and it makes no difference. The shoe is not rigged yet, just a prop by now. I don't want to rig it before I resolve this. :)

I would appreciate any hints. ^___^

Thanks,

--=Ken

ArtRoulade said:

RustyBln said:

Richard Haseltine said:

yonashald said:

Richard Haseltine said:

yonashald said:

Falco said:

I ended up downgrading from the 5090 back to my 3090 so i could use 4.24 again, being able to work more quickly/smoothly in the viewport for production outweighed the 3x faster render times since I can queue those.  $3000 paperweight sitting on my desk until things hopefully improve .  

 

It is seriously embarassing how long this has been a problem that hasn't been fixed yet. 

Whata re you meaning? DS 4 will never be able to use 50x0 cards, nVidia changed the way they compile the render engne and that cannot be used with DS 4. The only way to itengrate the iray versions required for 50x0 card support is to make changes that break compatibility with DS 4, in other words a full new version. Fortunately DS 6 was already in development and can use the versions of Iray required for 50x0 support.

What I'm refeering to is how insanely bad the viewport on the BETA is compared to DS 4, you can act like it isn't but it is, it laggs/stutters way more than DS4, and considering that is the only real option for people with newer graphic cards, and yeah its a "beta" but I would expect that they would be able to do something about it within a year, but I guess I was wrong.

No one is acting like it isn't so, but it does eem to vary from user to user - which makes it much harder to figure out what is happening and how to address it.

 

As far as I can see it almost every user here with a 5090 card reported that issue with the BETA. I'm one of them. Just test your own software with a 5090 card and a bigger scene and you should immediately notice the bad viewport performance compared to 4.24. Can't be that difficult. 

For example using a scene in Daz Studio 6.25 with New York Stores | Daz 3D on a 5090 the camera movement becomes sluggish even without characters.

In DZ 4.24 with a 4090 everything runs smooth using the same scene. 1st pc - AMD 9800X3D + NVidia 5090; 2nd pc - AMD 5900X + NVidia 4090.

In which mode? I have a 5090 here, Texture Shaded seemed fine, Iray of coursedrops duriing movement but settled down as soon as I stopped, Filament also seems fine.

Daz is not allowed to distribute 3DL in DS because Daz's license period ended. Extending the license would not help because the version of 3DL in DS is very old and Daz 3DL shaders are incompatible with current versions of 3DL.
 

Daz 3DL is supported up to DS4.23 and many 3DL surfaces still work in DS 4.24 and up. Fancy shaders will not work past DS4.23 . Many 3DL shaders and materials can be converted to Iray and many also work in Filament and Iray with some tweaking. DS has limited means of converting shaders and materials between renderers.

 Hope that was helpful and not too pedantic.

I agree with everyone complaining about viewport performance in 6.25 with a 5090. It's simply too frustrating to create scenes and pose characters with the jerky viewport. To make lemonade out of the situation I've learned to use 4.24 and 6.25 simultaneously and I kind of like it. I do pretty much everything except rendering in 4.24 and then do the rendering in 6.25. While a scene is rendering I use 4.24 to create the next scene. Of course there is a performance hit but with a high end PC it's not too bad and I suspect most people who can afford a 5090 have a pretty good PC. I know this workflow isn't for everyone because we have different needs but for story telling where characters are re-posed in the same scene a number of times it's not bad. It also has the benefit that all the scripts and plug-ins you own work in 4.24 where you do the detail work. This way you don't have to worry about script and plug-in upgrades for 6.25 and potential upgrade charges.

This next part is a naive guess on my part and if it's crazy I apologize for wasting your time. I don't know how things work 'under the hood' but if supporting the new 'Universal' view option is responsible for the performance issue then maybe it's time to back the feature out? Since 6.25 is now a beta it would be a significant setback to return to alpha but viewpart performance has to be restored. Although the universal view is a nice idea there are other ways to increase contrast between objects when the colors are too similar in texture shaded. For example, switch to cartoon shaded or filament temporarily. I miss cartoon shaded in 6.25 but filament is still available.

Thanks for all the info everyone. ;)
I have to admit, Filament and subsequently Filatoon haven´t been on my radar so far.

Filatoon is a toon/cell shading shader for Filament engine. You can find more informations about it in these threads: 

https://www.daz3d.com/forums/discussion/704951/anime-toons-and-filatoon-shader-q-a/p1

https://www.daz3d.com/forums/discussion/704931/filatoon-cell-shaded-rendering-with-filament/p1

Nexy said:

Cool to see the new Alpha update! Got a few issues I'd like to flag up that are still ongoing issues (I've posted about them ages ago, so just want to keep them in the cycle in case they've been forgotten about).
Please don't take this as me being negative or complaining, I understand this is a whole process and am night trying to throw shade at all, this is purely me pointing out the pressure points I run into the most 
1. Keyboard shortcuts are still broken, a couple in particular that I use a lot in my workflow that works strangely:
-I have 'collapse all' bound to a keyboard letter (c), and if I am using the scene panel and press it, nothing happens. The ony way to make it work is to click elsewhere such as the viewport and THEN press it to make the thing collapse.
-Same with the keybinds I have for the scene tools. I have to specifically have to click on the viewport first for them to work, which makes it very frustrating if I'm for example fiddling with the sliders in parameters, then hit the shirtcut for my tool I want to use and then go to use it... but don't realise nothing happened to I end up dragging my character instead which locks up the computer while it 'thinks' and then I have to undo it... ugh. Can be so frustrating!
-None of this is an issue in the 4.24 version as keybinds work anywhere, so if I'm missing something like a box I need to tick somewhere to make keyboard shortcuts work anywhere, I'd love to know! 

It used to be that you could type the first letter of a file name in a content pane and ity would jump to the first entry after the current one that matched it - people liked that feature and were sad when it went away. Now it does work again, but that stops the use of shortcuts for commands when the pane has  focus. it's a swings and ropundabouts thing.

2. There is still a very frustrating issue (this is actually with ALL the DAZ versions) where if I open the program, there is roughly about a 50/50 shot on if it gives me the Premiere tools or not.
I pay for Premiere and it's attached to my account and all that, but for example it happens often where I'll open DAZ, load a scene (you guys know that's not a short process and I work with big scenes), then during my work I go to tuse the Geometry Sculpter tool for example and it's just not there as an option. In order to fix this I have to close DAZ completely and reopen it again and hope this time it 'registers' and then re-load that scene all over again.
Not only that, but if I've opened a scene that's has a prop or clothing or whatever that had the GS tool used on it, those changes are reset. This is a big issue when I render out a whole bunch of panels over night (I'm a comic artist so this is a common practice) and in the morning I see that when I loaded the Alpha version to render out, I hadn't checked to see if GS was 'active' and so all the GS effects are missing and I have to re-render them.
3. Just adding on to the discussion above about the glass shaders, I have this issue constantly too, not just for glass though.
I use 'slime' shaders a lot, and it happens with those too where I can see and pose a 'slime' shaded figure or prop fine in 4.24, but then if I flip to Alpha to review it I can either not see it until the bounding box is there, or there's only like a... 'sheen'?... like a ghostly reflection mark on the outside rim of the object almost like just the specular highlight?
it makes tweaking any poses very difficult to see and do. If anyone has the 'lady goo' gifure for Gen 9, or 'nightmare ooze' kit or any of those, it's very easy to see what I mean with that... basically any fluids are impossible to see when you load in the prop.
And none of the viewport options work other than MAYBE filament?... but it's very marinally better (of course you can see it in iray, but making poses with iray is so slow it's essentially uselss)

4. Lastly the spotlights being 'blacked out' is one of my other frustrations.
If you have more than like... 8 or so spotlights in a scene, the 'preview lights' (control+L) simply doesn't work on any of the spotlights beyond that.
I know that sounds like a lot of spotlights, but I frequently use spotlights to light environments to create pockets of light and other effects, as well as use them as 'three point lighting' on characters, and when you have multiple characters in a scene they add up!
It seems like DAZ picks the first 8 (or however many it is) lights to be viewable in the 'preview lights' toggle, and the rest are completely black. This makes that feature essentially useless for me which is fine when just working on the scene and posing... but then when I want to adjust the spotlights on the characters I usually select them in the viewport to 'look through them' to line up where it is pointing and hitting the character. In this mode if that spotlight isn't one of those first 8 or so, then it's completely pitch black dark, and if there is none of 'first 8' lights around this area, then the figure is ALSO completely black and so I literally can't see anything in the scene and can't line up the lights without going to iray... which means the whole process takes AGES because moving stuff in iray CHUGS. 

This is a limitation of OpenGL, I am not sure if the updated viewport coding in DS 6 will offer a workaround

Some possibly solutions would be:
-Allow us to expand the amount of 'preview' cablable lights in the viewport settings like we can adjust the texture quality
-Somehow allow us to toggle which spotlights are the viewable ones instead of the first 8 or however, because currently the only "solution" would be to delete all the env lights so that the 3-point ones are "first", and then re-set up the env lights which is super annoying... and also still breaks if I then want to add more lights in future comic panels as I'd have to do that all again...
-Just have it behave like the camera does where if you toggle the 'preview lights' it does the usual blackness thing, but if it's NOT toggled you can just universally see everything in a flat light so I can actually see whenre it's pointing

So they are my current pressure points of friction!
As I said before, don't take this as me bitching or throwing shade, this is meant to be me just making sure these issues aren't lost in the noise. 
I totally get that it's an Alpha an you guys are doing a great job bringing consistent updates! I do follow a lot of the conversation that happens in here and I see when there's people who 'blow up' about their frustrations, and I think although sometimes the response of it's an Alpha, it's to be expected' is valid... this is a very different situation than say a game Alpha where testing it out is volountary. This Alpha is forced on anyone with a 5000 series, and people may not have the ability to 'wait it out' for a while if it's their livelihood (such as myself), so the frictions can be a lot more grinding than if it was a video game Alpha or something.

So thank you for your hard work, and I look forward to more updates! For such a small software dev team (from what I hear), you're doing a great job