Help troubleshooting liveDb

[sikotik13]

I have officially run out of ideas aside from a bug, but since no one else has mentioned it, I'm seeking help in case I'm missing something, before reporting it as such.

First, system and specs (although they are included in my signature, may as well add them here):
Windows 7 Professional 64 bit
Intel i7-5960x @ ~4.2 GHz
ASUS X99-E WS
64 GB G.Skill DDR4 2400 Ram
3x EVGA GTX 780 6GB
1x EVGA GTX 670 FTW+ 4GB (display)
OS on a 120 GB SSD
Primary Daz Studio install (release and beta) on a separate SSD for programs
Backup Daz Studio installs on an SSHD with other programs of less importance
Watercooled

To simulate all I need to do to provoke this error that leads to a crash every time, steps are quite simple:
1: Start up Daz Studio (Using the current plugin release, with 4.8, had the same results with newest plugin using backup install of 4.7)
2: Create a primitive (to have a surface to apply stuff to. I like cubes and planes, personally)
3: In the materials tab of OcDS, select liveDb, enter "spandex" (or as much of it as you desire, it's the only material once you reach "span")
4: Right-click and Copy said (ghastly pink) material to clipboard
5: Scroll all the way back up to the top to your one present surface. On your way, note that the the handy status bar under your viewport showed:

Code: Select all

OcDS: Successfully copied 1 Spandex to clipboard
OcDS: Successfully copied 1 OctaneRender element to the clipboard

in rapid succession.
6: Right-click the default material generated by your primitive, and select paste from clipboard.
7: If, at this moment, you are not left scratching your head trying to figure out why Daz Studio has encountered an error (Which I will post a snippet of below the rest of this post, and point out the only variance I have seen in multiple tries), by all means, let me know anything you can think of that would cause this.

To cover all bases:
I cleared the cache, and in fact reinstalled OctaneRender standalone to generate the folder anew after backing it up. I reinstalled every version of VCRedistributable from 05 to current in x86 and x64 format. Reinstalled Quicktime 7. Reinstalled Daz Studio and the plugin numerous times. Nothing makes this error go away. I also restarted my computer several dozen times during the series of un/re-installs. As far as Windows Update is concerned, my computer is up to date for everything Microsoft recognizes. Copying said material as new material and copying from there to clipboard functions just fine, only copying directly from the liveDb in this version of the plugin causes the force crash for me. Also, the spandex material is just memorable for it's ugliness, nearly every material with a mat present and some without (every single Otoy "official" material in the liveDb, for instance) causes the same crash result, including any saved preset that includes a material file that is not templated. I have a template that always loses the mats on application to a surface, but never causes the crash. I can copy said presets as new materials and to the clipboard from there as well without issue. That said:

Using my backup of the 4.8 beta with Prerelease revision 4 or 5, forget which was the last, but that one, without touching anything in the liveDb folder at all, I can go through those same steps above, and step 7 shows me staring at a cube that presumably would be covered in pink spandex if I opened the OcDS viewport. I decided to try all of this without the viewport to eliminate it as a potential variable.

The only error of any kind reported that I can find is the crash report, sample below:

Exception Reason:

Code: Select all

DAZStudio.exe caused ACCESS_VIOLATION in module "F:\DAZStudio4.8\QtCore4.dll" at 0033:0000000063A03816, QString::QString()+6 byte(s)

In the informational log associated with the crash dump is a mirror of the Daz Studio log showing that Daz Studio has started, followed by the above mentioned material messages being copied to clipboard (which does not appear in the Daz Studio log until I close the error report window). That's it. the only difference I've seen in the above box (which is the only thing that's ever changed in a few dozen tests), is the .dll named for the module occasionally changes to MVCR100.dll (I may have the letters out of order, it's only popped up three or four times, but prompted the reinstall of VC Redistributables, just in case, as well as the above prompting a reinstall of Quicktime, just to be sure).

Any thoughts on what I may be doing wrong here? I kind of always thought that the cache was one of the neatest features of Octane, and it having no point when I must recopy each material as new to download it to the cache each time a scene is loaded is frustrating. Also, my bandwidth is kind of poor in my new location, so the time lost re-downloading materials over and over again adds up quickly. Likewise the way that I only seem to forget and cause said crash when it's been too long since I've saved. Funny how that goes. I truly am seeking help, though. I tend to overlook things, and would rather fix the problem on my end if that's all it is without reporting a non-existent bug if that's the case.

Edit/Update: Upon further investigation, I have now also pored over the OctaneRender debug log, which contains a whole lot of nothing useful/pertinent, since all crashes are basically represented by the new starting of the plugin. I did note there are a few series of errors finding materials in the liveDbTextures folder, even though I can browse right to said images, which I suppose must be tied into this whole having to re-download things repeatedly. Guess I'll just go for a bug report on the off chance t_3 can figure it out when he has time.

[sikotik13]

As much as I hate necro-bumping, I am still having this issue.

I am now on Windows 10 Professional 64 bit, with 4 980 TIs, and more hard drives, but otherwise system is the same, though Windows has be reinstalled a few times.
In Daz Studio 4.9.0.61 beta (since it had less issues for me than the "stable" release. Probably doesn't really matter since, theoretically, this issue has existed for many versions of the plugin across three studio updates for me), with OcDS R2.24.2.5, I still have to copy most things from liveDb as a new material, then copy them to clipboard to use them and not crash Daz Studio. Most anything that has no image maps is fine, but even a few of those randomly cause a crash. Every liveDb texture with an image causes this crash, period, even though I have downloaded the entirety of the liveDb to my cache. This took forever, btw, as I am currently tethering to have internet, so I'm kind of stuck with version 2 of the plugin for now, since I can't stay online all the time.

It no longer attempts to re-download the textures on each scene load/copy as new, so there's headway of a sort, but I have to copy them as a new material to use them each time a new scene is created or the crash will occur. Unsure if this is related to when I use a preset of mine in a scene (it's a simple procedural for teeth, in fact), if I create a new scene, and right click on the same preset, it forces a crash. I can empty and delete everything from a scene, manually purging memory, essentially indefinitely without issue, but loading a new scene then right clicking a material used in the scene that should be deleted now == force crash.

I see no one else discussing this anywhere, so I guess I have to assume it's in fact me and/or my system, but I'm seriously out of ideas on what I am doing wrong here. Anyone with any idea, please help!

[linvanchene]

To simulate all I need to do to provoke this error that leads to a crash every time, steps are quite simple:
1: Start up Daz Studio (Using the current plugin release, with 4.8, had the same results with newest plugin using backup install of 4.7)
2: Create a primitive (to have a surface to apply stuff to. I like cubes and planes, personally)
3: In the materials tab of OcDS, select liveDb, enter "spandex" (or as much of it as you desire, it's the only material once you reach "span")
4: Right-click and Copy said (ghastly pink) material to clipboard
5: Scroll all the way back up to the top to your one present surface. On your way, note that the the handy status bar under your viewport showed:

Code: Select all

OcDS: Successfully copied 1 Spandex to clipboard
OcDS: Successfully copied 1 OctaneRender element to the clipboard

in rapid succession.
6: Right-click the default material generated by your primitive, and select paste from clipboard.
7: If, at this moment, you are not left scratching your head trying to figure out why Daz Studio has encountered an error (Which I will post a snippet of below the rest of this post, and point out the only variance I have seen in multiple tries), by all means, let me know anything you can think of that would cause this.

Error 1 - crash on copy to clipboard:

There are different errors you can produce by following those steps.

Tested with Daz Studio Pro BETA - version 4.9.1.25 & OCDS 3.0.4.10

It also seems to matter if you convert the target surface to a blank surface before starting to "copy to clipboard"

- select cube surface
- create as new material / blank material
- follow steps 1-5
- crash

On two out of three tries DS crashed the very moment I clicked on "Copy to clipboard"

- -

Error 2 - copy to clipboard blocks creating blank materials & auto materials:

Still I am also able to produce another error in which it becomes impossible to "create a new material / blank material" after something was copied to clipboard when there is still a blue unconverted surface

- select cube surface
- do NOT create as new material / blank material so the cube surface is still blue
- follow steps 1-5

Now you may notice that you cannot select an option "paste from clipboard" on the still blue surface.

Trying to use
create as new material /blank material
or
create as new material / auto material

will both not work on the blue surface

It seems the material that is copied into the clipboard is preventing new surfaces to be converted to auto materials or blank materials.

- - -

Workaround:
You can try to drag and drop materials to the target surface. In most cases this will result in the surface to update and work as expected again.

[sikotik13]

Thanks for helping me not feel crazy, linvanchene.

I would dearly love to know what t_3 messed with in the clipboard functions that broke them so badly in the prereleases. I pretty much never had a problem before them, and seem to recall pointing this error or other similar ones out for every prerelease version. Positive I suggested rolling back to the old one that still works in v 1.x. Wasnt as fancy, no. However, I personally prefer basic and stably functionstable to things like this. Ill make a note in one of the main threads and see if our awesome new dev person can either fix or revert it.

Thanks again, lin.

[face_off]

I am able to reproduce this crash. I've look into the code and it is going to be difficult to fix :-/ The crash appears to occur when setting the filename of an Image node, where the file path is coming from corrupted memory.

Paul

[sikotik13]

Thanks for at least acknowledging the issue exists. As you can see from the date of the original post, I could get zero feedback from anyone about it, so I thought it had to be something I was doing wrong somehow. I don't know if you have access to the older code (like from 1.2), but the clipboard functions in that worked just fine, even when the pre-releases were first being done with the new, broken one. I doubt it would be so easy as cut and paste, but might give a start if you decide to gut it, which could help expedite it when you get to it. I figure it's worth a shot, anyway.

Still glad we got a dev that cares and does things finally. So, so glad *weeps quietly*

[morphious2013]

my Live DB is not showing up. Tab is there, but nothing showing up. Ideas?

[sikotik13]

I had to redownload the cache (on the system tab, or which ever one is leftmost, not at my computer at the moment), for the liveDb to display anything. Give that a shot.

[face_off]

The crash is fixed in the latest TEST release of the plugin. Pls see the Release Notes for details.

Paul