Problem with droped itens in 2017-06-14bRagexeRE

[Feilor]

Everytime I kill a mob I get a effect in the screen or I kill a mob and it drop itens I get this:
http://prntscr.com/gd4nlm

 

My patch file:
 

5 Enable Proxy Support
6 Force Send Client Hash Packet
8 Custom Window Title
9 Disable 1rag1 type parameters (Recommended)
13 Disable Ragexe Filename Check (Recommended)
20 Extend Chat Box
21 Extend Chat Room Box
22 Extend PM Box
23 Enable /who command (Recommended)
26 Fix Camera Angles (FULL)
28 Increase Headgear ViewID
32 Increase Zoom Out Max
33 Always Call SelectKoreaClientInfo() (Recommended)
34 Enable /showname (Recommended)
35 Read Data Folder First
36 Read msgstringtable.txt (Recommended)
37 Read questid2display.txt (Recommended)
38 Remove Gravity Ads (Recommended)
39 Remove Gravity Logo (Recommended)
40 Restore Login Window (Recommended)
41 Disable Nagle Algorithm (Recommended)
44 Translate Client (Recommended)
46 Use Normal Guild Brackets (Recommended)
47 Use Ragnarok Icon
48 Use Plain Text Descriptions (Recommended)
49 Enable Multiple GRFs (Recommended)
50 Skip License Screen
53 Use Ascii on All LangTypes (Recommended)
61 Disable Packet Encryption
64 @ Bug Fix (Recommended)
65 Load Custom lua file instead of iteminfo*.lub (Recommended)
68 Enable 64k Hairstyle
73 Remove Hourly Announce (Recommended)
75 Enable Flag Emoticons
84 Remove Serial Display (Recommended)
86 Only First Login Background
88 Allow space in guild name
90 Enable DNS Support (Recommended)
91 Disconnect to Login Window
97 Cancel to Login Window (Recommended)
100 Disable Multiple Windows
204 Increase Attack Display
213 Disable Help Message on Login (Recommended)
229 Enable Emblem hover for BG

I'm using secret Patches folder and lastest nemo

Edited August 26, 2017 by luan122
info abot nemo

[Feilor]

I solved this problem using system folder from this git:
https://github.com/zackdreaver/ROenglishRE

[sader1992]

try it like that and see if it work

9 Disable 1rag1 type parameters (Recommended)
13 Disable Ragexe Filename Check (Recommended)
19 Enable Title Bar Menu
33 Always Call SelectKoreaClientInfo() (Recommended)
35 Read Data Folder First
37 Read questid2display.txt (Recommended)
38 Remove Gravity Ads (Recommended)
39 Remove Gravity Logo (Recommended)
40 Restore Login Window (Recommended)
41 Disable Nagle Algorithm (Recommended)
46 Use Normal Guild Brackets (Recommended)
48 Use Plain Text Descriptions (Recommended)
49 Enable Multiple GRFs (Recommended)
53 Use Ascii on All LangTypes (Recommended)
64 @ Bug Fix (Recommended)
65 Load Custom lua file instead of iteminfo*.lub (Recommended)
73 Remove Hourly Announce (Recommended)
84 Remove Serial Display (Recommended)
90 Enable DNS Support (Recommended)
97 Cancel to Login Window (Recommended)
213 Disable Help Message on Login (Recommended)

 

[Feilor]

Same, do you get this error with this patch?

does packet obfuscation change something?
in your patch i put since it hasn't

61 Disable Packet Encryption

because my source has the encrypt lines commented.

[Mikegyver]

12 minutes ago, luan122 said:

Same, do you get this error with this patch?

does packet obfuscation change something?
in your patch i put since it hasn't

61 Disable Packet Encryption

because my source has the encrypt lines commented.

I don't think packet obfuscation would causing trouble. And i'm using this client too.. with packet encryption / packet obfuscation enabled.. no problem when killed monster dropped any items. But just want to ask u. Do your kRO full client is in the latest version? As this is 2017-06-14 exe client, ur kRO also at least on the same date or newer. My suggestion, try to patch your kRO client first and see either this problem happen again or not.

[mrjnumber1]

doesn't matter what you patch - this is a glitch in 2017 client period. it's not just with dropped items. when numbers come out it shows up accidentally too close to you and they look invisible, or.. gigantic, in most cases. i have it too!

..unfortunately i have no idea what the fix is. it's possible we need to make a fix in the rendering code that converts things from what's on screen and where to make it work

 

please use win+r -> dxdiag and Save All Information and post that file in paste2.org and share it here, so we can compare! here's mine https://paste2.org/IxsehZmd

 

that, or, i'll have to do a whole lot of digging to figure out what it is.. ahhh

Edited August 26, 2017 by mrjnumber1

[Mikegyver]

2 minutes ago, luan122 said:

I solved this problem using system folder from this git:
https://github.com/zackdreaver/ROenglishRE

no wonder i don't face this kind of problem coz i've been using zack's data from the start. glad to know this problem not caused by client diffted by nemo patcher...

[Feilor]

3 minutes ago, Mikegyver said:

no wonder i don't face this kind of problem coz i've been using zack's data from the start. glad to know this problem not caused by client diffted by nemo patcher...

yepe, I thought i had the lastest version, but for surprise no... well... everybody make mistakes xD but i hope this help ppl getting this problem like @mrjnumber1 xD

[mrjnumber1]

holy crap it worked, i guess my system/ folder was out of date and it caused some optioninfo to load hecked up.. oh well!

[redlightliu]

On 2017/8/26 at 11:43 PM, mrjnumber1 said:

doesn't matter what you patch - this is a glitch in 2017 client period. it's not just with dropped items. when numbers come out it shows up accidentally too close to you and they look invisible, or.. gigantic, in most cases. i have it too!

..unfortunately i have no idea what the fix is. it's possible we need to make a fix in the rendering code that converts things from what's on screen and where to make it work

 

please use win+r -> dxdiag and Save All Information and post that file in paste2.org and share it here, so we can compare! here's mine https://paste2.org/IxsehZmd

 

that, or, i'll have to do a whole lot of digging to figure out what it is.. ahhh

mrjnumber1 this is my paste2 
I hopy you can fix it
it will become next stable Client

Edited September 6, 2017 by redlightliu

[mrjnumber1]

the fix above worked, some oddity in the system folder was out of date and.. just happened to do it. what it is, i'm not quite sure. it must have been a missing option i just didn't notice! i'll do a diff later, maybe ..