Throw Issue

[ade2004]

I'm trying to mix SF1 and SF2 nes together together:


But anytime an SF 2 nes char throws an SF1 char they fall through the floor and won't be seen again unless i restart the round


how can this be fixed?

FYI the SF1 chars do NOT have throws.

[XGargoyle]

- Custom states are not compatible
- Bad coding?

[Bastard Mami]

If getting a character from a full game to fit into regular mugen si pretty annoying, I guess that getting a character from a full game in another full game is at least 2 times harder.

[ade2004]

Yeah way to contribute

[BC]

looks like a velocity/physics || position problem.

[Byakko]

More like a custom state problem, as XGargoyle said, not compatible, especially since Adon seems to be stuck in a sprite that isn't him being thrown.

Yeah way to contribute

They're telling you what the problem is, and they're also telling you that there's very little chance mixing two full games will ever work. If you can't be bothered enough to show the code for the throws and the custom states used, just learn to code and fix it yourself.

[BC]

not compatible, especially since Adon seems to be stuck in a sprite that isn't him being thrown.

i guess he could ask for some help with sprite editing in the requests section or try editing himself, they dont look too detailed the sprites, well actually ryu doesnt lol i could prob draw that, just not adon 

More like a custom state problem, as XGargoyle said

well kinda what i meant, you have to note the physics of p2 in the custom state right? and velsets target bind. im no expert in throw coding but that looks like a posset problem in the custom state.


or basically

- Bad coding?

[Byakko]

i guess he could ask for some help with sprite editing in the requests section or try editing himself, they dont look too detailed the sprites, well actually ryu doesnt lol i could prob draw that, just not adon

WTF, do you understand anything of what we're talking about ? This has nothing to do with the quality of the sprite edit. Also of course the sprites aren't detailed, Ryu is supposed to look like a NES game and Adon is from SF1 which is well over 20 year old.

well kinda what i meant, you have to note the physics of p2 in the custom state right? and velsets target bind. im no expert in throw coding but that looks like a posset problem in the custom state.

Not physics, no. From what I can guess with these shots, Adon gets thrown, he's put in a custom state, he's asked to play an animation that he... doesn't have. So he's stuck on the animation he was in. And the custom state probably has a changestate triggered by an animelem or animtime, maybe even by checking the anim number, so obviously Adon never fulfils these conditions. Thus it never changes.
Well, that'd be my guess anyway. If it was a problem with physics or velocities, the bug would occur on the chars from the same game as well, and AFAIK, it doesn't.

It's probably not bad coding since both games are supposed to work when left on their own, the bug would happen with everyone. It's simply not compatible.

[ade2004]

you see i cant code, I dont intend to release this as a full game, just for my own pleasure, so how do i find these custom states you speak off, i know its in one of the cns, or cmd..........

[Byakko]

You don't, and you don't try to mix two games that were never made to work together I'm sorry but if you have no intention of learning how to code, you're not going to make it through. You'd need to learn to read through the CNS to find the custom state and the animation it uses, read through the SFF to check the sprites you want, read and write in the AIR to give him the animation he's missing...
And before you ask, guiding you through it will be more trouble than it's worth. Like [E] (Byakko Vazquez) said, it's already hard enough in normal time, it's already hard enough in one full game, but it's twice harder between two full games.

[BC]

WTF, do you understand anything of what we're talking about ? This has nothing to do with the quality of the sprite edit. Also of course the sprites aren't detailed, Ryu is supposed to look like a NES game and Adon is from SF1 which is well over 20 year old.

you was miss understanding what i was trying to say you said,

especially since Adon seems to be stuck in a sprite that isn't him being thrown.

what i was suggesting is a sprite edit for adon to have a get thrown sprites.
because he said sf1 characters dont have them, also refering to the quality of the sprites i was speaking about it shouldnt be too hard to edit them because they arent that detailed.(meaning obv its harder to edit more detailed sprites)


i still think its a position problem even if its stuck in a frame that isnt get thrown. usually with physics = N and poor positioning thats what happens when trying to get them on ground level

obviously not denying a changestate problem.......

[Cyanide]

i still think its a position problem even if its stuck in a frame that isnt get thrown. usually with physics = N and poor positioning thats what happens when trying to get them on ground level, physics = A is auto gravity.

It will be an issue with the state, unlikely to be an issue with the physics. If it works correctly vs an sf2 character then obviously the sf2 character checks on something specific to make this work. If it's unable to check that specific thing, then it breaks. Problem is with the sf2 characters throw states, I don't actually think it's with the custom state because the thrower has the issue, not the throwee.

[BC]

hmm ok, cant argue with that, i guess i thought it was pos problem because a move i coded along time ago when i was starting out didnt have the right position and the physics were neutral, and because the pos was too low he was standing lower than the floor, thats why when i saw adon standing lower than the floor i thought of that.

[Cyanide]

But anytime an SF 2 nes char throws an SF1 char they fall through the floor and won't be seen again unless i restart the round

He wasn't standing on the floor, he was busy falling through it to infinity.

[BC]

  lol im tired i guess im not reading the right things i should

[Byakko]

what i was suggesting is a sprite edit for adon to have a get thrown sprites.

I understood what you said and it has nothing to do with the problem at hand. The problem isn't that Adon is missing "get thrown" sprites, it's that the animation currently displayed is not that of "getting thrown". You did not understand what the hell this topic is about.

because he said sf1 characters dont have them

No, he did not say they "don't HAVE them", the problem is that they are not displayed.
Get a clue.

still think its a position problem even if its stuck in a frame that isnt get thrown.

If it was that, it would happen with everyone, not just the chars from the opposite game, like I said.

[Cyanide]

From the first post for anyone who happens to have missed it.

FYI the SF1 chars do NOT have throws.

[Byakko]

The fact that Adon doesn't actually have a "get thrown" sprite has no influence over the animation currently displayed, since the problem would be that the animation *number* (and how it's setup - number of frames and duration) doesn't match the triggers that are probably used ; the actual sprites used in the animation don't matter. A quick fix would be to make an animation that is empty or using other random sprites, but that would fit the SF2NES throw standard. That would be enough to have the triggers work properly, since they don't look at the sprites themselves.
So it's not the same if we're talking about fixing the "disappear through the floor forever" bug or if we just want to make it look nice after the bug is fixed.

[BC]

FYI the SF1 chars do NOT have throws.

No, he did not say they "don't HAVE them", the problem is that they are not displayed.
Get a clue.

looks like you was the one with no clue refering to that quote above


and why such attitude you need prozac or something, or a good night sleep 
all this code going to ya head

[Bastard Mami]

Actually is pretty easy to get angry when he is tring to help the guy above and you give false information instead.