ECM + GFX 1.4.2_v316 @ 1.3.6_v101

can you put the fixes for gfxelementid 210 and 200 in?

Quote:

---

Originally Posted by S3r3n1ty

PS: in the end my other idea did not work, so no use posting it.
Thanks a ton ronny! I'll try that. Would this then also work for the Brilliant Plumes wings? And of course by that I mean starting with the Brilliant Plumes files instead of the spear's?

Edit:
Okay. I tried what you said, ronny, and ran into a couple of problems.
First thing:
I tried to downgrade the .gfx files for the spear to 1.3.6 as you said to, however, they did not come out in the output directory's folder where I specified they should. So, then, assuming maybe they had already become "fixed" previously using your fixes or sMODfix at an earlier time, I continued with what you said to see what I could do.
I did the rest of the procedure you said to try. I also added in my own step- checking each .gfx file in game using a command window. I found out the one that crashes my client whether it's on the weapon or being shown through the command window is this one:
人物\通用\武器\武器效果\杖粉.gfx
none of the other ones seem to crash or do anything particularly unusual.
So, going along with the process, i compared the list of terms that should be or could be in the .gfx file, and everything seems to check out fine. Nothing is there that shouldn't be there.
So, what is the issue then? Could it be that my .gfx files didn't downgrade properly during the initial piece of this manual fix? (seems to be most likely, but then how would I correct that when I can't get them to appear?) Or, is there some other issue within the .gfx file's terms - and by that I mean are the numbers in one of the specific details of the .gfx file off or something?

Any other help with this would be really very much appreciated.

---

If nothing is working, remove the gfx block that cause the problem from the corresponding ecm file:

• open the ecm for the spear
• find "CoGfxNum:"
• decrease the number by one (i.e. "CoGfxNum: 7" -> "CoGfxNum: 6")
• now you have told the model file to use "6" gfx files instead of "7"
• the ecm still has "7" gfx blocks inside, now you have to remove the gfx block that cause the error
• each gfx block in the ecm starts with "FxFilePath: " in your case start searching the block with the file "FxFilePath: 人物\通用\武器\武器效果\杖粉.gfx"
• now you have to find the end of the block (or the beginning of the next block)
• search for the next "FxFilePath: " or "CombineActName: ", this is the line of the following block
• now delete everything from the beginning of the block (including the line "FxFilePath: 人物\通用\武器\武器效果\杖粉.gfx") until the end of the block (excluding the line "FxFilePath: " or "CombineActName: " as it belongs to the next part)
• save the ecm, repack and hope that the removed gfx caused the error...

*use GBK encoding editor when editing these files, double click on a file in sMODfix will use MadEdit for editing...

---------- Post added at 07:10 AM ---------- Previous post was at 07:08 AM ----------

Quote:

---

Originally Posted by rbb138

can you put the fixes for gfxelementid 210 and 200 in?

---

i havn't found any problems with the gfxelementid >= 200 and 1.3.6 client, do you have an example where this caused errors?

The .GFX that causes the error (the one I checked using the in game command console using command d_gfx) is used twice within the .ECM. I should move both blocks of them then and decrease the number by two? or just the one still?
Thanks a ton for the input ronny, this is really helpful to me >.<

Also, well, what is wrong in general if sMODfix is not producing anything in the output directory I set up? I know myself so I'm pretty sure I am doing something wrong, as opposed to maybe the files were already "fixed"... Any ideas what I might have done wrong?

Quote:

---

Originally Posted by S3r3n1ty

The .GFX that causes the error (the one I checked using the in game command console using command d_gfx) is used twice within the .ECM. I should move both blocks of them then and decrease the number by two? or just the one still?
Thanks a ton for the input ronny, this is really helpful to me >.<

Also, well, what is wrong in general if sMODfix is not producing anything in the output directory I set up? I know myself so I'm pretty sure I am doing something wrong, as opposed to maybe the files were already "fixed"... Any ideas what I might have done wrong?

---

yes remove both

sMODfix works on all files that are shown in the filelist, make sure to select ">1.3.6", if no files are shown in the file list than all files are still 1.3.6 or below and no files will be processed...

Thanks a ton again ronny for your help :)
I removed both blocks for that .gfx file in the .ecm for the spear and it works now absolutely fine. I can't even tell what's missing when looking at it. i'll have to keep this in mind for other .gfx's that don't work otherwise. :blush:

the 200 does error depending on the content of the files they link to.

also the 210 is simply unsupported.

Quote:

---

Originally Posted by ronny1982

do you have an example where this caused errors?

---

in .gfx file 82 version and above
in CtrlType: 108 last line
AlphaOnly:
this parameter is cause of crash client

@S3r3n1ty

Can you make a clear guide on how to go about this fix.
Cause i have also the same problem with that G16 wep its causing my client to crash. tried to read all guide here but to no avail still fails me.

Quote:

---

Originally Posted by mEE2

@S3r3n1ty

Can you make a clear guide on how to go about this fix.
Cause i have also the same problem with that G16 wep its causing my client to crash. tried to read all guide here but to no avail still fails me.

---

my opinion is if you can't understand even so simple programm, where you need just to click 2 buttons to make all work, you do not have to try hold server.

P.S. you can't imagine manual fixing, with no programm, hust notepad & your brain

Got it thanks!!

Quote:

---

Originally Posted by S3r3n1ty

Thanks a ton again ronny for your help :)
I removed both blocks for that .gfx file in the .ecm for the spear and it works now absolutely fine. I can't even tell what's missing when looking at it. i'll have to keep this in mind for other .gfx's that don't work otherwise. :blush:

---

Lucky you :P for some reason it didnt work.... will you share? ;P if not, i understand lol i'll keep trying. thx

Quote:

---

Originally Posted by caomhainn

Lucky you :P for some reason it didnt work.... will you share? ;P if not, i understand lol i'll keep trying. thx

---

when fexing programs don't work, use manual fixing

Quote:

---

Originally Posted by Du100

when fexing programs don't work, use manual fixing

---

Thx... even tho i was talkin to Serenity :P

any one have working gfx for new Flight Mounts PWI 350?

Quote:

---

Originally Posted by caomhainn

Thx... even tho i was talkin to Serenity :P

---

Sorry for the late response,...
I did a manual fix for the weapon. I went into a in-game command console and pulled up single .GFX files one-by-one and when I crashed at one of them found out that that was the .GFX crashing my client, deleted the whole "block" of information for that .GFX within the .ECM of the weapon's files, and it worked :) (Ronny is to thank for the help, otherwise I would not know what to do xD)
Normally if things can be fixed using sMODfix I prefer it as it means I don't have to take away anything from the item... but since that didn't work, the manual fix did and I can't notice a difference between mine or anyone else's spear.