Jump to content
TrinityCore

Kylroi

Members
  • Posts

    385
  • Joined

  • Last visited

  • Days Won

    17

Everything posted by Kylroi

  1. It would be nice to have the full world DB always updated, but you have to realize that we aren't dealing with a release quality or a commercial application. The developers aren't being paid to work on this, so things can and will be handled in a less than optimal way. As for which world updates to run first, that's a tricky one to answer. Chances are, you would be better off to merge the 2 folders and then run all the updates. That way, you shouldn't have EventAI or creature AI changes being applied when those aspects were removed by an update. If I didn't have custom things in my world DB, I'd offer you an sql of what I'm running on. For the most part, the only "custom" things are some weapons that I made (items 133475-133480).
  2. You mean ACE 6.0.3, since gcc isn't even to the 5.x series (yet).
  3. Sadly, the "How to" for Linux is a little outdated. You probably need to upgrade your gcc version. Plus, a recent announcement suggested that Trinity would require gcc 4.7.2 or higher, so you'll want to upgrade anyway. See http://www.trinitycore.org/f/topic/9214-updated-trinitycore-requirements-deprecation-of-old-compilers/ for the update announcement.
  4. With 4.3.4, item_template is used only as a supplementary source. The core will use the dbc/db2 files to define items. There is also a worldserver.conf setting to enforce the data file definitions or allow the DB to override them ('DBC.EnforceItemAttributes = 1' is in the worldserver.conf.dist). As for the SQL updates, ignore auth and characters updates, but apply all of the world updates (in order).
  5. You won't need 2 copies of those folders unless you simply want to have the extra space wasted. If C:Trinity is where you intend to have the servers executed from, just move those folders over as subfolders (i.e. C:Trinitydbc). Assuming that you simply renamed the .conf.dist files to just .conf, you should be set to go.
  6. Microsoft just needs a swift kick in the .NUTs for that mess. The .NET Framework was a good idea, but it should have been implemented better (from everything I've read and encountered).
  7. It would seem that sql/updates/auth/2013_09_29_00_auth_misc.sql saw the removal of rbac_roles and rbac_groups from the database. As such, any updates that are trying to change those tables can be removed. If you look at the end of the file I just mentioned, you will see 7 tables being removed because of being obsolete (the core, at that point, doesn't use them).
  8. Agreed on the OS issue being stupid, and that's pretty much what I was trying to point out (not clear enough for someone, so my bad). I happen to run 2 Mac systems, 2 Windows systems, and 3 Linux systems at this time. For the most part, the 3 choices are equal, making it all a matter of personal choice (not which is more versatile). Personally, I find Windows to best serve personal entertainment (mostly gaming). It's Linux (Fedora Core 18, I think it is) that runs my entertainment center. I already said my router is Linux (FC12...it's working, so why update it). Then I have a Linux server for my own domain (FC5, co-located). As for the SYNC issue, you're fortunate. I can't enable bluetooth on my iPhone while the car is running or it won't pair up. If I enable bluetooth and then start the car, it's all good. Before saying "just leave bluetooth on", I shouldn't have to do that to compensate for firmware failures. Plus, I turn it off to conserve battery power. I prefer to charge every 3 to 4 days rather than every night. Also, I have tried to pair up a Samsung Android phone that won't even pair up with 2 different Ford cars (2010 and 2013 models). That same phone will pair up with bluetooth headsets and my Mac mini. Ford techs tried everything they knew, and I even tried some tricks, but the phone simply won't pair up. That's all I need to know that Microsoft doesn't have it quite right. So long as you have a phone that can be paired, you're absolutely right that it does a good job.
  9. Honestly, that figures. Microsoft tends to break things constantly. I remember when DirectX wasn't checking what version was installed, so older versions would overwrite newer files and totally mess up the system. Those were the days when I loved my job because I could fix it easily, but most "experts" said "reformat and reinstall" to people in that situation. Because you got it fixed, that's good enough for me.
  10. It's Microsoft, you know. If it was supposed to make sense, that company wouldn't be the one putting the product out. Sorry, I've never really been a Microsoft fan, even if my best system was always running Windows (mostly for gaming purposes only). There are still issues with 15 year old products from Microsoft, not to mention the quirks with Ford's SYNC (powered by Microsoft). Seriously, though, glad that got you fixed up. I was wondering if it was a matter of all that 32-bit software on a 64-bit version of Windows. Instead, it seemed to be a software bug that got fixed by upgrading to a newer version.
  11. How is this remark even relevant to the request for help? Drive letters aren't a problem at all (I know this for a fact).
  12. If you're familiar with the Terminal app on OSX, you're familiar with BSD (a flavor of unix). Linux may not be BSD, or even BSD-based, but it is very BSD-like. There's a lot of code that will compile for OSX and Linux with essentially no changes. For a first time Linux user, I would suggest the Ubuntu distribution. That version has been worked on in an attempt to bring all the conveniences of Windows/OSX to a Linux installation. As with all things, there will be variances, but I think you'll find it to be a much more stable and powerful platform.
  13. Sorry to hear of your (forced?) downgrade. You would have been better off if you had done Linux.
  14. The suggestion to only use C: also resulted in a completely fresh setup that would have cleared other problems, too (leftover files, corrupt settings, etc). If the PATH still had directories in it that existed but were mostly empty, CMake likely assumed the contents were all there. As I pointed out, CMake, compiler, and source are not required to be on the same drive for proper operation. If they can be separate, claiming that they mess up if not installed to the same drive is simply not going to be true. Additionally, since there had been successful compilations in the past, it is easily seen that a simple configuration of where the source and build directories are was not the problem. I'm still thinking that the problem may have been tied to 32-bit Visual Studio being used on a 64-bit Windows. CMake might have seen a 64-bit OS and made the assumption that 64-bit compilers were available, thus it had errors. When a 32-bit Windows was used, suddenly it all worked like it used to.
  15. CMake doesn't have a problem of source on one drive and project/compile on another. That's my exact situation. My C: drive has the build directory, but my source is on an aptly named S: drive. I don't think the multiple directories was a factor at all, but leftover files is certainly a possibility (especially with MicroSloth in the works).
  16. Are you loading 32-bit or 64-bit versions of the Visual Studio compilers? I know you were compiling the core for 32-bit, but you can use the 64-bit compilers without issue. It's the creation of 64-applications from the Express Editions that requires extra steps (supposedly). I'm just wondering if CMake is seeing a 64-bit OS and expecting only 64-bit compilers when you have the 32-bit version installed. This is just a guess, of course.
  17. There has to be a simple solution. I'm using that 2.8.11.2 version with VC2010 Express. Then again, we are talking about Windows, here. I don't think that you wouldn't be having this trouble on a Linux system.
  18. Going 64-bit with Express will be tricky, but if you're willing to do it, it can be helpful. However, since you're on Win7, why not use 2012 Express? It may work better with the newer CMake.
  19. First, is there a reason that you are compiling for 32-bit rather than 64-bit? Second, are you compiling on one system to run on another? Third, is that the full VS2010 or Express Edition? Lastly, can you try a slightly older version of CMake (like 2.8.11.2)?
  20. Looks like you don't have OpenSSL installed.
  21. If you pulled the latest code, you will want to run all the updates for the database. I believe there are scripts (for Linux) to combine the many updates into a single file, if that will help.
  22. There should be 3 different databases: auth, characters, and world. The database you were importing is specifically the world database. Obviously, with the conf file allowing that to be set, you can call it something other than world, but the other 2 databases need to be created separately with the appropriate sql files from the source tree (see /sql/create, /sql/base, and /sql/updates).
×
×
  • Create New...