Serious sam fusion 2017 linux

I only own SSVR: TFE and SS3: BFE, and I do not own SSHD. When I try to play the game, it opens a missing executable error dialog. Manually running the game does not hook into Steam, so I am asked to enter my login credentials (what login credentials?) before I can continue, which means I can’t play. Changing the launch options in the Steam properties for the game does not seem to help.

A side note, which is not as critical, it defaults to using OpenGL in VR mode on Linux, when it should default to Vulkan.

If you own only SSVR:TFE, not SSHD:TFE, then you get a working VR launch option, and a broken flat launch option. We are working on removing that broken flat launch option for VR owners, but have to wait for Valve for that. Sorry for the inconvenience.

VR version on Linux should start in Vulkan. I just double checked. Can you please post a log file where it doesn’t?

I am not trying to play the flat version, I want to play the VR version. I’m confused about these «options» though. I only get «Play Serious Sam Fusion 2017 (beta)» and «Play Moddable» as pictured here [imgur.com] . Am I supposed to see flat and VR versions here? Maybe this is because I don’t own the flat version that the config is messed up.

Whichever I pick, I get the error dialog saying that there is a missing executable.

VR version on Linux should start in Vulkan. I just double checked. Can you please post a log file where it doesn’t?

I am willing to provide more information with anything you need to help fix this.

Edit: In addition, this does not show in my VR category in my Steam library.

Ah, that. Well, it’s meant to be launched from Steam. Especially the VR version. In general, it is best to run all VR games from inside the VR headset. There are various Steam client bugs that show up if you launch a VR game from flat client, or from shell.

Actually, Serious Sam VR: The First Encounter can be run from outside Steam with no issues, as long as Steam is running. It hooks into Steam so that my status changes/voice works/invites work/achievements work, and I don’t get a sign in screen when I progress past the start screen.

But really, I want to launch it from Steam, but if I do, it gives a missing executable error (EDIT: it now gives an invalid app configuration instead of missing executable). I wouldn’t care that much if launching outside of Steam was entirely impossible, if only I could run the game the proper way. The issue here is that I cannot launch the game from Steam, everything else is not a big deal.

Please restart Steam client, it should work from Steam now.

Launching from outside Steam is possible but will always launch the first launch option. Launching VR game outside of VR will confuse Steam client to think it is running even after exit, until you kill the SteamVR process started by the game, etc.

It still does not work for me, though now it shows in the VR section. Just give the invalid app configuration error.

I noticed that this uses DLC to determine what you can play. With what I own, what am I supposed to see there? Right now, I have one option, which is installed, called «Serious Sam Fusion 2017: The First Encounter.» Is that right?

Edit: To be more certain, I verified the files and uninstalled/reinstalled after restarting the Steam client, with neither making a difference.

Источник

Serious sam fusion 2017 linux

Fusion is a central hub for your Serious Sam fun. It merges several Serious Sam games in a single interface allowing you to switch through them seamlessly, without exiting to desktop. It automatically links all of the supported SS games you own, so all you need to do is jump in and enjoy them.
Fusion also gives you access to a lot of cool new features like common workshop, cross-game mods, 64bit executables, Vulkan API support, multi-threaded rendering, etc.

VR and HD versions of Serious Sam games are separate. You should only buy the VR versions if you own a VR headset. If you don’t, get those HD versions instead. Fusion 2017 will appear in your library automatically, regardless of the version you purchased.

Unfortunately, Serious Sam 2 is too old to port it to the Fusion engine. It used completely different lighting, different shader system, completely different scripting, many obsolete entities and code snippets, etc. Porting SS2 to the Fusion engine would take about as long as making a new game from scratch.

Along with getting access to your Serious Sam games within a single interface, you will be getting tons advanced features like split screen support, proper multi monitor support, and a new “light-weight” save system that allows you to save your progress much faster. Perhaps the biggest benefit of using Fusion is experienced in multiplayer, as this new hub allows you to play cross-platform on Windows, Steam OS, Mac and Linux. VR players can even join in on some multiplayer fun with their “flat” counterparts.

You don’t need to have the stand-alone versions of supported Serious Sam games installed if you want to play them, so go ahead and uninstall them since they will be available and playable in Fusion.

No. But on the bright side, now you absolutely NEED to to play Serious Sam again. You’ll thank us later.

Please locate the Sam2017.log file. It should be in the folder “ \steamapps\common\Serious Sam Fusion 2017\Log\”. It is just a text file, so you can open it with any text editor. Please copy the content and paste it in a new post on this forum.
If the forum says the file is too long, please use Pastebin and post the link to the paste in the forums.

Источник

Serious Sam Fusion 2017 Windows, Mac, Linux game

Serious Sam Fusion 2017

Croteam | Devolver Digital | Released 2017

Serious Sam Fusion 2017 is a fresh build of Serious Sam games developed by Croteam!

The best part? If you own a Serious Sam game listed below you’ll be getting a Serious Sam Fusion 2017 version of that game for FREE!

Serious Sam Fusion 2017 is also a central hub for existing (and upcoming) Serious Sam games that will enable seamless integration of new engine features, patches and upgrades.

Games available in Serious Sam Fusion 2017

Serious Sam HD: The First Encounter — now available!
Serious Sam HD: The Second Encounter — now available!
Serious Sam 3: BFE (coming soon)
VR versions of all games will be a part of Serious Sam Fusion 2017, too!

Please keep in mind that this release of Serious Sam Fusion 2017 is currently in beta; you’ll experience extreme violence, inexplicable joy, some sadness, sometimes all at once, and, how shall we put it. eeerm, occasional bugs. Please use the official discussions page to let us know. Thank you!

What does it do?

Serious Sam Fusion 2017 will enable a lot of cool new features, like a common workshop and cross-game mods. All of the games can be started from one application, so you can jump between playing The First Encounter level to a Serious Sam 3 level and back without exiting the game. When listing game servers, servers playing TFE, TSE, SS3 – will all appear in the same list and you can vote map across games if you want. Oh, and VR games will be able to be played in multiplayer together with their flat counterparts!

Since there are so many changes and exciting new features, we’ll just go ahead a list them here as bullet points.

Источник

Serious sam fusion 2017 linux

Serious Sam Fusion 2017 (beta)

Да, не помешало бы побольше информации о видеокарте, например, и драйверах.
Ну и тот же Вулкан должен лучше работать с ядрами. Хотя многопоток с Вулканом вроде не работает ещё в Fusion.

На винде возможно воспроизвести ?
Может сама игра тупо не умеет правильно распараллеливать ядра..

говорит, что на винде всё ок, но я еще все же попробую OpenGL.

На винде возможно воспроизвести ?
Может сама игра тупо не умеет правильно распараллеливать ядра..

I’m using all four cores (at least, their usage is roughly the same). That’s using Vulkan (desktop) and OpenGL (laptop, 4 threads). I have the game locked at 60 fps. Weirdly the game seems to use more CPU (on one CPU only) on the pause screen than when the game is actually going.

*Cue the dev coming in and confirming it’s single core only. *

EDIT more info:
Mint 17.3 x64 all around. Intel.

I’m using all four cores (at least, their usage is roughly the same). That’s using Vulkan (desktop) and OpenGL (laptop, 4 threads). I have the game locked at 60 fps. Weirdly the game seems to use more CPU on the pause screen than when the game is actually going.

*Cue the dev coming in and confirming it’s single core only. *

EDIT more info:
Mint 17.3 x64 all around. Intel.

Easter egg with OGL, when doing a screenshot — break the lighting. http://funkyimg.com/i/2vqVB.png

1. HD is not needed in multi-threaded mode

2. Or HD is not able in multi-threaded mode, because the game is old and its just ported from the old game engine.. Perhaps the developers do not want to improve the performance of the cores.

I think @AlenL should answer our question..

Easter egg with OGL, when doing a screenshot — break the lighting. http://funkyimg.com/i/2vqVB.png

1. HD is not needed in multi-threaded mode

2. Or HD is not able in multi-threaded mode, because the game is old and its just ported from the old game engine.. Perhaps the developers do not want to improve the performance of the cores.

I think @AlenL should answer our question..

Источник

Serious sam fusion 2017 linux

Good day, I will be running a Seriously Casual dedicated server instance simular to the SS3 Seriously Casual instance. Besides the boiler plate runSam2017_DedicatedServer.sh missing (works fine with the SS3 script adapted to fit and making sure the DS finds steamclient.so), I get this crash on map change:

TRC: Changing over to Content/SeriousSamHD/Levels/00_Egypt/0_02_SandCanyon.wld
LOG: Timestamp: 2017/03/23 12:41:32
LOG: Changing to ‘Content/SeriousSamHD/Levels/00_Egypt/0_02_SandCanyon.wld’.
LOG: World deleted in 0.01(0.01)sec.
LOG: World stopped in 0.01sec.
LOG: Process memory: 572 MB
INF: Crash! (Segmentation fault)
DBG:
DBG: //=====================================================
DBG: Report generated at: unsupported unsupported
DBG: Version: $Version: SE2017_PC_dev; SeriousSam2017_Executables-Linux-Final; 295848 2017-03-17 15:41:53 @builderl01; Linux-x64-Static-Final-DedServer$
DBG: Build type: Linux-x64-Static-Final-DedServer
DBG: Dump type: Crash
DBG:
DBG: Received signal 11 (Segmentation fault).
DBG:
DBG: Dumping registers:
DBG: RAX:0000000000000000
DBG: RBX:00007FD4DF0E3050
DBG: RCX:00007FD4E14E70E0
DBG: RDX:FFFFFFFFFFFFFFFF
DBG: RSP:00007FD4E0188BA8
DBG: RBP:00007FD4CD695610
DBG:
DBG: RSI:00007FD4CD695610
DBG: RDI:00007FD4DF068010
DBG: R08:00007FD4E15BF010
DBG: R09:FFFFFFFFFFFFFFFF
DBG: R10:0000000000002157
DBG: R11:0000000000000B1D
DBG: R12:0000000000000000
DBG: R13:00007FD4DF068010
DBG:
DBG: R14:0000000000000001
DBG: R15:0000000000000000
DBG:
DBG:
DBG: RIP:0000000001B2DFBA
DBG: Flags:00000000
DBG:
DBG: Dumping stack back trace:
DBG: 0000000001B2DFBA 00000001 $adr: «./Bin/x64/Sam2017_DedicatedServer» 0001:000000000172DFBA
DBG: 0000000001B2DFBA 00000001 $adr: «./Bin/x64/Sam2017_DedicatedServer» 0001:000000000172DFBA
DBG: 00000000018B562F 00000001 $adr: «./Bin/x64/Sam2017_DedicatedServer» 0001:00000000014B562F
DBG: 0000000001629755 00000001 $adr: «./Bin/x64/Sam2017_DedicatedServer» 0001:0000000001229755
DBG: 00000000017B9122 00000001 $adr: «./Bin/x64/Sam2017_DedicatedServer» 0001:00000000013B9122
DBG: 00000000017C87E8 00000001 $adr: «./Bin/x64/Sam2017_DedicatedServer» 0001:00000000013C87E8
DBG: 00000000019A4D0D 00000001 $adr: «./Bin/x64/Sam2017_DedicatedServer» 0001:00000000015A4D0D
DBG: 0000000001BF32B4 00000001 $adr: «./Bin/x64/Sam2017_DedicatedServer» 0001:00000000017F32B4
DBG: 0000000001BAEE41 00000001 $adr: «./Bin/x64/Sam2017_DedicatedServer» 0001:00000000017AEE41
DBG: 0000000001C1EF4D 00000001 $adr: «./Bin/x64/Sam2017_DedicatedServer» 0001:000000000181EF4D
DBG: 00007FD4E1270444 00000001 $adr: «/lib64/libpthread.so.0» 0001:0000000000007444
DBG: 00007FD4E0AB412D 00000001 $adr: «/lib64/libc.so.6» 0001:00000000000E912D
DBG: 00007FD4E1270444 00000001 $adr: «/lib64/libpthread.so.0» 0001:0000000000007444
DBG:
DBG: //=====================================================
DBG:
DBG:
Segmentation fault

I can confirm that, tested on Ubuntu 14.04 and 16.10. The server crashes whenever the last player leaves or there is a map change.

Источник