Navigation

    • Register
    • Login
    • Search
    1. Home
    2. Yakuza
    Y

    Yakuza

    @Yakuza

    2
    Reputation
    15
    Posts
    76
    Profile views
    0
    Followers
    0
    Following
    Joined Last Online

    • Profile
    • More
      • Following
      • Followers
      • Topics
      • Posts
      • Best
      • Groups
    Yakuza Follow

    Best posts made by Yakuza

    RE: Allocation of PrefsDialogObject

    SOLVED
    It's just static NodeData *Alloc() { return NewObjClear(SoloPrefs); }

    posted in Cinema 4D SDK •
    RE: Plug-in running fine on one OS but not another

    @ferdinand

    Yes. it's solved. Thank you.

    posted in Cinema 4D SDK •

    Latest posts made by Yakuza

    RE: Plug-in running fine on one OS but not another

    @ferdinand

    Yes. it's solved. Thank you.

    posted in Cinema 4D SDK •
    RE: Plug-in running fine on one OS but not another

    @kbar said in Plug-in running fine on one OS but not another:

    I was reading through this to see if you used a Debug build. Glad you finally found it. I assume what you were doing was compiling on one machine in Debug mode and then just copying the plugin to your second machine to try it out. That second machine wouldn't have had Visual Studio installed so it wouldn't have had the debug runtime dlls, so your plugin wouldn't have loaded. Always compile in Release mode if you are going to test your plugin on another machine, or if you are giving the plugin to someone to test out.

    That's exactly what happened. Thanks.

    posted in Cinema 4D SDK •
    RE: Plug-in running fine on one OS but not another

    OK, it's working now. I changed two things but probably what did the trick was the latter: I updated Visual Studio and compiled a Release build. 🙂 The shakey one was Debug config which I totally missed until after the update. FYI I'm using the Community Edition. You can re-download via the above link and test 2023.0.1. and 2023.1.0 again if you are interested. Here it's running just fine in both versions incl. prefs.

    Cheers!

    posted in Cinema 4D SDK •
    RE: Plug-in running fine on one OS but not another

    Yup, very odd. BTW on the failing OS neither the locally installed 2023.0.1. loads the plugin nor the installation that is installed on the other OS and works there does.

    posted in Cinema 4D SDK •
    RE: Plug-in running fine on one OS but not another

    Hi Ferdinand.

    The folder is the default "plugin" folder in the application folder with both OS so no path in the C4D prefs. But even with path it makes no difference. Yes, I'm using pluginflag_hide and access the command via Comand Manager shift+F12. Here the console doesn't even print the copyright remark. On the other OS everything works, console out, prefs dialog in C4D preferences, command in Command Manager.
    I'll get back on this later. Thank you so far.

    posted in Cinema 4D SDK •
    RE: Plug-in running fine on one OS but not another

    You can download the plugin here http://synesthetic.de/plugins/solo2023.zip

    posted in Cinema 4D SDK •
    RE: Plug-in running fine on one OS but not another

    @ferdinand

    Hi Ferdinand.

    Thanks for the quick reply. I'm currently a bit busy and can only answer some questions without investigating further.

    First of all I'm using legacy code and it's a commanddata plugin. I downloaded the project tool last week. I compiled it for 2023.0.1 and copied the same folder over to the other Windows running a fresh install of 2023.0.1 with no other plugins present in the plugins folder.

    Regarding registration I check this in Main like this

    #include "c4d.h"
    
    Bool RegisterSOLO(void);
    Bool RegisterSoloPrefs(void);
    
    Bool PluginStart(void)
    {
    	if (!RegisterSOLO()) {
    		ApplicationOutput(maxon::String("Solo could not be registered."));
    		return false;
    	}
    	if(!RegisterSoloPrefs()) {
    		ApplicationOutput(maxon::String("SoloPrefs could not be registered."));
    		return false;
    	}
    	ApplicationOutput(maxon::String("solo for Cinema 4D 2023.0.1 (C) 2007-2022 by synesthetic.de"));
    	return true;
    }
    
    void PluginEnd(void){ }
    
    Bool PluginMessage(Int32 id, void *data)
    {
    	switch (id)
    	{
    		case C4DPL_INIT_SYS:
    		// Don't start plugin without resources
    		if (!g_resource.Init()) return false;
    		return true;
    		case C4DMSG_PRIORITY:
    			return true;
    	}
    	return false;
    }
    

    There is no output in the console at all. I'm going to double check API and C4D versions later this evening and do a rebuild.

    Cheers!

    posted in Cinema 4D SDK •
    Plug-in running fine on one OS but not another

    I rebuilt my plugin for 2023 and it is working on the Win10 istallation I built it on but not on my 2nd installation of Win10. Any Ideas? It's not running from the sdk folder but rom a separate folder in the plugin directory. With the same folder copied to the other OS it doesn't even register. I checked the redistributables and the x64 ones seem to be there. Unfortunately this was the only thing I can think of as a cause.
    Left is the non-working OS.
    redistCompare.jpg

    Thanks a lot!

    posted in Cinema 4D SDK •
    RE: Project Tool Stops At Non-Existent Path

    @spedler

    Ahh. headdesk
    I'm doing this too rarely. Thanks a lot.

    posted in Cinema 4D SDK •
    Project Tool Stops At Non-Existent Path

    Hi.

    I'm trying to run the Project Tool on a fresh install of C4D for coding purposes on D.
    This is what happens:

    project tool.jpg

    I have no idea why. It throws the same warning when I try this on C:\Program Files where there actually is a "Maxon" folder. But it's just Maxon App stuff I think.

    Thanks in advance.

    posted in Cinema 4D SDK •