bylaws commented 2 years ago

Is there an existing issue for this?

[X] I have searched the existing issues

Tested Build

Edge-8

Android Version

13

SoC type

Snapdragon

Device GSMArena link

https://www.gsmarena.com/xiaomi_12-11285.php

Game Behaviour

Some Kingdoms boot depending on Dock mode. Docked on for Metro i.e.
Performance differs per kingdom/zone.
Some major graphical issues.
Best run with 6 executor slot count and readback hack
Cap kingdom almost entirely unplayable

https://user-images.githubusercontent.com/81425424/197383911-0357294a-af56-402c-b86a-b8bdad4cd6af.mp4

Is Log Level is set to 'Info'?

[X] Yes

Log file

emulation.txt

E121191HOS-13Signal: Segmentation fault @ 0x5F5DD4E (PC: 0x7BDFA78144) (SVC: SvcWaitSynchronization)
Stack Trace:
* 0x7BDFA78144 (from libskyline.so)
* 0x7BDFA77820 (skyline::kernel::svc::WaitSynchronization(skyline::DeviceState const&) from libskyline.so)
* 0x7BDFA5DC64 (skyline::nce::NCE::SvcHandler(unsigned short, skyline::nce::ThreadContext*) from libskyline.so)
* 0x802C6A0B8 (from sdk.nso.patch)
* 0x800AC3D64 (nn::atk::detail::driver::SoundThread::Run(void*) from main.nso)
* 0x800AD11F4 (nn::atk::detail::fnd::Thread::ThreadMain::Run(void*) from main.nso)
* 0x802CF68A8 (from sdk.nso)
* 0x802CFA958 (from sdk.nso)
* 0x802CFA8D8 (from sdk.nso)

Thepowa753 commented 2 years ago

Build 1067: Audio works :heart:

Thepowa753 commented 2 years ago

Build 1083:

[x] All text is now showing
[x] Passes the lock after the black screen when pressing play
[ ] Cinematic graphics is glitchy
[ ] 7 FPS
[ ] Crash after 1 minute of cinematic

I'm updating the logs: odyssey_log.zip

Thepowa753 commented 2 years ago

Build 1090:

:x: Game not booting (locked with black screen 0 fps) Screen record:

https://user-images.githubusercontent.com/44495483/167793930-6aad2cbb-34ba-4087-aaaf-872eceab0ea5.mp4

Log: emulation.log

ghost commented 2 years ago

Build 1193: Graphics look more correct and game is booting again but intro cutscene doesn't appear (regression)

ghost commented 2 years ago

Change the tag to "Ingame"

Technobird003 commented 2 years ago

For me it starts until the Intro scene... after that it crashes

Marryjam commented 2 years ago

GPU not supported problem

michasrutek commented 2 years ago

Compilation 1345 Android version: 10 SoC type: MediaTek Helio G90t Device: Redmi Note 8 Pro Game starts normally expect completely broken text up to moment when intro cutscene starts, screen turns black, audio works up to a moment when fireball was lauched to Mario when game nearly completely freeze, less than a second of audio for a minute or two waiting Super Mario Odyssey.zip

navarretejoel0323 commented 2 years ago

can i pls get the link of the game

Thepowa753 commented 2 years ago

can i pls get the link of the game

Skyline is an emulator, not a game collector... You should dump your own physical copy (or search on google)

Angel69968 commented 2 years ago

Dónde lo descargo?

Thepowa753 commented 2 years ago

Dónde lo descargo?

Skyline is an emulator, not a game collector... You should dump your own physical copy (or search on google)

FilipSly commented 1 year ago

Build 1447

Getting serious visual bugs, audio bugs and unplayable fps during 3D rendered parts of the game, its 120fps and perfectly fine on the title screen or menus but if i go in game it all goes downhill

Video of the bugs happening during a cutscene

https://user-images.githubusercontent.com/82275709/200114600-e19b3d7f-8ac1-4f4a-9ff4-53727d77fed9.mp4

I tried both drivers, turnip and qualcomm proprietary, neither seemed to change anything.

Logs with log level info emulation.txt

Device info:

Samsung Galaxy A52s CPU: 4x ARM A78, 4x ARM A55 GPU: Adreno 642L RAM: 6GB Android11 OneUI3.1

Pikachupikachup commented 1 year ago

My game is a lot like everyone else, with the cutscene so glitchy I can’t do anything at all. I don’t know what compilation I have but I am using a google pixel 3a running Android 10. I’ll show the logs later over here from my phone.

zatvio commented 1 year ago

2006

Issue: Game is Glitched but plays just fine at 20-30ish fps. On title screen, its fine and runs smoothly at 60fps emulation.zip

Device info:

Realme X7 Max CPU: Octa-core (1x3.0 GHz Cortex-A78 & 3x2.6 GHz Cortex-A78 & 4x2.0 GHz Cortex-A55) GPU: Mali-G77 MC9 RAM: 12GB

ghost commented 1 year ago

@subhagamer The graphics look less glitched on a Qualcomm Adreno GPU.

yhak22 commented 1 year ago

latest version 1772 Lg v60 SD865 the game run smoothly but freeze or crash after some playing tried others drivers but the same. new log @Crytonics SMO.zip

MYZ6 commented 1 year ago

Build 1807 skyline-mario

Device info: Redmi K40 OS: Android 12, MIUI 13 Chipset: Qualcomm SM8250-AC Snapdragon 870 5G (7 nm) CPU: Octa-core (1x3.2 GHz Kryo 585 & 3x2.42 GHz Kryo 585 & 4x1.80 GHz Kryo 585) GPU: Adreno 650

bmcpcmb commented 1 year ago

My device is a TCL 10 5G UW. It has a SD765G with Adreno 620 and 6GB of RAM. The game barely runs (but it does). Depending on the area (I've tested only the Sand Kingdom) the game can hit from 15FPS to some pretty impressive 45-50FPS. Now then, the game crashes for some reason. Same thing with other titles like Sonic Mania (and that Chemical Plant boss glitch that won't let me finish Act 2) which, after a while, crash or freeze (most commonly crash). I seriously need to know, is this a fault of the emulator or is my device just unluckily cursed and will force the emulator to crash or something? I've seen others test games with the same setup (although a different phone) and I have not heard anything about constant crashes that won't let a man finish their games.

For example, I played from the entrance of the Sand Kingdom all the way to the boss fight in Showdown at the Inverted Pyramid. Everything went smoothly, with a low but steady and somewhat playable frame rate. After the fight and the triple moon collection cutscene, when Mario and Cappy fly off, the emulator just crashes, and won't even save my progress up to that point, forcing me to loop all the way back and have to play it all again.

Anyway, pretty long it is, sure. So to resume. Should I bash my phone with a hammer, or this happens to someone else??? A simple answer is all I need. Nobody will say anything about it. I just need to know if it's the emulator or my device. I need a certain answer from someone who has experienced the same, not just vain conjectures like "eh it's in development so it's probably that". I need something concrete enough to help me rest assured. I'm not even mad at the crashes. Just confused and worried that my phone will never be able to run Switch games without crashing.

itzsubhashis commented 1 year ago

My device is a TCL 10 5G UW. It has a SD765G with Adreno 620 and 6GB of RAM. The game barely runs (but it does). Depending on the area (I've tested only the Sand Kingdom) the game can hit from 15FPS to some pretty impressive 45-50FPS. Now then, the game crashes for some reason. Same thing with other titles like Sonic Mania (and that Chemical Plant boss glitch that won't let me finish Act 2) which, after a while, crash or freeze (most commonly crash). I seriously need to know, is this a fault of the emulator or is my device just unluckily cursed and will force the emulator to crash or something? I've seen others test games with the same setup (although a different phone) and I have not heard anything about constant crashes that won't let a man finish their games.

For example, I played from the entrance of the Sand Kingdom all the way to the boss fight in Showdown at the Inverted Pyramid. Everything went smoothly, with a low but steady and somewhat playable frame rate. After the fight and the triple moon collection cutscene, when Mario and Cappy fly off, the emulator just crashes, and won't even save my progress up to that point, forcing me to loop all the way back and have to play it all again.

Anyway, pretty long it is, sure. So to resume. Should I bash my phone with a hammer, or this happens to someone else??? A simple answer is all I need. Nobody will say anything about it. I just need to know if it's the emulator or my device. I need a certain answer from someone who has experienced the same, not just vain conjectures like "eh it's in development so it's probably that". I need something concrete enough to help me rest assured. I'm not even mad at the crashes. Just confused and worried that my phone will never be able to run Switch games without crashing.

Haha, no need to bash your phone, most probably it's the emulator, just get logs from skyline emu and attach it in the skyline emu issues section. SM Odyssey is also not working for me on the current build(#1331) which was working on the earlier builds. However, I am facing this issue in mediatek device not snapdragon.

bmcpcmb commented 1 year ago

My device is a TCL 10 5G UW. It has a SD765G with Adreno 620 and 6GB of RAM. The game barely runs (but it does). Depending on the area (I've tested only the Sand Kingdom) the game can hit from 15FPS to some pretty impressive 45-50FPS. Now then, the game crashes for some reason. Same thing with other titles like Sonic Mania (and that Chemical Plant boss glitch that won't let me finish Act 2) which, after a while, crash or freeze (most commonly crash). I seriously need to know, is this a fault of the emulator or is my device just unluckily cursed and will force the emulator to crash or something? I've seen others test games with the same setup (although a different phone) and I have not heard anything about constant crashes that won't let a man finish their games. For example, I played from the entrance of the Sand Kingdom all the way to the boss fight in Showdown at the Inverted Pyramid. Everything went smoothly, with a low but steady and somewhat playable frame rate. After the fight and the triple moon collection cutscene, when Mario and Cappy fly off, the emulator just crashes, and won't even save my progress up to that point, forcing me to loop all the way back and have to play it all again. Anyway, pretty long it is, sure. So to resume. Should I bash my phone with a hammer, or this happens to someone else??? A simple answer is all I need. Nobody will say anything about it. I just need to know if it's the emulator or my device. I need a certain answer from someone who has experienced the same, not just vain conjectures like "eh it's in development so it's probably that". I need something concrete enough to help me rest assured. I'm not even mad at the crashes. Just confused and worried that my phone will never be able to run Switch games without crashing.

Haha, no need to bash your phone, most probably it's the emulator, just get logs from skyline emu and attach it in the skyline emu issues section. SM Odyssey is also not working for me on the current build(#1331) which was working on the earlier builds. However, I am facing this issue in mediatek device not snapdragon.

Okay. Sounds good to me. I feel a little relieved. Now then, can you help me get the logs and post them in where you said, please? I want to do it.

itzsubhashis commented 1 year ago

Sure, just click on the highlighted button and get the logs file. Just create a new issue in the issues section and provide details and attach the log Screenshot_2023-02-18-22-39-43-30_fcf072b9e4efc4ce5ca3e36691a7c3c6