Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add a way to connect 2 clients on one PC #7276

Closed
wants to merge 1 commit into from

Conversation

Bigpet
Copy link
Collaborator

@Bigpet Bigpet commented Jan 5, 2015

THIS IS NOT FOR MERGING

this is obviously just a hack for now to be able to test networking without needing two PCs or a VM, especially because of the inelegantly hackish global localIP value.

I also need to look at all the xyz_localIP() functions and how they would interact with this, but it seems to work for now

And it is useful for testing purposes which is why I made this pull-request as a place to discuss how to deal with this use-case as a whole.

Whether we should just add an option to add a header with port information and tunnel everything through one port or we should just port-shift everything uniformly like jpcsp does

@lightfirst
Copy link

how to make it work, does it need some special settings?

@Bigpet
Copy link
Collaborator Author

Bigpet commented Jan 6, 2015

@lightfirst Yeah, it's easiest if you make a copy in another directory and use the "notinstalled.txt" to make the settings local to that folder.

Then you can configure the two instances independently. Just enable the adhoc server in one of them (and disable in the other). It's easiest to just keep the proAdhocServer adsress to "localhost"

Enable the new option "Specify client address" in both. Then set the "change bind address" to 127.0.0.2 in one and to 127.0.0.3 in the other (basically give them two different IPs that both point to your own PC)

As you may realize this will not enable you to play with other PCs at the same time unless your PC has multiple public IPs that the other PC can reach.

@lightfirst
Copy link

Think you.

@lightfirst
Copy link

testing adhoclocal http://forums.ppsspp.org/showthread.php?tid=14313

@sum2012
Copy link
Collaborator

sum2012 commented Jan 23, 2015

@Bigpet can you try to fix conflict ?

@Bigpet
Copy link
Collaborator Author

Bigpet commented Jan 23, 2015

@sum2012 I could but like I said this is for adhoc testing purposes only and I don't want this version to get merged. So unless there's some specific adhoc changes that this would help test I don't see a reason to keep fixing merge conflicts when the actual soluion is probably something like the multicasting auto-discovery that JPCSP does.

I'm just keeping this open until we have an actual solution to this

@sum2012
Copy link
Collaborator

sum2012 commented Jan 23, 2015

@Bigpet
Copy link
Collaborator Author

Bigpet commented Jan 23, 2015

@sum2012 what is "bing address"? if he means bind address then why not just check out the branch instead of merging

if you just need builds you can use the ones I created here: http://goo.gl/qU2qVI (just *.exe files without assets, etc)

@sum2012
Copy link
Collaborator

sum2012 commented Jan 24, 2015

let me do rebase to do challenge :)

@zpzq127
Copy link

zpzq127 commented Oct 26, 2015

very good

@Cozy19
Copy link

Cozy19 commented Nov 5, 2018

Great software, works as magic with ppsspp! Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants