The AuxViewport was added to show a preview 3Delight render, using a feature for 3Delight that allowed a faster version to render, while keeping the main Viewport to Texture Shaded for responsiveness. You can assing it the Iray Drawstyle too, with the 3Delight IPR off, if you like though I am not sure how much benefit that would be compared to the main Viewport in Iray (or Filament) Drawstyle.

prixat said:

There's an annoying problem with a recent forum update that has stopped attachments for the last few weeks!

Can you show the successful preview to see how the scene should look?

Is it the Iray preview and Iray render you're using?

Why bother with a Filament node?

There's an annoying problem with a recent forum update that has stopped attachments for the last few weeks!

Can you show the successful preview to see how the scene should look?

Is it the Iray preview and Iray render you're using?

Why bother with a Filament node?

I have a question. When using an Iray culling camera, can you use it inside the scene or outside the scene with a part of the scene like a wall removed. I am thinking of buying Interior Light Pro for Filament and Iray to solve my interior lighting problems with Iray. Any help would be appreciated. 

I did some more simple tests, this time I used SpyroruE's gray shaders for G3 (now at deviant art?) cause I realised that I wasn't removing all of the textures and remembered I had that helpful one click solution. But using my partial map removal setup, I tested again exactly like mentioned before,(loaded G3F, loaded the anatomical elements, opened Animate loaded G3 "body shake", set it to loop), but with a fresh instance of DS 4.21. That test resulted in G3F+ anatomical elements dissapearing from Filament in less than 8 mins. except for the eyelash geometry (which of course is connected to the head in G3). As usual, all visable in texture view and when switching back, all was gone. I closed DS, opened a new instance and did the same test with the gray shader and it all dissapeared in less than 8mins ( all visible in texture view etc. but still all gone in Filament). I probably should have pointed out by now that I have 2 monitors, 1 for the DS tabs /content/scene/parameters/etc. powered by onboard intel graphics. The other monitor is a 4K TV that only displays the Filament viewport ( unless switched to another drawstyle ) always kept in fullscreen view (portrait) powered by the 3060ti. ( that should have enough power to run the TV in 4K , right?) Actually, both monitors are in portrait position - could it be that DS doesn't work well in portrait setup? Seems like everything else is okay. Thanks for reading all this. If you have any similar experiences your response will be much appreciated.  / Peace /                                                                                                                                     My PC is : Win10 10th gen i7 2.50 ghz 32 GB ram nvidia 3060 ti, using DS 4.21.

If you are using the Bottom View and are using Iray is Draw ground off in the Environment settings (properties for the Environment Settings node or in the Editor tab of Render Settings pane, though you will not see it until you have rendered or previewed using Iray or Filament, or have explicitly added the node via Create menu)

The Sun/Sky option is available in the Environment Settings node or through the editor tab of Render Settings - though you will need to render, do an Iray or Filament preview, or explicitly create the node from the Create menu. Set the Environment Mode to Sun/Sky (or Dome or Dome and Scene, the last of which will also allow local lights, with no map applied) and then set the location and time. If you mean an HRD image used for lighting, that is set in the Dome modes - there are a few free sources, though they may have usage restrictions, but there are also a great many in the store here and elsewhere for purchase.

Hi Dissendior, I much appreciate your feedback on this issue. My experience is that the "naughty bits" could certainly cause the problem like any other geograft, by Daz PAs or anyone else - I have some free ones from sharecg.com that are identically problematic. Anyway, last night I did a simple test in Filament. I loaded G3F, loaded the anatomical elements, removed all the textures, opened Animate2 (you could use the basic version). Then I loaded the G3 "body shake" aniblock and set it to loop (choosing that aniblock cause it's rather hyperactive). After G3F flailed around for almost exactly 10 minutes, she dissapeared. Swtching to texture shaded made G3F + the geograft visable again. I hadn't tried it before but this time, I then switched to iray view and that looked normal (of course there weren't any textures) then switched back to Filament and again nothing was visable. My test was somewhat flawed in that I didn't do the test with a fresh instance of DS, I'll do a better test soon. At least I finally found a use for "body shake" :) And thanks to everyone giving this issue some thought and response! / peace /  My PC is : Win10 10th gen i7 2.50 ghz 32 GB ram nvidia 3060 ti, using DS 4.21. 

Hi Dissendior, did you determine if there were geografts in your scenes when this problem happens? Maybe you have some hidden geografts applied, for example; pants, that with a geograft remove some of the pelvis and legs of the figure, but not the ankles and feet (created so the item won't have pokethrough). I forgot to mention the dissapointment of having this issue with the Legacy V4 UVs for G8F. Since it's created with geografts, the dissapearing issue is the same as with any other geograft that I have. Converting G8/G8.1 UVs to G9 would seem to have the same problem. Thanks for submitting a ticket! >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Hi WendyLuvsCatz, I just wanted to say that I also had this issue on my old Win 7 first gen i7 PC that had a pitiful 2 gig nvidia card. It was well below specs for using Filament (when DS first implemented it) but magically, most of Filament was functional! Knowing the graphics card wasn't up to the minimum specs, I figured that was why I was having the problem. Then I drastically upgraded my setup, but the issue is the same. And it doesn't even take any longer for the figures to go bye bye :) / peace /      My PC is 10th gen i7 2.50 ghz 32 GB ram nvidia 3060 ti, using DS 4.21.  

I wonder a little bit which view mode you guys use when preparing your scenes / renders... I found Filament most helpful as it is closer to the scene in iray but due to this issue I now work more and more in "Texture shaded".

@3DmentiaNull - you describe exactly what I see: the figure disappears, leaving hair and clothing there. Switching to another view mode like texture shaded shows everything again. Except when I go back to Filament the disappeared figure is still disappeared. But the other items of the scene only start to disappear this way when I hide them via scene navigator and unhide them there again... then they are also not visible anymore. Until now I think I had not the issue that when I leave filament and come back the whole scene is invisbile.

@WendyLuvsCatz - thank you for this tip, but no. I really just do a position change on a figure for example in Filament and suddenly the figure disappears.

@RexRed - this sounds promising. But I remember that I have made several renders with the characters in the scene without doing any changes when it comes to props / objects / textures (just pose and position changes). It does not mean that there is no influence of incompatible textures or so but at least it is for sure not the only influence as I was able to work for a longer time on the scene without this problems. I just try to remember if it may be connected to a special camera angle / position... so that this problem may only have appeared when an item was actually included into the viewport... may this be a point? That this issue appears when an object with incompatible texture come into the viewport?

I'm sorry to hear someone else is having this problem, but misery loves company :) At this point in time, I use the Filament view exclusively, and in my experience, the issue is : if there is a geograft in the scene, figures will definitely disappear at some point.  Any generation, any character (though I don't use G9) that has compatible geografts attached, including clothing, will end up with this issue. I'm typically spinning dials to refine some figure's shape and frequently previewing aniblocks to see how it works in motion, and that motion can be the tipping point. However, I could be working on the textures or anything else, when the figure with the geograft will disappear, but leaving parented items like, eyebrows, hair etc. alone. As noted, switching to another drawstyle makes it all visible again. But then switching back to Filament makes everything disappear completely! It's hard to remember if you need to save the scene in it's present state when you can no longer see the PBR version. And, yes, after retarting DS and reloading the scene everthing will be visable again ( for a while ). I hardly use geografts any more. It also adds to why I wouldn't want to use G9, figuring that one needs geografts to make the base figure look right. 'Hope newer DS versions will work better. / peace //////////////// My PC is 10th gen i7 2.50 ghz 32 GB ram nvidia 3060 ti, using DS 4.21.   

oh do you UPDATE your Filament drawstyle after changing things in the scene or saving by going to smooth shaded view and back before rendering your animation?

that  could be the issue, it needs a refresh

I use filament to position the HDRI sky. It is the only view besides Iray that will show the HDRI sky texture. This is VERY helpful!

In Iray you cannot drag the HDRI sky because it is too heavy on the renderer but filament you can rotate the sky in real time. It is good for getting the sun in the HDRI positioned where you want it in the scene and Filament shows light on your figure and a rough idea of light directional angles.

With some HDRI skies though, filament will not display them.

I think it is because of various incompatible elements that are included in the texture nodes or HDRI file format.

So, I would look at that as your problem. Your scene probably has a texture on an item (maybe hair) that confuses filament. (Just a guess) try removing an item one at a time and save your scene restart Daz reload your scene and see if the problem persists.

strandbased hair vanishes for me in Filament animations but I haven't had anything else vanish yet so cannot help

(and I do lots of them)

V3 and M3 Filament animation 

wearing a G8 hood converted to a prop

I have the same issue with filament sometimes, but it's very random. I did put in a ticket, however, it happens so infrequently, I wasn't able to replicate it. Good to know it's not just me. I use filament view very occasionally to be able to see darker surfaces where in texture shade it is sometimes hard to see collisions between dark floors and dark shoes.

Oh, Filament... Sorry, I don't use it that I deactivated the plugin from the 1st day... Pls see if other Filament users can help.

I now found out that this only happens in filament view mode. When I switch to Iray, cartoon shaded or texture shaded I see the character

As the title says: I am currently working on a set of renders and therefore I adjust the posing for the involved characters for evey render using the same scene. Sometimes it happens that the character that I have just posed with the PowerPose tool simply disappears from the view port. It is not hidden accidentally or so... when I hide and unhide the character in the scene navigator nothing changes. At the moment when I shut down Daz Studio and restart it everything works fine again but this happens very often at the moment. Just a moment ago it happened again and I wanted to hide the back scene by hitting the eye in the scene navigator for the group of the scene props (with holding Ctrl) and then it happened to the props as well: they were invisible and became not visible again after hitting the eye again. Can anybody tell me what could cause this? May it be a performance issue? I am not sure but I think this happens after I had rendered the scene....

Hi. I have been using DS for some years now, mostly for my own entertainment snd suffering from the problems caused by my devoton to Apple Macs. I know features like filament for instance re not open to Mac users, or it wasnt last time I checked, but thats not the thing I need help with. 

Apple have just released the new operating system called Ventura, which i installed and I have found it a horror story. The effect on my Daz studio has been catastrophic. The version I am running is 4.21.0.5 which has to be out of date. When I opened it up after installing Ventura the interface had changed a lot, as an example the tabs group seems to have lost some options, there is no tab  for contents for instance, is this the result of installing Ventura or someother reason.

I would like to install the latest version of Daz but cant seem to find it and I have forgotten how to install it anyway, I dont have DIM or the other content management thing Daz central, could do with some help plese...