Maxon Developers Maxon Developers
    • Documentation
      • Cinema 4D Python API
      • Cinema 4D C++ API
      • Cineware API
      • ZBrush Python API
      • ZBrush GoZ API
      • Code Examples on Github
    • Forum
    • Downloads
    • Support
      • Support Procedures
      • Registered Developer Program
      • Plugin IDs
      • Contact Us
    • Categories
      • Overview
      • News & Information
      • Cinema 4D SDK Support
      • Cineware SDK Support
      • ZBrush 4D SDK Support
      • Bugs
      • General Talk
    • Unread
    • Recent
    • Tags
    • Users
    • Login

    unresolved external symbol "void __cdecl maxon::_ConsoleOutputC4D when compiling under R19.

    Cinema 4D SDK
    r19 c++ sdk
    4
    15
    1.4k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • P
      pim
      last edited by

      After some extra tests I found out that when I comment out all DiagnosticOutput()

      // DiagnosticOutput("Rendering Phase: Finalize");
      

      it compiles and links ok!

      What could be wrong?

      1 Reply Last reply Reply Quote 0
      • P
        pim
        last edited by

        Pinned it down to

        DiagnosticOutput(String());
        
        1 Reply Last reply Reply Quote 0
        • M
          m_adam
          last edited by

          Use maxon::String

          MAXON SDK Specialist

          Development Blog, MAXON Registered Developer

          P 1 Reply Last reply Reply Quote 0
          • P
            pim @m_adam
            last edited by

            And here another one

            DiagnosticOutput("Loading Project: " + fn.GetString());
            

            So I should use

            DiagnosticOutput(maxon::String());?
            

            And what to use for this one?

            DiagnosticOutput("Loading Project: " + fn.GetString());
            
            1 Reply Last reply Reply Quote 0
            • P
              pim
              last edited by pim

              DiagnosticOutput() statements like these

              DiagnosticOutput("Rendering successful: " + maxon::String::FloatToString((GeGetTimer() - starttime) / 1000.0) + " sec.");
              

              give me the following warning:

              c20f6f21-40cc-489c-99fe-de3565c3e1f5-image.png

              Normal DiagnosticOutput() are ok

              DiagnosticOutput("Rendering successful: ");
              
              1 Reply Last reply Reply Quote 0
              • M
                m_adam
                last edited by m_adam

                This is part of the R15 transition Change in R15, more information on
                Debugging - Conversion To String
                and String - Creation Manual.

                And you are looking for maxon::FormatString

                Cheers,
                Maxime

                MAXON SDK Specialist

                Development Blog, MAXON Registered Developer

                1 Reply Last reply Reply Quote 0
                • P
                  pim
                  last edited by

                  Ok, I will read and try to understand.

                  Pim

                  1 Reply Last reply Reply Quote 0
                  • P
                    pim
                    last edited by

                    Yes, I should have read the manual.
                    In R19 it is GeConsoleOut() and not DiagnosticOutput()

                    C4DSC 1 Reply Last reply Reply Quote 0
                    • C4DSC
                      C4DS @pim
                      last edited by

                      @pim
                      I have the original R16 and R19 SDK documentation installed locally, and there I do find DiagnosticOutput.
                      As such, I am still wondering what the issue is you have.

                      here's an excerpt from the R16 SDK documentation:

                      #define DiagnosticOutput 	( 	  	fmt,
                      		  	... 
                      	) 		
                      
                      DiagnosticOutput outputs text into the console. The output is visible in debug builds or in a release build when the debug console with diagnostic output is activated. The full printf syntax can be used for the format string. THREADSAFE.
                      

                      To me this seems mostly identical to what the current R21 online documentation mentions.
                      So in theory it should be no problem for R19.

                      1 Reply Last reply Reply Quote 0
                      • P
                        pim
                        last edited by

                        Yes, strange.
                        But going from DiagnosticOutput() to GeConsoleOut() solved the issue.
                        Using maxon::String in DiagnosticOutput() seems to be the issue.

                        1 Reply Last reply Reply Quote 0
                        • M
                          m_adam
                          last edited by

                          Looking at the doc in R19:

                          5fdf5fb0-1327-4589-b6b6-d68af8869c11-image.png
                          821d97fa-e103-4cca-84b1-85f0f50304f0-image.png

                          So I'm afraid there is no simple solution that will work on each version maxon::String being introduced in R20, you will need to adapt your code.

                          Cheers,
                          Maxime.

                          MAXON SDK Specialist

                          Development Blog, MAXON Registered Developer

                          1 Reply Last reply Reply Quote 0
                          • First post
                            Last post