OcDS PROBLEMS RESULTING IN CRASHES - read & post here...

[t_3]

I discovered the problem with V6 but I repeated it with Genesis.

ok, thanks...

[SimonJM]

I seem to be in the happy position of having both Look At My Hair and the Octane plugin for Daz Studio. Happy except for the fact that if I have the OcDS active then using LAMH presets causes DS (4.6.0.18, 64-bit) to hang. If I move the OctaneRender directory out of the plugins directory and do the same thing (load Mill Big Cat, create LAMH object, apply fur preset) it all works.

There is another issue that is independent of OcDS that I have with this - gee, aren't I the lucky one! - whereby DS just crashes if I load a figure that has a LAMH preset associated with it.

[larsmidnatt]

You can disable plugins via Daz studio. the Garibaldi Hair solution does not crash when runing with octane so I use that instead these days.

[SimonJM]

Very true, but is a pain to have to do that as you need a restart to make the changes. Also I am not sure why I should even have to - these plugins should co-exist peacefully.

[t_3]

Very true, but is a pain to have to do that as you need a restart to make the changes. Also I am not sure why I should even have to - these plugins should co-exist peacefully.

may i have some crash reports please?
does disabling live geometry do any change to the situation?

in general: every plugin can do harmful things to any other plugin. i.e. it can globally override event processing in a way that another plugin that relies on getting events in the right order will get messed up. it may block signals that daz studio emits, that of course will be also missed by other plugins when they would be needed.

sometimes such hacks seem to be a last resort to overcome certain problems with the daz api - and there is nothing that keeps one from doing them; of course i can't say if this might be the case here, but it's at least one of a thousand possible reasons.

ps: needless to say that since the octane plugin needs to catch up with nearly anything that happens in studio, from nodes, geometries, surfaces, materials, cameras, lights, animation, load, save, script execution, ... it is a perfect crash target if anything goes wrong in any other place...

[SimonJM]

There certainly seems to be something going on betwixt LAMH (Look At My Hair) and OcDS.
There are two, separate 'events' that have issues. One is the loading of a LAMH preset on a figure already loaded into the scene (such as using the Tiger fur preset on the DAZ Millennium Big Cat). This works if OcDS is not active, otherwise LAMH, and by extension Daz Studio, hangs.
The second event is the loading of a figure that comes 'pre-supplied' with a LAMH preset, such as RawArt's Sasquatch or Lycaon figures. These crash Daz Studio regardless of if OcDS is active or not. I am not sure how much use a crash report of this event would be to you as evidence would tend to indicate that OcDS is not an issue here.

The problem details, from the hang are as follows:

Description:
A problem caused this program to stop interacting with Windows.

Problem signature:
Problem Event Name: AppHangB1
Application Name: DAZStudio.exe
Application Version: 4.6.0.18
Application Timestamp: 5191dc25
Hang Signature: 829a
Hang Type: 0
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 2057
Additional Hang Signature 1: 829abc320ce7cc120edabda89227fbe0
Additional Hang Signature 2: 8dc4
Additional Hang Signature 3: 8dc460feaaf645001f580d2de71c8ab8
Additional Hang Signature 4: 829a
Additional Hang Signature 5: 829abc320ce7cc120edabda89227fbe0
Additional Hang Signature 6: 8dc4
Additional Hang Signature 7: 8dc460feaaf645001f580d2de71c8ab8

It has been mentioned, elsewhere, that there is a 'known issue' of OcDS and the RiCurve renderman primitive which LAMH can make use of. Personally I am not convinced of that, but who can say?

[t_3]

ummm; "AppHangB1" is pretty strange. to me this looks like something works up the ui framwork (= Qt), apparently on a level beyond what daz studio/Qt can report as internal crash. googled about this a bit but found nothing descriptive regarding it; it seems to be sometimes connected with viruses/trojans, but most probably this is not the case here. to me it looks like something very tricky is done somewhere, on a very basic level. it indeed indicates (a bit) that lamh is messing with the signal/event flow in studio. i can only hope that my update will resolve it just per accident...

[t_3]

ps: i'm working on a method to switch on/off ocds without the need to disable/enable it in the studio plugin dialog; it will be then not completely inactive, but only maintaining saved ocds data, if a scene is loaded and again saved (as otherwise the data will be lost). this should not interfere with anything else, since it hooks up to a straight and capsuled interface in ds...

[SimonJM]

The flat-out crash (wen loading a figure complete with LAMH preset) has beene explained - not yet supported by the full program, just the LAMH Player. Workwound is to load the base figure then the associated LAMH preset.

The hang is, as you say, more bizarre. I'd certainly like to think it's not linked to a virus or trojan as I do take care in that area!

I am sure something suitable will be worked out in the fullness of time

[t_3]

in the fullness of time

does this include the timespan needed for the human race to excavate and reach distant solar systems because our sun melts down?