need a little help

IvyIvy Posts: 5,154

I think I may need some help with using SDK for daz4.6
when i tried loading a project I have been working on in Microsoft Visual basics 10
I keep getting this script error in daz that tell me to check my log file , which its telling me it can't find my particle library and it keeps giving me this line error codes.
can someone please tell me what this error means and if it a value missing in my c++ programing or is it my version of VB I am using or maybe something else I may be lacking or over looking. SDK is something new to me so its a little confusing

I been working on a particle effects program that creates fire effects for poser. but I would like to try to make it a plugin for daz studio so I can use it in my Daz animations. but I'm not seeming to have any luck getting this to work for some reason. I am sure its in experience on my part.

The error i keep getting in the log file is as follows can some one please tell me what I maybe doing or not doing right to get this error. and at the end of of the log it says it loaded successfully when it does not load at all. it does load as a duf. prop file but it won't animate its just static, but as a dsa file in poser it will animate, my folder name is practical Particle effects in the content folder where i keep all my special effects so the file seems to read correctly as G:/Documents/Daz/Special Effects/Particle effects/ but it keeps saying its can not find the particle library.
I'm a little confused I need a little help here i think.
thank you for reading my comment


Log File
-------------------------------------------------------------------------
OpenGL features for current hardware:
OpenGL provider: NVIDIA Corporation
OpenGL renderer: GeForce GTX 560/PCIe/SSE2
OpenGL version: 4.4.0
Maximum number of lights: 8
Number of auxiliary buffers: 4
Number of texture units: 4
Depth buffer bit resolution: 24
Maximum OpenGL texture size: 16384 x 16384
Current OpenGL Texture Quality Setting: High Quality
RGBA color bitplane resolutions: 8 8 8 0
GLSL version: 4.40 NVIDIA via Cg compiler
Shadow mapping supported
VBO supported
WARNING: dzvalentinaobjectdatabase.cpp(38): DB Register Open error: Cannot establish VC_Connection with remote server.
Make sure the server address and port number are correct.
DB Register Open error: Cannot establish VC_Connection with remote server.
Make sure the server address and port number are correct.
WARNING: dzvalentinaobjectdatabase.cpp(38): DB Register Open error: Cannot establish VC_Connection with remote server.
Make sure the server address and port number are correct.
DB Register Open error: Cannot establish VC_Connection with remote server.
Make sure the server address and port number are correct.
Error connecting to CMS
*** Scene Cleared ***
Loading plug-ins:
aniMate2.dll
dazscriptide.dll
dz3dconnexion.dll
dz3dmouse.dll
dzalignace.dll
dzassetiofilters.dll
dzautofit.dll
dzautoriggerbasic.dll
dzautoshaderbakeractions.dll
dzbrycebridge.dll
dzbvh.dll
dzcolladax.dll
dzcomponents.dll
dzcontentdbeditor.dll
dzcontentlibrarypane.dll
dzcr2exporter.dll
dzcustomizedlg.dll
dzdelightrenderer.dll
dzdformeditor.dll
dzeasyloader.dll
dzexpexporter.dll
dzfbxexporter.dll
dzfbximporter.dll
dzfiguresetup.dll
dzhexagonbridge.dll
dzimageio.dll
dzjointeditor.dll
dzlayerededitor.dll
dzlayerfilter.dll
dzmanualshaderbaker.dll
dzmaptransfer.dll
dzmorphfollower.dll
dzmorphloader.dll
dzmorphloaderpro.dll
dzobjexporter.dll
dzoptitexclothbasic.dll
dzpolygongroupeditortool.dll
dzprimitives.dll
dzpropertyhierarchyeditor.dll
dzpuppeteer.dll
dzpz3importer.dll
dzrenderedit.dll
dzrenderlibrary.dll
dzrslshadercompiler.dll
dzsavefilters.dll
dzscriptedrenderer.dll
dzscriptedsteps.dll
dzshaderbaker.dll
dzshaderbuilder.dll
dzshadereditor.dll
dzshadermixerbase.dll
dzshadermixergui.dll
dzsmartcontentpane.dll
dzspotrendertool.dll
dztextureatlas.dll
dztransferutility.dll
dzu3dexporter.dll
dzweightmapbrush.dll
dzwinvideo.dll
lamhPlugin.64.dll
sdk_sceneinfopane.dll
dzdrawstyles.dll
dzpowerpose.dll
Total class factories: 1289
WARNING: 3DConnexion Plug-in Error: Could not create Device, CoCreateInstance failed
3D mouse support library could not be loaded.
Creating interface
Successfully created OpenGL viewport for Viewport1.
Successfully created OpenGL viewport for Viewport2.
Successfully created OpenGL viewport for Viewport3.
Successfully created OpenGL viewport for Viewport4.
WARNING: QFile::flush: No file engine. Is IODevice open?
WARNING: QLayout: Cannot add null widget to QGridLayout/
Executing startup script...
Started in: C:/Program Files/DAZ 3D/DAZStudio4
DAZ Studio Started
Creating Pixel Buffer
Pixel buffer - Width: 1024 Height: 1024
Compiling OpenGL Shader...
Fragment Shader:
Fragment Shader compiled successfully.
Linking Shader:
Shader Program successfully linked.

WARNING: Script Error: Line 8
WARNING: ReferenceError: Can't find variable: Particlelibrary
WARNING: Stack Trace:
()@:8
Error in script execution!

Script executed successfully.
Executing DAZ Script file: G:/Documents/Daz/Special Effects/Particle effects/fire/ Wild-Fire.dsa
Script executed successfully.
Executing DAZ Script file: G:/Documents/Daz/Special Effects/Particle effects/fire/ low-burn-Fire.dsa/smallFireWithMultipleBounce.dsa
WARNING: Script Error: Line 15
WARNING: ReferenceError: Can't find variable: Particlelibrary
WARNING: Stack Trace:
()@:15
Error in script execution!
Executing DAZ Script file: G:/Documents/Daz/Special Effects/Particle effects/fire/ Wild-Fire.dsa
WARNING: general\dzscript.cpp(599): Empty filename passed to DzScript::loadFromFile()
WARNING: general\dzscript.cpp(599): Empty filename passed to DzScript::loadFromFile()
WARNING: general\dzscript.cpp(599): Empty filename passed to DzScript::loadFromFile()
WARNING: general\dzscript.cpp(599): Empty filename passed to DzScript::loadFromFile()
WARNING: general\dzscript.cpp(599): Empty filename passed to DzScript::loadFromFile()
Script executed successfully.
Executing DAZ Script file: G:/Documents/Daz/Special Effects/Particle effects/fire/ low-burn-Fire.dsa
WARNING: general\dzscript.cpp(599): Empty filename passed to DzScript::loadFromFile()
WARNING: general\dzscript.cpp(599): Empty filename passed to DzScript::loadFromFile()
WARNING: general\dzscript.cpp(599): Empty filename passed to DzScript::loadFromFile()
WARNING: general\dzscript.cpp(599): Empty filename passed to DzScript::loadFromFile()
WARNING: general\dzscript.cpp(599): Empty filename passed to DzScript::loadFromFile()
Script executed successfully.
Executing DAZ Script file: G:/Documents/Daz/Special Effects/Particle effects/fire/ blue-flame.dsa
WARNING: general\dzscript.cpp(599): Empty filename passed to DzScript::loadFromFile()
WARNING: general\dzscript.cpp(599): Empty filename passed to DzScript::loadFromFile()
WARNING: general\dzscript.cpp(599): Empty filename passed to DzScript::loadFromFile()
WARNING: general\dzscript.cpp(599): Empty filename passed to DzScript::loadFromFile()
WARNING: general\dzscript.cpp(599): Empty filename passed to DzScript::loadFromFile()
Script executed successfully.
Error in script execution!
WARNING: Object::disconnect: Unexpected null parameter
*** Scene Cleared ***
DEBUG: End DAZ Studio log...
--------------- DAZ Studio 4.6.3.52 exited ------------------

Post edited by Richard Haseltine on

Comments

  • SMokeyDemonSMokeyDemon Posts: 0
    edited December 1969

    Hey Ivy,

    Looks to me like a script error rather than an error generated by a compiled plugin error.
    I'd probably take a look first at those dsa files and see if they are referring to this Particlelibrary variable its complaining about.
    maybe remove one by one and see if the error goes away to narrow down where (or which file) the error is happening in (looks like it might be in 2 files).

    It could be something that existed in poser but not in daz (assuming there that you've tried to port the code over) , I cant really see any particle classes defined in the daz3d sdk so that's probably the case.

    Ive never really used poser Im still new to daz sdk too so hopefully this helps.

    cheers

    ps...

    G:/Documents/Daz/Special Effects/Particle effects/fire/ low-burn-Fire.dsa/smallFireWithMultipleBounce.dsa
    this one looks a little strange since its in a folder called low-burn-Fire.dsa ?? unless the log is playing funny buggers.

  • Richard HaseltineRichard Haseltine Posts: 52,872
    edited December 1969

    Is your plug-in meant to be exposing certain functions to scripting? It could be that that isn't working if so, and so the script is failing to find the target object.

  • IvyIvy Posts: 5,154
    edited December 1969

    s0t said:
    Hey Ivy,

    Looks to me like a script error rather than an error generated by a compiled plugin error.
    I'd probably take a look first at those dsa files and see if they are referring to this Particlelibrary variable its complaining about.
    maybe remove one by one and see if the error goes away to narrow down where (or which file) the error is happening in (looks like it might be in 2 files).

    It could be something that existed in poser but not in daz (assuming there that you've tried to port the code over) , I cant really see any particle classes defined in the daz3d sdk so that's probably the case.

    Ive never really used poser Im still new to daz sdk too so hopefully this helps.

    cheers

    ps...

    G:/Documents/Daz/Special Effects/Particle effects/fire/ low-burn-Fire.dsa/smallFireWithMultipleBounce.dsa
    this one looks a little strange since its in a folder called low-burn-Fire.dsa ?? unless the log is playing funny buggers.

    Hi s0t
    Thank you for the reply, the file line you showed ( low-burn-Fire.dsa/smallFireWithMultipleBounce.dsa) I think is my texture bounce for the small fire particle effect . but I'll check it line by line like you aid.. if i load it from my prop file it will load but its static and the fire won't run the practical effect so could it be i don' that t have it linked wrong in my data connecting it to prop file? I'll go through it again as you suggest and try it one line at a time and see if i can debug which line it is ..

    this is a little confusing because when i loaded this in pp2014 it run like a charm but it won't render with out taxing my vb server for debugging& tells me poser has to shut down in daz it won;t load at all.. so that is why i was thinking i my vb coded could be error with the line code i was getting.

  • IvyIvy Posts: 5,154
    edited December 1969

    Is your plug-in meant to be exposing certain functions to scripting? It could be that that isn't working if so, and so the script is failing to find the target object.

    I'm not sure Richard, what do you mean "exposing functions to the scripting"? , do you mean is it suppose to run the script in daz and log the results in the daz log file?
    I think that in VB 10 I had it set up when i attached the plugin code to install to daz & have it log my debugging results in daz as well as in VB one thing i did noticed last night is that Daz is not recognizing as a plugin like it does in poser.
    . would that scripting give me my code 8 and line code 15 because i see a lot of empty container tags and don't quiet understand why they are not reading my script to execute my particle library it appears as a plugin. have I missed something somewhere? .. I appreciate any help I've been looking at it today and charged 2 lines of functions . one to execute the plugin in the"practicallibrary" which points to my special effects folder in my prop file and it gave me a lot more error codes, so I don't think its how i have my plugin linked to my library, but i defiantly messing up somewhere on that part of it . The SDK documents didn't really explain how to code that connection to my library or i am missing it in my reading perhaps .. I know I am not to good at closing tags in vb so I'm not sure if i missed one, could that expose my script? If so what kind of code error would that give me if i missed one(tag) some where. could that be it ? the question then would be what code error would it read if I did? would you know where i could find that kind of information? I been looking at Microsoft web site for some help on it but have not found nothing yet on error line codes that relates to this . its a little confusing but i'll keep working at it

    Thank you very much for the reply and the help

  • Richard HaseltineRichard Haseltine Posts: 52,872
    edited December 1969

    A plug-in can make some of its functions available to DAZ Script, so that its functions can be used from scripts (the DForm plug-in does this, for example). Since the error was in a .dsa script file I thought perhaps you'd tried to do that and it hadn't worked, hence the error, but it isn't something you would do without knowing it.

  • IvyIvy Posts: 5,154
    edited June 2014

    A plug-in can make some of its functions available to DAZ Script, so that its functions can be used from scripts (the DForm plug-in does this, for example). Since the error was in a .dsa script file I thought perhaps you'd tried to do that and it hadn't worked, hence the error, but it isn't something you would do without knowing it.

    I think I found it .Richard.
    Looked back it in my file after what you said about the functions being available to DAZ Script, so it rang bell about looking at the script version because I remember it said something about being available in the daz x86 plugin folder and trace my file folder back. the file system in programs x86 version of daz. and I was trying to get it to work with daz4.6 so I downloaded the daz 5 version in the sdk kit that came as part of the download options
    when i loaded the daz 4.5 - 32 byte version of daz .the plugin work and I got a bug with the serial code and but it showed Red as a plugin. but now i got to make this work for the 4.6 64 byte and it still will not load the texture file either But I'll work on that next
    i guess this prove I'm don't know what the heck I'm doing.


    The top picture is 64 byte plugins loaded
    bottom one is 32 bytes plugins

    Sigh!

    Capture3_32_byte.JPG
    950 x 748 - 68K
    Capture2_64_byte_version.JPG
    1244 x 947 - 114K
    Post edited by Ivy on
Sign In or Register to comment.