Jump to content

Recommended Posts

hi, when i do sometime teleports i have crash client syserr:

0202 15:22:44679 :: ResourceManager::GetResourcePointer: NOT SUPPORT FILE d:\project\metin2\main\assets\npc\lion\lion.psd
0203 00:29:25257 :: Traceback (most recent call last):

0203 00:29:25271 ::   File "game.py", line 615, in OnChangePKMode

0203 00:29:25282 ::   File "interfaceModule.py", line 802, in OnChangePKMode

0203 00:29:25283 ::   File "uiCharacter.py", line 560, in RefreshAlignment

0203 00:29:25283 :: TypeError
0203 00:29:25283 :: : 
0203 00:29:25283 :: __pack_import() takes at most 4 arguments (5 given)
0203 00:29:25283 :: 

0203 01:34:08525 :: Unknown packet header: 183, last: 126 19

 

can anybody help how to fix it? i think problem in packets .. how to fix it in source?

Link to comment
Share on other sites

1 hour ago, bumxd said:

i think you too don`t know how fix it) cuz i checked:

im try find 183 in client(packet.h) src game(packet.h) common\tables.h but don`t find 183 nothing..

Here is the fix.https://msdn.microsoft.com/en-us/library/2e70t5y1.aspx

Read documentation and i'am sure you will fix all packets.

Link to comment
Share on other sites

1 hour ago, bumxd said:

zxczx

 

#pragma pack instructs the compiler to pack structure members with particular alignment. Most compilers, when you declare a struct, will insert padding between members to ensure that they are aligned to appropriate addresses in memory (usually a multiple of the type's size). This avoids the performance penalty (or outright error) on some architectures associated with accessing variables that are not aligned properly. For example, given 4-byte integers and the following struct:

struct Test
{
   char AA;
   int BB;
   char CC;
};

The compiler could choose to lay the struct out in memory like this:

|   1   |   2   |   3   |   4   |  

| AA(1) | pad.................. |
| BB(1) | BB(2) | BB(3) | BB(4) | 
| CC(1) | pad.................. |

and sizeof(Test) would be 4 × 3 = 12, even though it only contains 6 bytes of data. The most common use case for the #pragma (to my knowledge) is when working with hardware devices where you need to ensure that the compiler does not insert padding into the data and each member follows the previous one. With #pragma pack(1), the struct above would be laid out like this:

|   1   |

| AA(1) |
| BB(1) |
| BB(2) |
| BB(3) |
| BB(4) |
| CC(1) |

And sizeof(Test) would be 1 × 6 = 6.

With #pragma pack(2), the struct above would be laid out like this:

|   1   |   2   | 

| AA(1) | pad.. |
| BB(1) | BB(2) |
| BB(3) | BB(4) |
| CC(1) | pad.. |

And sizeof(Test) would be 2 × 4 = 8.

 

 

 

 

 

 

This is a hint. I'am not working for you. This forum it's called question/answers not work for me.

Read pragmas effects.

 

 

 

Link to comment
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now

Announcements



×
×
  • 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.