Jump to content

Vanilla

Developer
  • Content Count

    413
  • Joined

  • Last visited

  • Days Won

    52
  • Yangs

    92 [ Donate ]

Vanilla last won the day on January 19

Vanilla had the most liked content!

Community Reputation

1,070 Godlike

About Vanilla

  • Rank
    Noble

Profile Information

  • About Me
    <p>
    ¯\_(ツ)_/¯
    </p>

Recent Profile Visitors

11,319 profile views
  1. Vanilla

    open

    One thing I can absolutely recommend is stop using package system. It gave me enought trouble. I recommend you to stick with the ports tree and build your programs this way. Why do I say this? I've seen a lot of issues occuring with package system and building the source. If you build the programs via ports tree you make sure they are being built according to your system environment. Especially when encountering lib problems it might help you fix this issue. Next I'd like to know what exactly are in those lines? #7 0x00446040 in CClientManager::FlushItemCacheSet (this=0xffbfe910, pid=792) at ClientManager.cpp:1408 #8 0x0043c308 in CClientManager::UpdateLogoutPlayer (this=0xffbfe910) at ClientManagerPlayer.cpp:1335 And obviously Main.cpp:58 Can you post the whole functions and mark down the line that's mentioned there? And thanks for using it, though it's clearly outdated and would need a few fixes here and there ^^' I'm glad you like my work nevertheless and I hope you'll enjoy it in the future, too!
  2. Vanilla

    open

    Downgrading FreeBSD version only masks the problem. Are you running it on the same machine as you're building it? If no, what version does the target system and the building system have? Can you call ldd db? What compiler are you using?
  3. Vanilla

    open

    what settings do you have that you need to use a very old toolset? And why wouldn't that be possible with more recent toolsets?
  4. Vanilla

    open

    I recommend doing what the error tells you: Right click and Upgrade solution. This way you'll be using the more recent toolset. As I said, it'd work out of the box and compile just fine.
  5. Vanilla

    open

    You can often check if your distribution allows to use older toolsets. This is afaik the case with 2017 and 2019, but I'm not sure if that works on 2013, too. I wouldn't try it if I were you. Your best bet is to just upgrade to the newer toolset... It'd work out of the box without having to modify anything.
  6. Vanilla

    open

    If it's not working we need further information. What exactly doesn't work? The query? And why? What error do you get? Any new syserr/syslog entries?
  7. Vanilla

    open

    I cannot agree more. If there's need for a special encryption (and trust me, there is) you can just use a tool that's already included in source: Metin2PackMaker. Afaik it's bugged from start and needs a bit of a setup but it's not that much. As soon as you have it working you're simply having a program that can archive and extract pack files. After this you can think about changing compression or encryption algorithms. It's definitely worth it.
  8. But you do have logfiles, don't you? Without it debugging will be very difficult. We need to know if the client sends the appropiate packet and if the server receives it and what it does with it. Thus reading the syslog is very important even if there's no clear error happening.
  9. Vanilla

    open

    Best way to determine this is analyzing a .wav file that's currently in client. I did that for fishing_fail.wav from Sound/warrior/fishing and it tells me: 353 kbps with 22 KHz So make sure you convert your file with a bitrate of 353 kbps. I dunno if other values are possible but this one should be a safe one.
  10. Vanilla

    open

    afaik if you're going for WAV you need to be cautious about the bitrate of your file. If you do not set it to the supported range you'll encounter exactly this issue. It's not the converters fault, it's a setting you may be able to change in almost any converter.
  11. Vanilla

    open

    Well in that case you either have to fix the code or get it somewhere. I don't know what you downloaded and who did what on these script files but certainly they seem to be out of sync.
  12. Vanilla

    solved

    Your faulty line is: self.toolTipAlignment.AutoAppendTextLine(localeInfo.TITLE_NAME_LIST[grade], gradeColor) How does TITLE_NAME_LIST look like? And what is your grade? Most likely your title (Pvp title) mismatches and therefore the 'grade' value is higher than your list of titles. This leads to your issue. Check if you made some changes there and if everything is correct like it should be.
  13. first you shouldn't use devel compiler, you'd rather take a stable one. Second there's no reason in using GCC anymore since clang is now part of FreeBSDs base system. Though if you wanna use GCC that's fine, but you shouldn't use devel versions. They can lead to unexpected outcome like you mentioned. Try to revert what you do and go for a stable version. If that doesn't work we need more information on what exactly happens (logfiles etc..)
  14. Vanilla

    open

    Oh yes, I was blind about that. Didn't even look at the caracter, my bad^^' Well, you have implemented the weapon in a wrong way. Did you check logfiles? Either you're missing the line in item_list.txt or your 3d model is missing/corrupt. Can you check this?
  15. Vanilla

    solved

    This means that something is already bound to this address (ip and port). So in this case you either have another program running that listens to the ports of ch2 or ch2 is already running. Can you check with ps -aux if ch2 is already running? Also I saw a critical error from your Ch2 log: !!! FATAL ERROR !!! multiple MAP_ALLOW setting!! You may want to have a look at this. It may be the reason why your ch2 freezes.
×
×
  • Create New...

Important Information

Terms of Use / Privacy Policy / Guidelines / We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.