Closed ryzom-pipeline closed 4 years ago
Original comment by Meelis Mägi (Bitbucket: [Meelis Mägi](https://bitbucket.org/Meelis Mägi), ).
You should check client log for 3D / OpenGL specific lines and see which resolutions it detected. You may also want to test in windowed mode. Login/char select is always windowed just so you know.
Original comment by Qian Cai (Bitbucket: deusk, GitHub: deusk).
I suspect that is due to using a secondary monitor to combine the laptop monitor to form a bigger screen. There is an external monitor connected to the laptop for non-mirror mode. I noticed even if in windowed mode after char select screen, it filled the whole either of screens with black think edges.
Original comment by Guillaume DUPUY (Bitbucket: [Guillaume DUPUY](https://bitbucket.org/Guillaume DUPUY), ).
I'll test tomorrow, I have the same CG (altho with debian sid), the issue arises when you use fullscreen with two screens (not duplicated, as "secondary" screens), right ?
Original comment by Qian Cai (Bitbucket: deusk, GitHub: deusk).
After disconnected the external monitor, it is stil coredumped in the same loading screen but with a different trace.
Stack trace of thread 26307:
#0 0x0000000000f8a4ae _ZN6NLMISC14CCDBNodeBranch4findERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE (ryzom_client_dev)
#1 0x0000000000b3e01c _Z25updateInventoryFromStreamIN11INVENTORIES30CInventoryCategoryForCharacterEEvRN6NLMISC13CBitMemStreamEPKT_b (ryzom_client_dev)
#2 0x0000000000b2fafd _Z20impulseInitInventoryRN6NLMISC13CBitMemStreamE (ryzom_client_dev)
#3 0x00000000017d4c35 _ZN27CGenericXmlMsgHeaderManager7executeERN6NLMISC13CBitMemStreamE (ryzom_client_dev)
#4 0x0000000000b50276 _ZN18CNetworkConnection20receiveNormalMessageERN6NLMISC13CBitMemStreamE (ryzom_client_dev)
#5 0x0000000000b50ca3 _ZN18CNetworkConnection14stateConnectedEv (ryzom_client_dev)
#6 0x0000000000b51038 _ZN18CNetworkConnection6updateEv (ryzom_client_dev)
#7 0x0000000000b2b617 _ZN11CNetManager6updateEv (ryzom_client_dev)
#8 0x0000000000afc7a1 _Z8mainLoopv (ryzom_client_dev)
#9 0x00000000008c1ac5 main (ryzom_client_dev)
#10 0x00007fd825d97401 __libc_start_main (libc.so.6)
#11 0x000000000093e42a _start (ryzom_client_dev)
Original comment by Guillaume DUPUY (Bitbucket: [Guillaume DUPUY](https://bitbucket.org/Guillaume DUPUY), ).
This one is intended, see https://bitbucket.org/ryzom/ryzomcore/issues/307/ryzom_client-development-build-crashes-on for more information
Original comment by Cédric Ochs (Bitbucket: [Cédric OCHS](https://bitbucket.org/Cédric OCHS), ).
Indeed, latest Ryzom Core code is not compatible with Atys data :(
Original report by Qian Cai (Bitbucket: deusk, GitHub: deusk).
Compiled the client using today's develop branch. It worked fine to login and create a character. Once clicked the "play" button, the loading screen started, and then immediately core dumped after RYZOM screen with a full progress bar. I tried both windowed and full-screen mode.
Then, I won't be login again short after saying "Error: your account is already in online state, please retry in a few seconds (2102) (ls error 2: user already online, please relog for userid 808494)".
This is the compilation flags it used.