Lots of stuff now broken
alisa53
Posts: 157
in The Commons
Following the download of new beta AND non-beta versions, I find lots of my content is absent and files are missing. Some items I can now only find on beta, some only on non-beta. I use Li Incandescent to light many of my renders. Now the system tells me files are missing. Initially this was just on beta, but now following latest system download, also on non-beta. Any suggestions? Solutions? Thanks.
Screenshot 2022-02-20 083618.jpg
3196 x 1818 - 529K
Daz 3D is part of 
Connect
DAZ Productions, Inc.
7533 S Center View Ct #4664
West Jordan, UT 84084
Licensing Agreement | Terms of Service | Privacy Policy | EULA
© 2024 Daz Productions Inc. All Rights Reserved.
Comments
In your log file you can see the actual path it searches, so you can compare that to where the asset is.
Are you using more than one content library, and if, are they identical in the normal release and the beta?
I have just one content library, and it has always been identical between normal release and beta. I can't see a path in the log file.
I can't see that in the log file. I am using one content library. Have always had just one content library. They should be identical.
Iray 2021.1.0
Known Issues and Restrictions
So, nVidia removed support for Portal Lighta, nothing you or DAZ can do about it.
I think now would be a darned good time for DAZ to impliment more of Filament's features such as emissive surfaces and improve the cutout opacity
it is opensource after all and not subject to the whims of a video card company
I have a similar issue where scene files that worked perfectly fine in 4.15 and 4.16.. Now with version 4.20 I am getting missing texture errors, even though the texture files exist, and the directory they are in is mapped in Studio..
This is why I have been aprehensive about updating since several revisions ago. They keep breaking more and more stuff.
Would this include creating a new primitive (plane) and using an emission color to make it a light source? I've been doing that for a long time and it's always worked fine but suddently it has stopped working completely and I'm just here looking for reasons this might've happened.
Not sure if it's a light portal as I'm quite noob on most of these things but worth asking before starting a new thread I'd imagne.
Redacted
The quote is about portals, which were a way to guide light through windows etc. so the render wasn't wasting a lot of time lighting the ourtsite of a room, not emissive lights. If you are creating an opaque plane and making it emissive then there is no change, it's only when there is a degree of transparency that there is a difference. Is it just the lights thata re failing? A gneral render failure most likely means you need to update your GPU driver.
In (simple-ish) English, please? (i.e. What is it, and where can I find it?)
(Not upgrading at the moment. I'd just like to know what that means).
And most importantly and that should be the north of the heart of the developers: my CPU* stays 20ºC cooler when I use filament instead Iray
(*My 2012 GPU is a bad joke and is not Nvidia)
I think IRAY was a mistake, because like you said not everyone has a high end video card, let alone Nvidia. Some people straight up prefer AMD cards.
..well if anyone here rendered with Realiy/Lux even Iray CPU rendering is an improvement. I've had render jobs that after 12 to 15 hours to even a day which would still be grainy as well as have fireflies . I only had a 4 core/8 thread 2.8 GHz i7 at the time and yes even on that Iray rendering was much faster. Of course the more cores/threads, the better the performance. should the pro cess dump from VRAM. Granted, it would be nice if like Octane, Iray had out of core rendering, but with Nvida putting the kibosh on light portals (which are very useful for architectural rendering), I'm not going to hold my breath.
DAZ should simply upgrade 3DL to offer an alternative for those rendering on CPU...
As far as I am aware upgrading 3Delight much further would require replacing all the material and shader files too.
...or just vault the old stuff and offer modern pbr materials and lighting solutions for new products along with IRay presets
Just tested that light set on my system with Daz 4.20 without any problems. I would try doing Content DB Mantainace - Re-Import Metadata, as it sounds like your Database file has been corrupted doing the update process.
"..or just vault the old stuff and offer modern pbr materials and lighting solutions for new products along with IRay presets"
Considering how angry customers get a vendor decides to pull product that is obsolete, that is a no go.
Yeah! So keep the stuff and learn customers how to convert 3DL 11 to 3DL 13! Can't see why it would be different than converting old stuff to IRay?
possibly one could have both 3Delight versions though unlike iray, I don't know but if it's possible why not, just an extra render option naming this one legacy 3Delight maybe.
I'm not particularly technically minded with the IRAY/Filament discussion. However with the LI Incandescent Render Lights it seems bizarre as when I load as a Scene it works fine but as a light I get the same error.
This looks like a dumpster fire to me.
I'm getting missing texture alerts with some SASE figures, and when I guide Studio to the actual file location, it's the same as the file location in the error. Weird.
That's because the path to the textures has an extra "/" in it, ie. "//Runtime/..." instead of "/Runtime/..."
Previous versions of DS just ignored the extra character.
The PA is making fixes
And people wonder why I'm still running DS 4.12 and refuse to upgrade.
Thank you.
Hi,
I understand this is an old thread, just seeking feedback though if the problems have been resolved.
There's a possibility, in relation to the LI Incandescent - Portrait Lighting for Iray it might simply be the lower case 't' in the texture path name. ie:
Runtime\textures\Laticis Imagery\LI Incandenscent - Portait Lighting
VS
Runtime\Textures\Laticis Imagery\LI Incandenscent - Portait Lighting
The lower case T never gave me issues except in recent months.
I run 4.10 on one, and 4.16 on the other. there's no rush to upgrade beyond that.
On a PC, running Windows, the case should not make a difference.