Jump to content
Forgot your email address? ×
  • Create New...


  • Posts

  • Joined

  • Last visited

  • Days Won


Gurgarath last won the day on October 31 2020

Gurgarath had the most liked content!



  • Country
  • Gender

Social Networks

  • Discord

Recent Profile Visitors

3508 profile views

Gurgarath's Achievements

Rising Star

Rising Star (9/14)

  • Reacting Well
  • Dedicated Rare
  • Very Popular Rare
  • Collaborator
  • First Post

Recent Badges




Community Answers

  1. Hello, Just for the record, the same thing happens when you Windows + Arrow left or right when you have two monitors with different resolutions, or when you change your DPI (Even when I've updated the method to handle the DPI change it still did the same).
  2. As far as I remember, this topic fixes it and play around with the playable area. I personnally use this to get my metrics. Note that I am using W11 and that Taskbar isn't really easy to tweak without going into regedit. Only available option is to hide it and the metrics catch it greatly.
  3. Because someone I've talked with had an issue with his width in the metin2.cfg. This is the main issue as width is the issue and I wanted people to double-check that they had no issue there. Height on the contrary has nothing to do with the bug, that's why I've kept it normal in my example. Also, the width of the client should be your full monitor width, unless you have your sidebar on the side.
  4. It is the size of the "playable area", not the size of the whole application. For example:
  5. Oh, yes, this isn't a bug this is a feature. Ymir did that on purpose. You can use @Abel(Tiger) fix for this, every window will open on the center of the screen (which is what most modern games do).
  6. I've talked about this with Intel and yeah, the whole check is clumsy, it works only for the second window and if you open it during a specific timestamp. However the fact that it opens at the opposite of the second one is an approach I could understand, but centering it would erase any clumsyness I personally had no issue with the second window, but here you are. Undo the original tutorial and do this (it will render the whole if useless though so you can as well remove it):
  7. Thanks for your share but that's what I said, to adjust to your needs. At first I was going for 7 then needed 8, Haios needed 9 for example. Also, you can add it into "bAnotherWindow" condition if you have the bug more than once with multiple clients.
  8. Hello! Many people complained about a "7 pixel bug" on some clients. For example the client will open a few pixels too far from the left-side of the screen. Usually between 7 and 9 pixel on the right. I still do not know why it happens for some people and not for other. I thought about a visual studio toolset, a screen configuration or whatever but it turns out to be harder to know why it actually happens, I also had only two people talking about this so I cannot get accurate data. Anyway, let's get started it's really easy. The bug looks like this, take from the official client it looks like 1 or 2 pixels only. But it looks almost exactly like it at some moments. First, make sure your metin2.cfg is correct and does not display a weird resolution (like 1913 * 1080). Then just add this small line in PythonApplication.cpp: SetPosition(-8, 0); Right after this one: AdjustSize(m_pySystem.GetWidth(), m_pySystem.GetHeight()); EDIT: If you happen to have it on the second window as well, move the line under the bAnotherWindow check. Just like this: And voilà, it's fixed. Don't hesistate to add or remove one pixel if needed. It's really small and looks like a workaround but I did it really quickly. I didn't test this fix on clients / computers not having the actual bug. If it is a client issue it shouldn't cause any problems, if it's a computer issue, I might need more data to fine-tune the fix. Don't forget to share some data if you have.
  9. This is wonderful and it goes toward a better game
  10. Yeah, it is leaked and it lacks many features and has some issues related to rendering (and categories and whatever). But I think only one version is around
  11. This leaked system is intended to be fully fixed as it lacks MANY things and I highly recommend you to use it if you know what you are doing. About the t identifier, it is ONLY in Martysama sources, so you will need to add this part of the code (Struct autodetect iirc). As xXIntelXx said, many things will be missing and many crashes will occur if you do not fix faulty / unadapted code. The code itself is good, but keep in mind that you need to make it blend into your sources.
  12. Thanks for sharing! I've had this idea and done it for a project of mine. If you want to sacrifice a little bit of loading time you can also place monsters (note they will have no collision and will clip through objects) using the chr. methods. (chr.CreateInstance() and then specify the race and the motion). [Hidden Content] And this is fine AF, really good realisation and good use of it. I love the scenery and the dark-souls mood.

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.