Final Fantasy Type-0

[AdamN]

(08-11-2014 04:15 PM)gainsly Wrote:  

(08-11-2014 03:01 PM)AdamN Wrote:  

(08-10-2014 02:26 PM)gainsly Wrote:  I tried playing multiplayer via hamachi/tunngle/coldbird with a friend and we couldn't connect at all. The best we could do was me (the host) being able to see the mission and when joining I would get the "There was a communication error." message. We were using the latest build, v0.9.9-68-g404766c.

However, I did see the Compatibility thread and saw

Final Fantasy Type-0 [Work] Before revision v0.9.8-1390 not after (Adhoc update killing this game, waiting new update fixed)

Will netplay end up working if we just use a v0.9.8.-1390 build or do we need an older version of AdHocServer as well?

Have you tried using ppsspp builds from this post ? -snipped link-

Yeah, I've tried using those builds. Is there anything special I need to do other than drag-and-drop them into a current build folder? I know those .exe's "break" when you don't have the other main system files.

Builds I've tried using include
v0.9.9-68-g404766c
v0.9.8-1390-g6cada10
v0.9.8-1389-gc5e5ebe
irubwwu9wf6lg9b/PPSSPPWindows64.zip build that you linked.

Terminology:
Host - Person who is hosting via AdHocServer and trying to invade a mission.
Client - Person who is connecting to the AdHocServer and starting a mission.

We tried 3 different methods of connecting 5 times on each build.
1. Host slowdowns emulator when inside the Request List room. Client does slowdown after mission has started.
2. Host slowdowns emulator after invasion message sent. Client does slowdown after invasion message is received.
3. No slowdown from either player.

We've had mixed results but nothing that allowed us to play. Using the current 0.9.9-68, the one you linked (placed in current build folder) and 0.9.8-1389, it would automatically go to the communication error message very quickly. Client would never receive the invasion message.

Using the v0.9.8-1390, the client would receive the invasion message but host would get stuck on "Waiting for response from host. Please wait a moment."* I waited over two minutes on each attempt and nothing came through. [* The game interprets the "client" to be the host because it is indeed the one starting this mission.]

Later tonight we're going to try v0.9.8-1154-g3da962f because I did find a video where someone claimed netplay did indeed work using that build. They didn't use slowdown in the video, so I am a little suspect of it actually working.

Is there any methodology that we should try using? Or is placing the build exes that you linked into a current build folder the incorrect way of using them? I'm really lost at how to get this game working. I do know that I can host with hamachi and it is indeed connectable because I've played over 20 hours of MHP3rd HD on 0.9.9-68 without failure but FFT0 has yet to work on any build.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Well, this certainly is weird. I guess I need to make clarifications.
The person I play MHP3HD is from FLorida, US. I'm from MarylanD, USA.
FL Client -> MD Host, game works fine. [MHP3HD]
The guy I am trying is from MarylanD as well.
MD Client -> MD Host, game doesn't work. [FFT-0]

However, I made my girlfriend try being a client for FFT-0.
MD Client -> MD Host, game works fine. [FFT-0]
We tested the 98-1154 build and then 99-68, both worked fine. No slow down was necessary on either build.
I tested my normal internet connection and 4g to her, our ping was around 80~160.

I guess first thing is to check the latency between the guy I had problems connecting to. Other than that, I'm unsure of what our problem could be.

I never tried playing through the internet, but i never had any problem on LAN (doesn't even need to change the speed)

There are 3 possibility, big latency or lost packets, or the port already used by another program on one of the player (different games use different ports)

If the game can use the port without problem the next highest possibility is lost packets, as some games may not be able to handle too many lost packets (since adhoc multiplayer games wasn't designed for long distance communication)