Jump to content
TrinityCore

CDawg

Members
  • Posts

    1477
  • Joined

  • Last visited

  • Days Won

    85

Posts posted by CDawg

  1. :D This has been this way for quite some time. Then when people compile, follow the wiki and dont produce any debug logs, we yell back at them that they didnt compile correctly and cant help them.

    I honestly thought it was intentional to compile in release, so that in the OPs case here he is just complaining about how slow it is.

    Better to be slow compile, then to have issues you cant identify.

  2. 15 hours ago, Bokrom said:

    Hi all. I was patching a custom script and building my solution wasn't fixing the issue. I copied the authserver and worldserver .exe's from my Debug folder into my Release folder and my script now works! But for some reason the .exe's are about twice as large as the old ones, and the world server takes much longer to initialize than the old one, 45 sec. compared to just 6. Any ideas on what's causing this? Sorry if it's something obvious, I've only been spending most of my time now doing .dbc editing and less in the core, so I may have forgotten something simple.

    The whole idea it's larger and slower (in debug) is for that very reason. Where if it crashes, hopefully there is a catch to the exact symbol where it crashed and it logs just about everything in memory when you execute the binary (why worldserver.exe is so slow).

    As for the DBC editing, well, you are on your own with that one. That would cause client issues if something goes wrong.

     

    EDIT:

    This will help you understand the differences. http://haacked.com/archive/2004/02/14/difference-between-debug-vs-release-build.aspx/

  3. 9 hours ago, gegge said:

    It's cool and.. damn, everyone use it, we are in 2017

    I actually hate it. No offense, but it's sometimes unreliable. I have friends post links and message me, where they asked later why I didn't reply, in which I would respond with "I never got that message".

    Anyhow, IRC is the most reliable source you can get. I will still use it in the year 2040 (if i live that long)

  4. Only one address for one realm.

    Your ports need to be different, also not sure why your localadress is in the 5.x.x range. it should be 127.0.0.1. Your lan address' are correct. You need to configure and whitelist the 8085 and set your realmid 2  to 8086 in your .conf for your second realm

  5. I didn't see any documentation to compile with clang. so...

    To everyone that wants to use it i added options to my cmake, so every compile by default will be clang

    -DCMAKE_C_COMPILER=clang -DCMAKE_CXX_COMPILER=clang++
    

    Also, for debian users 'sudo apt-get install clang' installed all the compilers and libraries for me. If you choose to back to gcc, just blow away the options and rebuild with gcc.

    I don't have access to edit the documentation and add this piece.

  6. On 2/11/2017 at 0:25 PM, Fuckinloop said:

    Little Random but does anyone remember the free-trail wow.exe that streamed the client and never downloaded all the patch files? would be cool to host everything remotely with a barebone wow.exe it was during wotlk

    Yes, unfortunately, blizz has scrubbed through all of their static or s3 buckets and removed all traces to that streaming service. (Im assuming that blizz caught on that private server idiots were direct linking to it)

    Iv'e search for close to a year with no success.

    • Upvote 1
  7. 6 hours ago, tot78 said:

    Would be good to have this indeed. For the 3.3.5 branch as well.

     

    -- chaodhib

    Again...

    Start off by seeing what works as percentage scale... then list everything. Everything! (then assume from there that, that is what needs work or improvements)

    It's alot of work and the devs would have to continually maintain it. As you search other posts you will see other members that have created these exact lists, but never go back to update it when there is so much activity.

    BTW, thanks for the downvote... Learn some constructive criticism and do it yourself. It takes alot of time and if you want to invest in doing it, then you can get pats on the back. The main problem is maintaining it. I recommend a percentage level, since most scripts/instances/bgs, etc... will not be 100%

  8. 3.3.5a (enUS) hash should match or never change (This was for Windows OS 8/XP). I can't speak for other locale copies, nor operating systems outside of Windows.

    After Wrath (Cata) It was almost impossible to do a hash check. It was a nightmare for BlizzCS to assist customers at the time (they enabled the live streaming) which varied across everyone, even for clients in certain regions within or outside the US. (using enUS version)

     

    • Upvote 1
×
×
  • Create New...