Daz/Plugin crash after updating from LiveDB

[larsmidnatt]

Resolution was downloading the latest version of 1.0 from the forum and not using the version in my account page. The version in my account crashed when loading scenes, while the version posted on the forums works fine.

Anyone else have this issue before and know a way to fix it? I recently had my computer die so I'm running Daz and Octane render on a new box. on Windows7 if that matters.

I'm using the old plugin 1.0 and trying to open old 1.0 files and when I do they crash if they have a file from the livedb in them. I tried updating the live db via the plugin update button without a file loaded and it will also result in a crash.

I've tried running Daz as an Admin, uninstalling the pluging and reinstalling (including that file in the roaming folder), I've tried changing the cache path to a different location. And I always get the same result.

Any help would be appreciated.

I've also tried rebooting

Seems like i can grab some of the livedb materials without crashing, I even got one that had a texture in it to work. But many of them will crash Studio and the plugin.

EDIT: I deleted all the textures in the liveDBTextures folder, there were only a handful and now it doesn't seem to crash when i click the LiveDB update button. I still crash when I load old scenes though.

i tried installing DS 4.7 into a different directory and then the plugin into that one and still no dice. trying to load the second material on the livedb list will crash the program

UGH, looks like i'm not having this issue with 2.1 so its related to 1.0. uuuugh. Even if I move to 2.X i'm going to want to keep the 1.0 plugin installed separately so I can open old files safely.

[sikotik13]

Using 1.2 with the DS 4.7 beta and 2.xx with DS 4.6, I noticed that since I activated version 2, version one activates, but no longer connects to liveDb.

Not thinking, I also re-installed version 1.2 to the beta earlier this afternoon, as before, it retained all of my presets just fine (when I "sideways" upgraded, using the 1.2 installer in the preview installer thing).

In OcDS version 1.2:
I tried loading a subset I had just made, and it crashed Daz every time. On a whim, decided to open up the alternate install with OcDS version 2, right-click the db in version 2, and copying the entire liveDb to new materials (forces download of all liveDb mats, which takes a decent amount of time, fair warning). It took about 25 minutes to download all 716 presets in the liveDb, then I made a backup zip of the %HOMEPATH%OctaneRender\Cache\LiveDbTextures folder, which is where all of those presets go when you apply them to anything (i.e. if you use a liveDb mat for anything at all in a preset, it reads that from this folder).

Said preset, and all others previously made now work just fine in version 1, but the livedb no longer functions (like an idiot, in retrospect, I tried to update it with no connection, which deleted the previews/meterials that were there). You can add back the icons manually, but they don't function, so it's sort of pointless. Something changed between the liveDb from version 1 and version 2 (the filename changed from ***livedb.oczdb to ***livedb2.oczdb, copying the second, renaming the copy to overwrite the earlier version restores those icons of uselessness), so version 1 cannot access them directly, even though they are now present enough for presets to recognize them. Not sure why the interface can't use them, really, but it can't just so you know. However, at least everything you made before will be usable.

If you know precisely which textures you used from the liveDb, you can perform the operation above for those specific ones only, which would cut down on bandwidth/time.

[larsmidnatt]

Thanks for the tip but that didn't help anything for me. I actually had both 1.0 and 2.x on my last computer with no issues. its only giving me a problem now. I am no successfully able to use the "update now" button for materials and got the preview images. but if i try to load a file with a material it causes it to crash. Same with loading the material 180c (2), works in 2.x but crashes 1.0 every time.

EDIT: OK I see you added more text, thanks again. I'll reread it and see what i'm missing.

EDIT2: Ok I see where you are going with this, im currently download the entire assortment now. I just want to be able to open my old files for the time being so if this allows for that I can deal with the limitations. Thanks again.

[larsmidnatt]

Dang it, i still get a crash after all of that. So i don't know what the deal is. I copied over the files you mentioned, renamed that db file (which for me v1 was not existent anyway) but it still tries to access the livedb and crashes.

I do apprieciate your time writing that up however. Hopefully t_3 will chime in with a solution so I can start rendering again.

I just uninstalled 1.0, 2.x and cleared out the roaming folder and the stuff anywhere i could find it. had to re activate octane for both standalone and daz studio but i still get the db issue that causes a crash.

[sikotik13]

When is it trying to access liveDb? If you are using your own presets, it should only look for a link to the files in the textures database (which was the thing I downloaded in my previous post). At no point, should OcDS be attempting to access the liveDb in version 1 with that method, as you effectively download every single mat the liveDb has.

The only two ways I can think of it attempting to do so are you either:
A) telling OcDS version 1.x to update (It can't),
Or B), attempting to copy or drag from the liveDb tab in version 1.x(which is non-functional, as it can't access the database anymore).

Neither of these scenarios causes a crash for me, but if it does for you, just load up what you had, and if necessary, modify another preset that is similar. You are not getting any new mats from liveDb (even though you downloaded the whole thing, it's incompatible with OcDS version 1.x interface) into those scenes. If you did the "update now" in the preferences tab thing, like I did, you wiped what was there from the version 1.x database. The materials themselves, once downloaded, will work for any presets you already have in place (or should, if not, that's something else entirely), but I stress, you cannot access the liveDb in version 1.x if you have activated version 2.x. For you, it seems, attempting to do so causes a crash.

Unless t_3 has some magic to get us the version 1 liveDb, whether by similar method or an alternative, the best you can do is preserve what you have, modify those assets, and save often in case you forget and try to access things you can't. Or, if there's a way to make the version 1.x interface with the version 2.x liveDb, that would be cool. As it would probably solve all the problems, but that strikes me as more of a cross-licensing issue than anything.

tl/dr: Unless t_3 can pull magic out of nowhere, those scenes have all the liveDb mats they are going to get at this point. The best you can hope for until said magic, is that you don't have to re-download the stuff again if you manage to delete it somehow. If literally loading a scene crashes you, that is not it accessing liveDb (or it shouldn't be), if you actually downloaded the files, they are there (no need to access the Db), and if you didn't, it's crashing because they aren't there in that LiveDbTextures folder.

[larsmidnatt]

So I found a workaround I think. I dug through the forums and found a version that t_3 had loaded to the forums a while back. http://render.otoy.com/forum/viewtopic.php?f=44&t=33059

even though the packaged plugin found in our accounts is newer i figured this couldn't hurt. It does load my scenes but I do get all the "could not download" etc etc WARNING. But the victory is the file doesn't crash and allows me to continue working.

but hell beggers can't be choosy. (not sure why I have to beg really)

but alas I can do what I need to for now. I'm still wondering if there is a better way that wouldnt require any development? Or are 1.0/1.2 users just not able to connect to the db anymore. ANd frankly even if they can't get on the DB they should not suffer a crash and they should be able to access their files gracefully.

[larsmidnatt]

When is it trying to access liveDb? .

when it opens a file.

But Siko, my point is I can't even OPEN the files. They always crash :/ I'm not even trying to access the livedb. I'd rather it didn't even try. I put all those files into the cache and it still tried to connect.

[sikotik13]

That's odd. It, quite literally, should not be accessing the liveDb at all. Even if you don't have the stuff, it should just force close Daz because the mats are missing (which was what notified me of my issue). That would just mean the mats are missing, or in an incorrect location. Is your log saying it's attempting to access the liveDb when it crashed?

For the record, I'm still using 1.2 myself, so I'm interested ion anything new that goes wrong with 1.x. I'm just trying to help figure out what's going on, that way maybe, if there is a fix, it'll be easier to narrow down what exactly is wrong. I'm not trying to pester, I promise.

[larsmidnatt]

the popup modal crashes on the "accessing missing material from LiveDB" section of the file load.

If i cleared out the livedb folder before loading a file I could see it makes folders for some of the materials than crashes. Even if all the materials are already in the folder it was trying to access them from the livedb for some reason.

There may be a difference between how 1.2 and 1.0 operate and that may be why it worked for you and not me. Thats my guess.

[sikotik13]

I guess so. It still seems odd it would be trying to do that. Guess that was one of the things that got "fixed" early on. Go fig.