-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
lan-play and ldn_mitm issues with Atmosphere 1.8.0 #2476
Comments
This is completely not Atmosphere related. Tool needs to be fixed, not Atmosphere. |
No?
Then contact that person and have him open up his github issue tracker for his fork, and then submit the issue where it belongs (on his fork). That's how that works. You don't file unrelated issues in other projects issue trackers. |
I was unsure if this was an Atmosphere bug not playing nice or a bug with ldn directly 🙄 Keyboard warriors everywhere. |
If you have problem with some game or app on some OS, you are going first to that OS customer support or to that app support? The same analogy |
Bug Report
[ If any section does not apply, replace its contents with "N/A". ]
[ Lines between [ ] (square brackets) should be removed before posting. ]
[ * ]
[ Note: If the bug or crash you encountered is related to; ]
[ - software used to make "backups", ]
[ - software explicitly distributed for piracy, etc ]
[ then contributors will not provide support for your issue and your issue will be closed. ]
What's the issue you encountered?
[ Describe the issue in detail and what you were doing beforehand. ]
I'm not able to play on lan-play servers using ldn_mitm. I'm not sure if this is an atmosphere issue or not, but I've used it before, but now that I'm on fw 19.0.1, it doesn't work. I show up on the lan-play website and everything as an open lobby, but get an error when trying to connect to someone or when they try to connect to me (they're also on 19.0.1).
[ Did you make any changes related to Atmosphère itself? ]
No, I'm running the latest 1.8.0 build and a fork of ldn_mitm made for newer fw.
[ If so, make sure to include details relating to what exactly you changed. ]
How can the issue be reproduced?
[ * ]
[ Include a detailed step by step process for recreating your issue. ]
Basically try to join a lan-play server with newest fw and newest atmosphere cfw. I'm using DefenderOfHyrule's ldn-mitm fork.
Crash Report
[ Crash reports can be found under
/atmosphere/crash_reports
. ][ If your issue caused Atmosphère to crash, include the crash report(s) by creating a gist and pasting the link here. ]
[ If you don't include a crash report in instances of crash related issues, we will ask you one to provide one. ]
System Firmware Version
19.0.1
[ Replace X's with system firmware version at time of crash. ]
[ You can find your firmware version in the Settings -> System, under "System Update". ]
[ If it says "Update Pending", you can clear the pending update by rebooting to Maintenance Mode. ]
Environment?
Additional context?
I'm just really wondering if this issue is due to Atmosphere or fw 19.0.1 because I know atmosphere for this fw is still in kind of earlier stages.
The text was updated successfully, but these errors were encountered: