these weapons are rank9
these weapons are rank9
And that's how i fixed this weapons:
http://s53.radikal.ru/i141/1008/11/899c4d822d72.jpg
http://i062.radikal.ru/1008/88/22245bf41e08.jpg
http://s16.radikal.ru/i190/1008/59/3e72e7952a5f.jpg
http://i076.radikal.ru/1008/1a/a5fe9274e024.jpg
http://s49.radikal.ru/i125/1008/d6/56ca873a838e.jpg
http://s43.radikal.ru/i101/1008/fe/98fddafc22a4.jpg
http://s43.radikal.ru/i102/1008/19/3f16709ca1f2.jpg
http://i056.radikal.ru/1008/d0/b2b3f9093e04.jpg
http://s005.radikal.ru/i212/1008/ce/1bf8dc68d0c6.jpg
http://s49.radikal.ru/i125/1008/c3/a411a0947bd1.jpg
http://s44.radikal.ru/i104/1008/74/bbe84291bc66.jpg
http://s55.radikal.ru/i147/1008/32/1b25efdaebf9.jpg
http://s58.radikal.ru/i162/1008/a2/82c709cf7679.jpg
http://s40.radikal.ru/i087/1008/95/6d7e8187701f.jpg
http://s52.radikal.ru/i135/1008/55/1ac9b2a8309a.jpg
http://s53.radikal.ru/i139/1008/5d/63700593d20c.jpg
http://i074.radikal.ru/1008/04/ef22edd54d56.jpg
http://s52.radikal.ru/i137/1008/d0/6d7a32311920.jpg
http://s40.radikal.ru/i087/1008/fb/0a8dbc53d4e5.jpg
http://s006.radikal.ru/i215/1008/4b/4e9c88e3652e.jpg
very nice, you have slightly more gfx working than me.
how did you manage to fix all of the elementid: 200s and 210s?
surely not manually?
210 GFXELEMENTID isn't working, so I just deleted it. I've made a gfx language for NotePad++, and fix all effects manualy. On the 1st day i was making a list of all using effects. On the 2nd day I was making a list of all textures of used effects, and fixing effects. On the 3rd day I was testing all effects one by one, and then fixing not worked effects. And on the 4th day (today) I was fixing ecm files (I also made a ecm language for a NotePad++), and testing weapons.
4 days of manual fixing and I got almost maximum working effects.
very very nice.
thats alot of manual fixing!
did you have problems with anything except the elementid: 200s then?
i have found ronnys or eistigers editors can fix everything else.
No, it's thery simple to fix. I fix effects to MOXTVersion 58. But there was 1 problem, in chinese developers. They made a few bugs in effects, and that was a reson of not working effects, or crushing client.
Last edited by Du100; 18-08-10 at 06:46 PM.
OMG xD you lags like hell on your video !Originally Posted by PWReadyGO
very interesting.
is there ever any chance of you sharing which fields need to be edited or changed?
i have spoken to eistiger about it and he explained the gfxelementid:200 is perfectly supported, you just have to leave/remove the right things, and most editors get it wrong.
Find them your self. It's very easy, but not for sharing. You just need to compare working variant, and non working variant.
i never get those gfx200 blocks to work, so here is a tutorial how some of these blocks can be replaced
my base setup: i've fixed all 19***.gfx files in advance with sMODfix and re-order option activated
(** and all ecm's are also fixed with sMODfix)
- this is our example, the initial blade
- first open the gfx file you want to fix
- now go to the gfx200 block that don't work
- gfx200 blocks are some kind of parent container that contains child gfx in a seperate file
- in the gfx200 block look for "GfxPath:" this is a child gfx file
- open the child gfx file
- now lets see what happen when we replace the gfx200 block by all blocks from it child file (don't forget to change gfxelement count if you i.e. replace 1x gfx200 block with 4x child blocks you have to add +3 to gfxelemntcount)
- nice, effekt is now working but scale/position is wrong because the parent transformation are not applied because the childs are now no longer childs of gfx200
- to fix the the scale/position you have to multiply the parent(gfx200) scale with the each child block scale and also add parent(gfx200) position to each child block position, same with direction...
- when you're done the blade now got an glowing eye
- i'm sure you're to lazy to do all this recalculation, so i've a tool which do the math for you
- on the left textbox enter the text of the gfx200 block
- in the center textbox enter all blocks from the gfx200 child file (only the blocks not the whole file!)
- now click the button and the right textbox will be filled with the child blocks with re-calculated scale/position/direction
- copy the content of the right textbox and return to your editor
- replace the gfx200 block with the copied and re-calculated child blocks (don't forget to change gfxelement count if you i.e. replace 1x gfx200 block with 4x child blocks you have to add +3 to gfxelemntcount)
- try this for all other gfx200 blocks in the file
- save the file, add them to the pck and check it out ingame...
Oh and don't waste your time with manual fixing, i'll start adding such a feaure with gfx200 replace to sMODfix when i'm back from vacation next week...
Last edited by ronny1982; 19-08-10 at 12:53 PM.
what i want to know is why did they add a full set of these weapons, but they only use like 8 of them ingame? 1 per class.
and i remember being told smodfix deletes too much from a gfx file?
also something about filter:1, ill have to ask around a bit.
what would really really help is if somebody could share a working gfxelementid:200 at any version.
then we have something to go by, i cant find any.
i don't think sMODfix removes to much, it fixes things like silk perfume and mammoth mounts automatically, the parameter replacement is based on the gfx and ecm files from PWI 1.4.2 v283 which are <= 1.3.6 that are a lot of reference files. If you don't remove some parameter and the gfx is working don't mean that this parameter is really used, i.e. hNumber x wNumber -> dwColor these parameters are garbage but if you want you can let it stay in your file...
CN 1.3.6 hold exactly 2 files that contain gfx200 blocks, these blocks looks similar to the output of sMODfix...
To locate the files, open the CN 1.3.6 gfx folder in sMODfix, enter the parameter "GFXELEMENTID: 200" and click "CT FILTER" this will filter the given filelist with only files that contain "GFXELEMENTID: 200"
Last edited by ronny1982; 19-08-10 at 03:14 PM.
i never get those gfx200 blocks to work, so here is a tutorial how some of these blocks can be replaced
my base setup: i've fixed all 19***.gfx files in advance with sMODfix and re-order option activated
(** and all ecm's are also fixed with sMODfix)
- this is our example, the initial blade
- first open the gfx file you want to fix
- now go to the gfx200 block that don't work
- gfx200 blocks are some kind of parent container that contains child gfx in a seperate file
- in the gfx200 block look for "GfxPath:" this is a child gfx file
- open the child gfx file
- now lets see what happen when we replace the gfx200 block by all blocks from it child file (don't forget to change gfxelement count if you i.e. replace 1x gfx200 block with 4x child blocks you have to add +3 to gfxelemntcount)
- nice, effekt is now working but scale/position is wrong because the parent transformation are not applied because the childs are now no longer childs of gfx200
- to fix the the scale/position you have to multiply the parent(gfx200) scale with the each child block scale and also add parent(gfx200) position to each child block position, same with direction...
- when you're done the blade now got an glowing eye
- i'm sure you're to lazy to do all this recalculation, so i've a tool which do the math for you
- on the left textbox enter the text of the gfx200 block
- in the center textbox enter all blocks from the gfx200 child file (only the blocks not the whole file!)
- now click the button and the right textbox will be filled with the child blocks with re-calculated scale/position/direction
- copy the content of the right textbox and return to your editor
- replace the gfx200 block with the copied and re-calculated child blocks (don't forget to change gfxelement count if you i.e. replace 1x gfx200 block with 4x child blocks you have to add +3 to gfxelemntcount)
- try this for all other gfx200 blocks in the file
- save the file, add them to the pck and check it out ingame...
Oh and don't waste your time with manual fixing, i'll start adding such a feaure with gfx200 replace to sMODfix when i'm back from vacation next week...
Nice Ronny.
we can actually get dwcolor working you know, its supported in annother id.
what makes you believe that it's working? Do you have an example gfx that shows the graphical difference with and without dwColor
you can use simple searching tools such as windows grep to find them....
havnt verified this as working, but thats the general idea.Code:GFXELEMENTID: 124 Name: Unnamed3 SrcBlend: 5 DestBlend: 2 RepeatCount: 1 RepeatDelay: 0 TexFile: 纹理\通透.dds BindEle: ZEnable: 1 MatchGrnd: 0 GroundHeight: 0 TexRow: 1 TexCol: 1 TexInterval: 50 Priority: 4 IsDummy: 0 DummyEle: Warp: 0 TileMode: 1 TexSpeed: 0.300000 TexSpeed: 0.300000 UReverse: 0 VReverse: 0 UVExchg: 0 RenderLayer: 0 NoDownSample: 0 wNumber: 8 hNumber: 4 -0.400292 0.123913 -0.689449 dwColor: ffffff -0.326642 0.203023 -0.773963 dwColor: ffffff -0.250000 0.306979 -0.937915 dwColor: ffffff -0.101153 0.344879 -0.877115 dwColor: ffffff 0.061727 0.320945 -0.982836 dwColor: ffffff 0.236307 0.281072 -0.940151 dwColor: ffffff 0.327373 0.201141 -0.747359 dwColor: ffffff 0.375000 0.180498 -0.819979 dwColor: ffffff -0.387165 0.108216 -0.684032 dwColor: ffffff -0.312894 0.128668 -0.765098 dwColor: 78ffffff -0.217603 0.140607 -0.864169 dwColor: ffffffff -0.101153 0.168591 -0.959376 dwColor: ffffffff 0.061727 0.168591 -1.007748 dwColor: ffffffff 0.240299 0.152182 -0.875478 dwColor: ffffffff 0.280784 0.144274 -0.830513 dwColor: 78ffffff 0.407539 0.106874 -0.701684 dwColor: ffffff -0.387165 0.104708 -0.671745 dwColor: ffffff -0.326642 0.046275 -0.773963 dwColor: 78ffffff -0.223020 0.000000 -0.937915 dwColor: ffffffff -0.101153 0.000000 -1.007748 dwColor: ffffffff 0.061727 0.000000 -1.007748 dwColor: ffffffff 0.240299 0.009442 -0.911097 dwColor: ffffffff 0.334947 0.064249 -0.780639 dwColor: 78ffffff 0.367020 0.048037 -0.848476 dwColor: ffffff -0.344810 0.065339 -0.708263 dwColor: ffffff -0.315350 -0.016909 -0.852504 dwColor: ffffff -0.178580 -0.079189 -0.919010 dwColor: ffffff -0.025214 -0.121000 -0.853500 dwColor: ffffff 0.068085 -0.142984 -0.963989 dwColor: ffffff 0.285360 -0.050640 -0.920896 dwColor: ffffff 0.338843 -0.003188 -0.754724 dwColor: ffffff 0.309233 0.023080 -0.733563 dwColor: ffffff fGridSize: 0.500000 fZOffset: 0.000000 StartTime: 0 KEYPOINTCOUNT: 1 InterpolateMode: 0 TimeSpan: -1 Position: 0.000000, 0.000000, 0.000000 Color: -922746881 Scale: 1.000000 Direction: 0.000000, 0.000000, 0.000000, 1.000000 Rad_2D: 0.000000 CtrlMethodCount: 0
ah ok i thought you have a same gfx that looks different with dwColor and without dwColor...
than i'll not look into this and trust my parameter conversation list, like i said none of the PWI 1.4.2 v283 gfx files with version <= v58 has this dwColor, so i'm really sure it was introduced later...
Last edited by ronny1982; 21-08-10 at 04:31 PM.
how to fix GFXELEMENTID: 210?
Just delete it.
人物\通用\飞行\巨灵鸟_鸟观.gfx
thats file all used gfxelementid : 210, than we never get work this gfx?
That's right.
when i get working GFXELEMENTID: 200, AF.log always show
[18:49:00.468] AFilePackage::OpenSharedFile, Failed to find file [Gfx\] in package !
[18:49:00.468] AFileImage::Can not open file [Gfx\] from disk!
[18:49:00.468] AFileImage::Open(), Can not init the file image!
[18:49:03.656] AFilePackage::OpenSharedFile, Failed to find file [Gfx\] in package !
[18:49:03.656] AFileImage::Can not open file [Gfx\] from disk!
[18:49:03.656] AFileImage::Open(), Can not init the file image!
i have check all texture. but still like thats, it will not show if GFXELEMENTID: 200 not fixed, anyone know where is problem?
Here is my C19 GFX Pack
*Powered by sMODfix v2.0 Developer Alpha
- the left dagger has some gfx blocks with wrong position
- check "人物\通用\武器\武器效果\19品匕首_基础右.gfx" and fix the blocks manual (as far as you know whats the correct position)
- the affected blocks in the files are block 5 (Name: Child_Block_4) and following
Gallery
Last edited by ronny1982; 23-08-10 at 11:57 PM.
ronny.. what for *.smd options?
Reply With Quote
