-
Notifications
You must be signed in to change notification settings - Fork 14
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
Game crashes on launch. #17
Comments
So couple of questions:
|
(gdb) run Thread 1 received signal SIGTRAP, Trace/breakpoint trap. |
I was kinda wondering the same thing if it was a memory issue. I do have the Render96 model pack and the HD texture pack installed. |
Do you have some sort of game controller connected? The backtrace indicates the error is related to some game controller polling functionality which is odd. Would be good if you can verify if it runs properly without the texture pack as well. |
It was totally related to the controller I had plugged in. I have no Idea why, but the PDP Afterglow Nintendo Switch controller causes the crash. It works fine with my PS4 controller, but as soon as I connect this Switch controller either via USB or Bluetooth it causes this crash. EDIT: Tested just now with default textures and the problem persists. It's still the controller causing the issue. As long as it isn't connected the game launches and runs great. |
Well, it would be interesting if you could test if this happens in sm64rt if you have the time or just on Render96ex. If it's a Render96ex problem you'll need to report the problem to their team then. Since I haven't modified a single thing or know how the controller polling works in this port, I'm gonna guess it's not really related to the renderer at all. |
I already did that. Both sm64rt and Render96ex run great now and both also crash with the controller plugged in. I only just recently started using this controller at the same time I started having issues with this Mario 64 port. I just never put it together or assumed the controller would be the issue. Thanks for helping me figure it out. I should probably report this to whoever started the sm64 port as they're probably the ones who need to know. |
Yeah, I guess you can just go backwards to sm64ex (which both projects are forked from) and even sm64pc to see if you can track down from where the problem starts from. |
Just finished testing back and the problem first appears with the Render96ex fork. sm64ex works fine with the Switch controller connected. The original sm64-port doesn't seem to have any issues either. |
What about sm64ex |
I didn't think to test that, but I will and report back. I'm not incredibly savvy with this type of thing so I may just be suspicious for no reason, but I did find it a bit strange that your version says it's forked from sm64ex and the Render96ex project says it's forked from sm64-port. Unless their project just says that on the git page and it's actually borrowing features from sm64ex, otherwise I don't see how this issue could exist in both projects especially since you've changed nothing but the rendering. |
I think that's just due to what GitHub's |
Right on. Like I said, I'm not very familiar with this so I might not understand it fully. I am on a mission now to nail this down though as it's really got me curious. |
Well, I feel good now knowing what the issue was, but it kinda bugs me to say this. I'm almost %100 certain now that whatever my issue was had to be user error. I had been building this with the msys2 command prompt myself and never had any issues before, but started to for whatever reason. Maybe I didn't have it properly set up, I'm not sure, but after building several versions of this game with and without models and textures, every version including your ray traced version works perfect with the controller using sm64pcBuilder2 to build the projects. EDIT: Well, now unfortunately I have to take that back. It seemed like it was all working OK, but after about 15 minutes of gameplay it froze and now it's back to crashing when that controller is plugged in. I'm not so sure this really has anything to do with the game or not now. Maybe that controller just has issues in general. I'm not sure what to say at this point. |
If I had to guess: maybe it has something to do with the controller connecting or disconnecting while the game is running. |
I'm downloading the ex nightly build and I'm gonna play it for a while instead of just briefly testing it. It seems it doesn't cause issue immediately. I was able to launch the Render96 rt build several times and played it for about 15 minutes before it went haywire. I should probably mention that it didn't just randomly freeze. It happened when I increased the draw distance. As soon as I hit apply is when it froze. OK, I just finished building sm64ex nightly and it fails to launch. It's definitely not related to your build or Render96. |
Describe the bug
Game crashes nearly every time it's launched.
To Reproduce
Launch game EXE file
Watch it hang
It crashes.
Expected behavior
Game runs normally.
Screenshots
I got a 7 minute video of me launching it over and over. Unfortunately I wasn't lucky enough to capture that elusive launch where it actually shows the logo and it runs at 1 FPS and then crashes.
https://streamable.com/kfl2ky
Desktop (please complete the following information):
DXDiag Attached
Smartphone (please complete the following information):
N/A
Additional context
I spoke with Dario on the Discord earlier about this issue and he wanted to look into it. I wish I had captured the partial load of the game where it was running so slowly before it crashed, but this is what I was able to reproduce. I think I remember this being an Issue since the release of the RT version, but it may have even been an issue with the normal R96 version.
DxDiag.txt
The text was updated successfully, but these errors were encountered: