Spuddyman95 said, January 13, 2010, 02:02:25 amthere is a bug. when i use subzero's deep freeze on the non fatality compatibility char, it went invisible!fix that.whoaastrange, thanks for reportEDIT: i found the error, sorry, you can wait to the update (not soon) or change by yourself, to do it you need to:Open the shaddap.cnsGo to the state 60731then find this state controller (is easy because is a short state)[State ]type = Helpertriggerall = !numhelper(60733)trigger1 = animelemtime(4) = 10helpertype = NormalID = 60733name = "eternal ice"postype = p2stateno = 60733ownpal = 1then just change the 4 in the trigger1 to a 3, then it must be like thistrigger1 = animelemtime(3) = 10 thats allany other problem please report
Juano Borsalino said, January 12, 2010, 07:36:16 pmLucky Dearly said, January 12, 2010, 08:29:25 amcool, I'll go check them outhmm might be time for me to go to 1.0 Mugen although I hope it will be easy to convert the rest of my mugen roster to 1.0you not need to convert you can use all your old stuffstry download the mugen 1.0 RC6, and do a backup of the new mugen.cfg, then erase the folders data, chars and stages, the take yours (that folders in your winmugen) and move, then overwrite the mugen.cfg from the RC6 that you copied, then your data folder will chagne just in the mugen.cfg file cool, I'll go check this out
Show us a video demonstration of soul ninja UMK3, and don't forget to add shang tsung MK2 and soul ninja umk3 the in-game movelist!
Spuddyman95 said, January 13, 2010, 10:24:37 pmShow us a video demonstration of soul ninja UMK3, and don't forget to add shang tsung MK2 and soul ninja umk3 the in-game movelist! i think time ago in the movelist and make video, but im a little lazy
ran into a bug with the 1.0 version of female ninjaError message: Trigger not valid for mugenversion of character: ailevelError parsing trigger1. 1Error parsing [State -1 -- AI ---,=== ACCIONES AI ===]Error in [statedef -1]Error in code\ninja.cmdError loading chars/FemaleNinjaUMK3/jadeumk3.defError loading p1Library error message: died parsing ailevelEdit: Same error appears with Cyberninja too
Lucky Dearly said, January 13, 2010, 11:52:24 pmran into a bug with the 1.0 version of female ninjaError message: Trigger not valid for mugenversion of character: ailevelError parsing trigger1. 1Error parsing [State -1 -- AI ---,=== ACCIONES AI ===]Error in [statedef -1]Error in code\ninja.cmdError loading chars/FemaleNinjaUMK3/jadeumk3.defError loading p1Library error message: died parsing ailevelEdit: Same error appears with Cyberninja toothats because i commit a error in the DEF, i forgot to change the mugenversion = 1.0 in all the DEf files oops againyou can fix it opening the DEF files and changing that line, all must be mugenversion = 1.0, i think actually say 2002, blablalbalb, change to 1.0
a bit of a glitch with soul ninja umk3 (unless its the stage itself) when I did the stage fatality for the pit 1 the stage doesn't scroll down all the wayEdit: I think it might have to do with my Mugen scrolling since I got the same glitch with female ninja and with some other stage fatalities. I did get the 1.0 versions of your stages Edit: I found a good resolution but ran into another bug, most of the stage fatalities are either ignored or they do the spike fatality (which is the kombat tomb style fatality for most other mugen stages) Also I noticed the finish him music for each of your stages doesn't play with any of the chars (all ninjas and shang tsung)
Lucky Dearly said, January 14, 2010, 05:54:21 ama bit of a glitch with soul ninja umk3 (unless its the stage itself) when I did the stage fatality for the pit 1 the stage doesn't scroll down all the wayEdit: I think it might have to do with my Mugen scrolling since I got the same glitch with female ninja and with some other stage fatalities. I did get the 1.0 versions of your stages Edit: I found a good resolution but ran into another bug, most of the stage fatalities are either ignored or they do the spike fatality (which is the kombat tomb style fatality for most other mugen stages) Also I noticed the finish him music for each of your stages doesn't play with any of the chars (all ninjas and shang tsung)Well the finish him music can fixed if we wait for the ex + alpha series of 1.0 mugen.
Lucky Dearly said, January 14, 2010, 05:54:21 ama bit of a glitch with soul ninja umk3 (unless its the stage itself) when I did the stage fatality for the pit 1 the stage doesn't scroll down all the wayEdit: I think it might have to do with my Mugen scrolling since I got the same glitch with female ninja and with some other stage fatalities. I did get the 1.0 versions of your stages Edit: I found a good resolution but ran into another bug, most of the stage fatalities are either ignored or they do the spike fatality (which is the kombat tomb style fatality for most other mugen stages) Also I noticed the finish him music for each of your stages doesn't play with any of the chars (all ninjas and shang tsung)use the res 640x480, because if you use other then the game localcord change and the stageID system no longer works (it returns wrong values) Spuddyman95 said, January 14, 2010, 01:41:22 pmLucky Dearly said, January 14, 2010, 05:54:21 ama bit of a glitch with soul ninja umk3 (unless its the stage itself) when I did the stage fatality for the pit 1 the stage doesn't scroll down all the wayEdit: I think it might have to do with my Mugen scrolling since I got the same glitch with female ninja and with some other stage fatalities. I did get the 1.0 versions of your stages Edit: I found a good resolution but ran into another bug, most of the stage fatalities are either ignored or they do the spike fatality (which is the kombat tomb style fatality for most other mugen stages) Also I noticed the finish him music for each of your stages doesn't play with any of the chars (all ninjas and shang tsung)Well the finish him music can fixed if we wait for the ex + alpha series of 1.0 mugen. thats true, the last is the mugen 1.0 RC5 EX + alpha, im waiting for a new one for RC6 Well the finish him music can fixed if we wait for the ex + alpha series of 1.0 mugen.
alrighty, I'll try the 640X480 resolution although it might glitch my character selectEdit: the fatalities work but the glitches remain, the pit 1 doesn't scroll down to the bottom of the pit when the fatality is done, a similar glitch occurs with the bell tower fatality too. the pit 2 fatality is misaligned when the impact occurs here are some screens I took of these glitchespit 1 glitch as you can see the scrolling stops here when the fatality is executedpit 2 final scene is misalignedBell Tower, again scrolling issue like the pit 1 only the screen doesn't scroll down showing the opponent hit the spikes
Lucky Dearly said, January 14, 2010, 08:23:08 pmalrighty, I'll try the 640X480 resolution although it might glitch my character selectEdit: the fatalities work but the glitches remain, the pit 1 doesn't scroll down to the bottom of the pit when the fatality is done, a similar glitch occurs with the bell tower fatality too. the pit 2 fatality is misaligned when the impact occurs here are some screens I took of these glitcheshttp://img.photobucket.com/albums/v77/BabyGatomon/Screenshots/mugen004.pngpit 1 glitch as you can see the scrolling stops here when the fatality is executedhttp://img.photobucket.com/albums/v77/BabyGatomon/Screenshots/mugen005.pngpit 2 final scene is misalignedhttp://img.photobucket.com/albums/v77/BabyGatomon/Screenshots/mugen006.pngBell Tower, again scrolling issue like the pit 1 only the screen doesn't scroll down showing the opponent hit the spikesmmmm try to use your old winmugen screenpack too, but check in the mugen.cfg, the linemotif = data/mugen1/system.deferase the mugen1 and leave the system.def, thenmotif = data/system.defEDIT: yes i found the error, the mugen 1.0 default screenpack uses localcoord = 1280,720, then that affect the camera move in the stage fatality, you need to use a localcord = 320,240 but if yu do that in the mugen 1.0 default screenpack, that will affect the whole screenpackthen you should use a low res screenpack, i think with the change of the line that i say before (motif) if should be solved, try and tell me what happenEDIT2: no wait thats not the problem, the problem is in the stages themselves, im fixing, im gonna reupload the stages when i finisg, sorryEDIT3: i fixed, im uploading in this moment, it will finish in some minutes
Spuddyman95 said, January 14, 2010, 11:02:35 pmAnything you added for soul ninja umk3? i just fixed the stages, but in soul ninja umk3 i added the ingame movelistSpoiler, click to toggle visibiltyhttp://juano.mugen-hispania.org/WIP_images/soulninjaUMK3_WIP02.JPGthe AI calling the movelist is fixed thanks to the new trigger AIlevel i also removed the normal uppercut stage fatality, now you must use the command that appear in the movelist
Spuddyman95 said, January 15, 2010, 04:27:04 pmCan you add robot smoke UMK3 the global destruction fatality?i dont like that fatality
I know this one would need alot of edits but here's Smoke's fatality from MK Deceptionhttp://www.youtube.com/watch?v=5VGApN7cTOA&feature=related
sorry for the double post but I just caught thisseems we got a size glitch with Shang Tsung, most notibly with the other MK2 chars other than Shang himself
Lucky Dearly said, January 18, 2010, 11:44:18 amsorry for the double post but I just caught thishttp://img.photobucket.com/albums/v77/BabyGatomon/Screenshots/mugen007.pngseems we got a size glitch with Shang Tsung, most notibly with the other MK2 chars other than Shang himselfi think i know whats the problem, in the separate DEF i forgotten to erase the line localcoord, you can fix it removing the line localcoord = 395,254in all the other DEF files