LOG Cleanup - Live (Discoveries, Solutions, Qs & Discussion for LOG Events)

Home Page Forums General Chat LOG Cleanup - Live (Discoveries, Solutions, Qs & Discussion for LOG Events)

Viewing 12 posts - 1 through 12 (of 12 total)
  • Author
    Posts
  • #1919958
    Spats
    Participant
    Rank: Rank 4

    Using the log, live. Discovering and solving "warning"s and "error"s; questions and discussion about what's left/unresolved.

    [Lengthy - Skip to Log events below as nec]
    [If formatting changes are needed for clarity, open to suggestions]

    Background:
    Recently started using a live log viewer (a Tail emulator for Windows - "Tail for Win32" [https://tailforwin32.sourceforge.net/], kind of old but fast, light, and configurable), and employed it to more easily view and highlight warnings, errors and issues (collectively "events") in the DAZ log file, live, as they happen. (Used second-screen alongside DS now whenever running.)
    The revelations have been abundant.
    Have discovered everything from program loading, closing, and saving events, to read problems and bad file/morph/texture references of scene and scene objects and figures, to memory allocation and routing patterns, to many things in between - some of which have led to additional discoveries of why various scenes and circumstances lead to CPU fallback, for example. (And on the latter, possibly even a way/technique/trick to not only avoid fallback, but to make DAZ seemingly force-release VRAM from card(s) to start using GPU again without DAZ restart when it does.)(Possibly more later.)
    All of this can, of course, be done and found by manually opening the log file, and "searching" for problems and errors; or "tracing back" by scrolling through gobs of lines - hopefully knowing what you might be looking for. But with a viewer like Tail the events can be seen in real-time, and highlighted (literally, with colors and line highlighting of keyword-flagged search terms) as they happen; making for a powerful finding and solving tool.

    Anyway, that's a cursory of the technique. Through discovery, and subsequent searching, it's led to resolution of most of the error, and some of the warning issues in question; resulting in faster load, save, and render times, and a bettering and cleaning of scene files, and improved usage and understanding of the program in general. (The learning curve of what DAZ Iray expects and needs to function optimally, for example, has increased in the process as well, leading to a different approach to metrics and bench-marking among other things. Maybe a separate but also relevant discussion associated to those log findings later.)(Comforting, as well, have been such discoveries as, "Oh, so THAT/THOSE file(s)/textures/LIEs take that much longer to load on open. Ok." And, "Hey, this scene render is NOT falling back to CPU because it's too big? It's falling back because of thus and such error(s)? Associated with thus and such warning(s)? And fixing those warnings/errors gets it to render with GPU? Every time? And quickly? Ok.") And so, in the face of some successes, it's also subsequently led to a desire to "fix them all", of course. While that might not be realistic for all events (ex. "warning"s vs "error"s), it's still something that tends to nag when seeing any/all in the log. "WARNING"s, of course, are NOT "ERROR"s, admittedly; but they do often point to something that may associate directly with error events, or hidden non-functioning portions of DS - especially references. Those warning-error associations are either A) resolvable, or B) not. The "other" forums would have you believe that most all "warning"s are innocuous and insignificant; holdovers from past versions, or pointing references to software or hardware differences not associated with the machine in question. "Pay them no mind." I would beg to differ. There is credence to looking into warnings, instance by instance, to be sure; and in personal experience most every warning has pointed to a resolved issue and often an increase in performance.
    And so, in hunting down and resolving log "warning"s and "error"s on a per-operation and per-scene basis, and failing the finding of adequate info or results elsewhere, this is where the stumped-and-reaching-out happens.

    All said, here are some of the (many - in my case, and I'm sure most others') remaining log warnings/errors/events which continue to annoy, from both the program and from various scene files. (Mainly "warning"s are remaining here, as "error"s have mostly been successfully resolved so far at a personal level.) Wanted to post here, since, like say, "other forums" don't always address these items directly - whether incompletely or at all - often with dismissive "it's not DAZ it's you" short-speak or even guesses when it comes to log events, especially "simple warnings". A shame, since it really does seem that the program is trying to say what's wrong (when it's been programmed to do so, and when including output for a given log entry), if not offering a completely clear or unambiguous solution to fit.
    If anyone knows the answers to these, feel free to chime in. Links included for some personal searching, but by no means comprehensive.
    Not the most glamorous of topics, but solving the unseen, background problems in scenes and DAZ execution seems to often be half the battle. I know there might be other examples here of such search and destroy missions, but if anyone else wants to post log events (warnings, errors, other) here, with possible community-based experience/anecdotes, maybe it continues what forums can be good for: sharing improvements and solutions - or clues to their discovery.
    Thanks for any continued help/participation.

    Format:
    - Log Event (other descriptors/instances):

    (relevant event line(s) copy/pasted, NOTE: Scrub lines of any local machine reference - ex. "/Users/Username/AppData" should be redacted to "/Users/[REDACTED]/AppData")(screenshot if needing to relate errors contextually, but usually pasting one or multiple lines in context should be enough - same redaction rules in screenshots for privacy/safety if it matters to you)
    

    - Event Type: Program Error/Event or Scene-File Error/Event
    - When: (when Error/Event happens)(user action/activity/conditions)(what it affects/seems to affect)
    - Research: (research/searching/links)(possible answers, things tried, results/non-results)
    - Status: RESOLVED/UNRESOLVED

    EXAMPLE SUCCESSES:

    - Log Event (single-line, but MULTIPLE items/assets/events depending on scene):

    WARNING: \src\pluginsource\DzIrayRender\dzneuraymgr.cpp(359): Iray [WARNING] - TRIT:GEOMETRY ::   1.0   TRIT   geo  warn : Object DS_shape_267f_1: the parametric approximation level is set to 4. The original value of 7 would produce too much geometry in a single mesh.
    

    - Event Type: Scene-File Warning/Error
    - When: Happens on running render on specific scene file/asset with specific texture, wherein default Displacement SubDiv is loaded from library at 7. DS seems to take the Displacement Subdivision level down to what it needs/can handle (4) on its own prior to render (see warning note), but performance may be affected. Load times and initialization definitely are.
    - Research: Links- [https://www.daz3d.com/forums/discussion/507761/increasing-fatal-errors-when-previewing-iray]; Things tried: Took Displacement subdiv down to 3 or less on any textures in scene that were higher. Results: All such errors gone; scene rendering times substantially improved.
    - Status: RESOLVED

    - Log Event:

    WARNING: 3DConnexion Plug-in Error: Could not create Device, CoCreateInstance failed
    

    - Event Type: Program Warning/Error
    - When: On program load. Every time. Not sure if it affects anything. Consistent program loading warning/error.
    - Research: Links- [https://hpclscruffy.daz3d.com/forums/discussion/452306/errors-in-log-file-on-startup-of-daz-studio-v-4-15-0-8]; [https://f95zone.to/threads/help-me-sort-out-daz-load-up-warnings.43066/]; Things tried: Disabled 3DConnexion plugin as suggested.
    - Status: RESOLVED

    #1919968
    Spats
    Participant
    Rank: Rank 4

    OPEN/UNRESOLVED:

    - Log Event (2-Separate, Successive Lines/Events, same code for each):

    WARNING: \src\pluginsource\DzIrayRender\dzneuraymgr.cpp(480): Could not add path: "C:/Users/[REDACTED]/AppData/Roaming/DAZ 3D/Studio4/shaders/iray". Due to unknown error -2
    WARNING: \src\pluginsource\DzIrayRender\dzneuraymgr.cpp(480): Could not add path: "C:/Users/[REDACTED]/AppData/Roaming/DAZ 3D/Studio4/temp/shaders/iray". Due to unknown error -2

    - Event Type: Program Warning/Error
    - When: On program load. Every time. Not sure if it affects anything. Consistent loading warnings/errors.
    - Research: Links- [https://www.daz3d.com/forums/discussion/479791/daz-studio-default-install-dzneuraymgr-cpp-warning-could-not-add-path] Dismissive; [https://www.daz3d.com/forums/discussion/404791/startup-warnings]; [https://f95zone.to/threads/help-me-sort-out-daz-load-up-warnings.43066/]
    - Status: UNRESOLVED

    - Log Event (1 to 3-lines following "Scene Cleared", depending on scene-file):

    *** Scene Cleared ***
    JSON interpreter warning: Unexpected string member: blend_mode
    JSON interpreter warning: Unexpected member object: pSadation
    WARNING: QColor::setRgb: RGB parameters out of range
    

    - Event Type: Scene-File Warnings, or could be Program Warnings
    - When: On scene load, depending on scene. pSadation warning every time regardless of scene-file. Separate warning/events, not nec associated. Consistent scene-loading warnings.
    - Research: Links- [https://www.daz3d.com/forums/discussion/336566/long-load-times-fixing-warnings]; https://zonegfx.com/forums/topic/log-txt-cleanup-wow-so-much-faster/page/2/ ; [https://www.daz3d.com/forums/discussion/472576/warning-qcolor-setrgb-rgb-parameters-out-of-range-is-this-slowing-the-deleting-of-a-model]
    - Status: UNRESOLVED

    - Log Event (3-lines/codes, but for MULTIPLE items/assets):

    WARNING: \src\sdksource\fileinput\dzassetdaz.cpp(5836): Could not find parent for modifier: CTRL-RSC-RhiannonOnyX.
    WARNING: \src\sdksource\fileinput\dzassetdaz.cpp(1660): Failed to prepare modifier: CTRL-RSC-RhiannonOnyX!
    

    ...later followed by...

    WARNING: \src\sdksource\fileinput\dzassetdaz.cpp(1671): Failed to create modifier: CTRL-RSC-RhiannonOnyX!
    

    - Event Type: Scene-File Warnings, or could be Program Warnings
    - When: On scene load any time Genesis 8 Female is loaded. Every time regardless of scene-file. Happens for MULTIPLE files/assets. Warning/events associated. Consistent scene-loading warnings.
    - Research: Links- [https://www.daz3d.com/forums/discussion/381691/error-could-not-find-parent-for-modifier-after-using-g3f-to-g8f-converter] (May try techniques from this next); [https://www.daz3d.com/forums/discussion/182766/could-not-find-modifier-definition#latest] (May try techniques from this next)
    - Status: UNRESOLVED

    - Log Event (single-line and code, but for MULTIPLE items/assets):

    WARNING: \src\sdksource\fileinput\dzassetdaz.cpp(6843): Could not find target property for formula: Genesis8_1Female:/data/Daz%203D/Genesis%208/Female%208_1/Morphs/Daz%203D/FACS/facs_ctrl_Wink.dsf#facs_ctrl_Wink?value in file : /data/Daz%203D/Genesis%208/Female%208_1/Morphs/DAZ%203D/Victoria%208_1/facs_Victoria8_1_ctrl_Wink.dsf
    

    - Event Type: Scene-File Warning, or could be Program Warning
    - When: On scene load any time Genesis 8 Female is loaded. Every time regardless of scene-file. Happens for MULTIPLE files/assets. Not sure what it affects. Consistent scene-loading warnings.
    - Research: Links- [https://www.daz3d.com/forums/discussion/10043/could-not-find-target-property-for-formula-genesis] Dismissive;
    Edit/Update: Tracked down all missing files/references, finding what program was expecting and not. Installed/reinstalled multiple items/packages and all (ALL) 6843 errors are gone from Log.
    - Status: UNRESOLVED Moving to RESOLVED
    (One/multiple down!)

    - Log Event (single-line and code, but for MULTIPLE items/assets):

    WARNING: \src\sdksource\fileinput\dzassetdaz.cpp(6777): Could not find output property for formula: Genesis8Female:/data/DAZ%203D/Genesis%208/Female/Morphs/D.Master/Auto%20Face%20Enhancer%20Female/G8Female%20Real%20Expressions%20HD/AFE%20%21Master%20Controller.dsf#AFE%20%21Master%20Controller?value in file : /data/DAZ%203D/Genesis%208/Female/Morphs/Carboncrow/Hagar/FBMHagar.dsf#FBMHagar
    

    - Event Type: Scene-File Warning, or could be Program Warning
    - When: On scene load any time Genesis 8 Female is loaded. Every time regardless of scene-file. Happens for MULTIPLE files/assets. Not sure what it affects. Consistent scene-loading warnings.
    - Research: Links- [https://www.daz3d.com/forums/discussion/480006/warning-could-not-find-output-property-for-formula-how-to-solve] Dismissive; Update: Similar to (6843) errors, 6777 often (mostly) seem to refer to missing/ghost-pointers and assets. Installing/updating said gets rid of most. (G8 relatively easy to solve for, for example.) 6777 errors also, however, make up the bulk of eCTRL errors on G8.1 loading when referencing "missing/blocked" G8 morph references (see details below)
    - Status: UNRESOLVED Update: PARTIALLY RESOLVED

    - Log Event (2-lines/codes, seemingly for a single asset):

    WARNING: \src\sdksource\fileinput\dzassetdaz.cpp(6995): Circular ERC!: DDGamerGirlPose01 with erc ERC [DeltaAdd] > HID Eve 8.1 Female:DDGamerGirlPose01
    WARNING: \src\sdksource\fileinput\dzassetdaz.cpp(7008): Unsupported formula: /data/DAZ%203D/Genesis%208/Female/Morphs/DeviousDolls/Poses/DDGamerGirlPose01.dsf#DDGamerGirlPose01
    

    - Event Type: Scene-File Warnings, or could be Program Warnings
    - When: On scene load when HID Eve 8.1 asset is loaded. Every time regardless of scene-file. Consistent scene-loading warnings.
    - Research: No search results other than other ppls log files with same event. No exact matches associated with solutions or troubleshooting.
    Update: Solution provided via @windreaver0118 below. Updated files at link. (THANK you again.)
    - Status: UNRESOLVED Moving to RESOLVED

    - Log Event:

    WARNING: \src\pluginsource\DzIrayRender\dzneuraymgr.cpp(359): Iray [WARNING] - MATCNV:RENDER ::   1.0   MATCNV rend warn : At 'DS_Bendine Hair Genesis 8 Female (2)__Side2_1fb3_1514.volume.absorption_coefficient': unsupported function call: 'operator/(color,float)'
    

    - Event Type: Scene-File(s) Warning
    - When: Happens when attempting to render specific scene-file(s). Multiple files associated with specific asset. Specific scene-rendering warning.
    - Research: Seems to be associated with a specific asset/file(s): OOT's Bendine Hair; several (8) files associated with each hair instance in scene (ex. if one asset instance, 8 line errors associated with the constituent files/parts of the asset, if two asset instances, 16 errors; no specific online search results found to date.
    Update: Solution provided via @windreaver0118 below. Updated files at lower link. (THANK you again.) Upon render or Iray viewport call, warning/error messages no longer present in Log.
    - Status: UNRESOLVED Moving to RESOLVED

    #1919971
    Frank21
    Participant
    Rank: Rank 5

    Sorry you lost me after the second paragraph. I did learn something today.... there's no need to re-render an image when the artifacts you're trying to fix are from sneezing on the monitor.

    #1919976
    Richard Y.
    Participant
    Rank: Rank Overload

    It used to be a headache to me... I ever spent a lot of time on resolving errors/warnings in the log file, then got 0 error and warning in it. Fast scene load, no annoying dialogue popping up, etc. perfect? Nope~ After installing some products, the headache is back. I had to check the log and tried to fix the problems from time to time...
    It was too time-consuming... on the other hand some issues can be fixed via the clues in log, some cannot... Especially for those errors coming from a certain product, such as when loading base figure, there's a horrible distortion on head or body, the log shows nothing about it...

    So I'm not entangled in such a thing nowadays. To me, duplicate formulas and rendering failure are the biggest troubles for most of the time, I will try to fix them myself or seek for resolution on DAZ forum. For the rest, I'd rather just let go ~

    #1919978
    Spats
    Participant
    Rank: Rank 4

    Myeah, this endeavor will not be for the squeamish or bored.
    Heady even as I look at it now. But who knows, maybe it gets contributed to and helps resolve issues.

    I know the idea of a "healthy" or pristine LOG FILE is a quest more than a destination. But if it helps (me, others), then maybe it's all worth something.


    @windreaver0118
    "Fast scene load, no annoying dialogue popping up, etc. perfect? Nope~ After installing some products, the headache is back. I had to check the log and tried to fix the problems from time to time…"
    Yeah, it's not infrequent that once one product is installed, depending on how it was created maybe it messes with (a lot of) default morphs or assets. Frustrating. Lame. Unacceptable.
    Typical.
    Finding and correcting is at least a goal, for me, regardless. The up side is re-realized performance and function. The worst downside is null/nothing.

    #1920006
    Richard Y.
    Participant
    Rank: Rank Overload

    @spats

    Yeah, fully understood! NP~ 😀
    I went thru some of the messages, as per my exp., here're some clues and solutions:

    - Could no add path for iray shader...
    I have no such an error. Besides, this directory on my side is empty and there's no relevant message for loading this path in my log, weird...

    - Failed to create modifiers for Rhiannon OnyX...
    I believe it's for this figure converted via RiverSoftArt Character Converter G3-G8...
    I remembered I had ever seen the similar messages from my converted figures but after updating the product, they were gone for newly converted ones~ Pls give it a try anyway or I may recheck some cases if needed.

    - Could not find output property for FBMHagar.dsf...
    This character's full body morph uses Auto Face Enhancer. Did you have this product installed? 'Output property could not be found within dsf file' normally results from that you don't have related products installed.

    - Could not find target property for facs_Victoria8_1_ctrl_Wink.dsf
    You need to install latest update of product: 42077 Genesis 8 Female Expressions (Jan, 2022). I can PM you if you need it.

    - Circular ERC!: DDGamerGirlPose01 with erc ERC [DeltaAdd] > HID Eve 8.1...
    Irrelevant to HID Eve 8.1. You've installed product 55991. There're wrong ID definitions in DDGamerGirlPose01.dsf and related JCM dsf files. I didn't see the author gave it an update... I just installed the product and fixed them. You may download the files as below. Copy data folder to the root path of your DAZLib, then warnings will be gone~
    https://mega.nz/file/HPxmWIAa#u-PUQrm3oVmqH3KwD4FWVH8imyZQMZWpwug1M0YxsKU
    PS: It's really unwise that this author make poses by using morphs... 😀

    - for OOT’s Bendine Hair's warning/error...
    Due to iray's update, lots of OOT hairs have problems or could not be previewed and rendered in beta ver. I just updated the fixed hairblending dsf files to both of my libraries, then all problems have gone, at least for the time being...
    I checked this Bendine Hair, OOT also gave it a fix but I didn't buy it. So you may update the hairblending files to see if it's ok~ I attached the files from other OOT hair I bought, just the same copy.
    https://mega.nz/file/feghxbJQ#C4GoIHjMvS4N7ErzX2UW2oNPPBHQGsu9f-YzqVsDsus

    Finally, for getting problems solved, roughly 50%+ come from DAZ forum, google search, user group/community, youtube, etc, 30% count on ourselves, the rest+-... pending or insoluble... 😀

    #1920007
    Abad
    Participant
    Rank: Rank 5

    @spats , maybe this can help, adding some code from the github repo.
    (I no have time now...)

    Console


    Anyway... Wouldn't it be better to activate the Linux subsystem in Win 10...? I activated it a while ago, with ubuntu, but it gave me some errors. On the other laptop I have Kali, and out of trouble.

    #1920041
    Spats
    Participant
    Rank: Rank 4

    Update: Resolved all (seemingly ALL, really) code 6843 errors. All were pointers to missing files or assets/packages. And there were a loooot.
    Some simple progress. Other warning/error codes, not so much.


    @abad
    Yeah, I considered firing up the console. But for what I was interested in TailForWin32 has been well enough. It's simple, no install required (runs portable as needed), and like say is configurable for more options. (Currently trying to figure ways to expand the plugins capabilities, to do things like trigger other programs or instances based on keyword results. Maybe a "render finished" alarm, too, hah.)

    (Still reading through your findings, @windreaver0118 , THANKs for input.)

    Update:
    – Could not find output property for FBMHagar.dsf…
    This character’s full body morph uses Auto Face Enhancer. Did you have this product installed? ‘Output property could not be found within dsf file’ normally results from that you don’t have related products installed.

    Auto Face Enhancer not installed. Just getting to the flags regarding this and a couple other characters. Will either install and update with results, or find reference and edit and update with results.

    – Could not find target property for facs_Victoria8_1_ctrl_Wink.dsf
    You need to install latest update of product: 42077 Genesis 8 Female Expressions (Jan, 2022). I can PM you if you need it.

    Installed this package as part of the code 6843 errors fixes. Exactly right, this and a few other packages/assets were all it took, at least for the code 6843s.

    Will install and update for "Circular ERC!: DDGamerGirlPose01" and "OOT’s Bendine Hair’s warning/error". (Had feeling it was something like this, vendor-mistake or similar.)(No way to control or compensate such when files or references or updates are not included.)
    THANK you, again @windreaver0118 , for the quick solves on these! Hopefully it helps others, too.

    Update: Can report that both these fixes worked as well. "Circular ERC!: DDGamerGirlPose01" no longer shows in Log after file updates; "OOT Bendine Hair" no longer gives errors in Log on render/viewport after file updates. RESOLVED status updated. (Leaving Log events, crossed out, for others to find if needed.)
    Still resolving Genesis 8.1 Female issues (separate from G8F). Finding more 6843 codes, stomping out one by one or ten by ten depending on broken references and missing assets.
    What's left is the 5836/1660/1671 events, and the mass amount of 6777 code errors. The latter seem similar to 6843 (missing reference) codes, but not as easily resolvable, as the assets are present and should be reading/finding correctly. (Correction: Actually many are not. Approaching similarly to 6843 errors when missing and finding/updating assets.)

    #1920122
    Spats
    Participant
    Rank: Rank 4

    Coming to realize that differences, and neglect of referencing, between G8 and G8.1 is ridiculous:
    [https://www.daz3d.com/forums/discussion/528741/getting-a-lot-of-errors-messages-when-loading-genesis-8-1-female]
    Between generations, it seems that the completely different sets of expression morphs were not only slapped on top, but possibly references back to G8 were never cured even though they're apparently blocked from being used?
    In the log these references are rampant when loading any G8.1 (ALL "eCTRL" warnings), regardless of cleaning up for G8; and now (at least in such threads as linked) it's suggested to just live with it as anything else could break it.
    Awesome.
    Maybe a workaround via altering DSFs? Other? (Seems tedious at best.)(What a mess.)(So much for "clearing the log".)

    #1920187
    gts6
    Participant
    Rank: Rank 4

    Like others mentioned, even after cleaning up, it doesnt last long once new things are added.

    The solution might be a "pre-install" software (that would need to be created) that scans all items about to be installed and scrub them of all errors before installing to DAZ

    #1920199
    Richard Y.
    Participant
    Rank: Rank Overload

    @spats You're welcome!

    I just got to test 5836/1660/1671 related warnings. You may try these steps:

    0. Firstly go to the data folder of your working DAZ library (My Daz Library, sth. like that), search RhiannonOnyX, the result should be like this:

    1. Delete them all! Clear the log and load a G8F base figure to see if the warnings are still there. They should be gone.
    But just in case if you cannot locate these files in your working library, try to search them in the data folder of your product library, and do the same.

    I just used '62491 Character Converter from Genesis 3 Female to Genesis 8 Female' to convert Rhiannon's OnyX G3F to G8F, and found no such warnings finally. If these warning are gone by using the above-mentioned steps, or you cannot locate those files nowhere, you may try the conversion again:

    0. Check this product in DIM - Installed tab, to see if Package Date is 2020/6/20. If not, download the latest package from the blog and update it.

    1. Use the script 'Convert Scene Character from G3F to G8F' for conversion since this Onyx G3F has no Character Preset, you have to convert it on-the-fly:

    a. Inject all the shapes of Onyx to G3F base figure, and load a G8F base;

    b. Excute the script and convert;

    c. Save the converted one as a subset or Character Preset. Reload it or load a G8F to see if there's any warning in log.

    Besides, for 6777 (Hagar's issue)~ Have you installed D.Master's Auto Face Enhancer yet? Can it be resovled? I've ever experienced such warnings and fixed them in this way, but uninstalled all of them finally... 😀

    #1920308
    Spats
    Participant
    Rank: Rank 4

    @ethiopia "It’s disappointing that Studio and it’s content cause so many problems. I get the feeling the Daz doesn’t/won’t clamp down on CC’s because it wants lots of stuff to sell vice less stuff but better stuff. It then blames the resultant problems on us, the users."
    I wish it was easier to imagine or even consider something else. But with DAZ history in play, utterly impossible to consider otherwise. In the G8 and other Log cleanup alone, there were two options: A) Install any/all packages being ghost referenced by PA/Vendor products producing error references in the Log (ex. a character based on - or linked-assets with - Penny 8 obviously throws morph or other errors if Penny 8 is not installed; ex. "Expression Morph Package X" expected with "Character Z" ...go buy it to get rid of this log error)(these are the bulk of the 6843 and 6777 code errors, for example)(I found that bluejaunte characters self-library-reference incessantly, btw, prompting errors for two or three other character morphs if you don't own them - so, just as much on PAs as DAZ in this regard), or B) Sleuth and edit DSFs for days to trick DAZ away from the unnecessary/unwanted Log errors. ("B", for the record, is possible but ridiculously tedious. And if you don't backup your original DSFs or packages, potentially permanent.)
    The majority of these "error"s (warnings, really) are mostly harmless, admittedly. Their cost mainly reflected in longer load or save times, however slight, rarely affecting core operating, editing, or rendering. I get that, and it's moot. That's fine. But the fact and the PRINCIPLE that none of this has to be this way is the continued saga of frustration that is DAZ Studio, that's all. As if the goal of an error-free log was such a ridiculous notion.
    Well, with DAZ, apparently it is. "Scuttle the ship" they seem to say, regarding log errors (among many other aspects of corner cutting and neglect). I suppose it shouldn't be surprising at this point.
    #tryingtobegrateful


    @windreaver0118
    I recall doing a few G3 to G8 conversions on chars some time ago, but never anything related to Rhiannon or associated assets. I've been looking for links to such problems, but have found none. I do have a shortlist of items yet to drill down into and hope to find some answers related to your suggestions. Thank you, again, for taking the time. I'll try the methods suggested and see if there are results.

Viewing 12 posts - 1 through 12 (of 12 total)
  • You must be logged in to reply to this topic.

 

Post You Might Like