srs008
Published
anti-cheat triggered by old version of GE proton, different but i suspect similar errors triggered by latest proton, and experimental.
-dx11
it will render the first "video" for long enough to give us a image before erroring out and freezing.
almost insta-crashed
so i tried glorious eggroll, i tried proton experimental, 7.0-4, 6.3-8... i could not find any config files to try deleting, so it's not even making it that far. making the game actually worse then when i last tried a while ago. note i'm dual screen at different resolutions and refresh rates, so that could be it.
game felt sluggish responding to input, and the game seemed to suffer cache loading issues
sony dualshock 4 controller (on usb) causes game to crash to desktop instantly.
at 1080p, game should play better then it does. certainly feels juddery.
(crash when controller connected and menu used)
game seemed to have input lag. not overly familiar with it, so maybe i just forgot after years...
between the input "sludge" and the dramatic FPS drops when under heavy rotation. there is clearly performance issues still occuring. that said, it's running a LOT better then the 5fps it managed a few years ago
DXVK_FRAME_RATE=60 DXVK_ASYNC=1 %command%
game executable fails to stop running after exit, requiring intervention to close it off.
without the commandline, game stutters fairly often for little to no reason.
it only needs to change that refresh rate based on the monitor's max. like mine is 70. game ran perfectly for the few minutes i played it. with no indications of anything particularly problematic occuring. e.g it detected 400+ players online, and moderate nat, which is exactly what windows detected last i bothered playing two years ago. i do not feel that the game has any abnormality except in closing itself down, likely a bad address read/write as it closes. probably in handing the device/s back to windows.
MUST have shader preload on. otherwise, my zombies in space land matches (3 solo's) worked 100%.
during initial scene loading (notably zombie "scene" main menu) it's a little slow to load then windows. it's a little messed up during this. unsure if this is BECAUSE the scene is always normally loaded first, or something else. either way. not a problem itself, just noteworthy.
shader preload is REQUIRED for good gameplay, but is abnormally slow (4fps, around half an hour i'd guess, I alttabbed out instead of waiting for it to do it's thing, and tabbed back later)
shader preload normally smoothes the game, but is not too much a issue to leave off in windows. it's REQUIRED in linux (manjaro?) otherwise you get nasty stutters and fps drops.
I only played zombies, don't care about multiplayer in general, but since the functionality is technically multiplayer, i marked as such. it loaded my profile, and everything except GAME settings off their servers no hitch.
Video is important for this game
due to missing video decoders, there is NO video clips under standard proton. I actually have no idea about audio, because i was not using the headphones on the machine at the time.
i played this on my brother's 2400g system, they are nearly identical, so these specs still work.
I did not bother connecting headphones, i was actually just seeing how one of the heavier games in my library ran under a fresh manjaro install. (there was/is concern the fan curve on the gpu may be stuck in idle...)
barring video, it ran fine, however, the fact that video decoders is not included in proton is not a big issue, however, we are at a point where steam should seriously enable winetricks to launch from steam itself to configure each game as needed. you know, inputting game path automatically.
proton 6.5-GE-1 GloriousEggroll
Renamed eg2.exe (launcher directory) to eg2launcher.exe (it don't matter what you call it, or delete it if you like) copied evilgenius_vulkan.exe from the bin folder to the launcher directory. renamed it to eg2.exe. thanks to the people in the discussions for pointing this out, i'd give credit, but i had to use search, so i've got no idea. running maxed out. seems perfectly fine
when i was searching, someone seemed to find a way to make the launcher work, seemed to be some updated files wine side? just letting people who have not seen it know, it exists so they can search it themselves. (i think it was kernel32.dll related if my memory is not playing tricks on me)
game is borked.
tried it running both my slightly outdated glorious eggroll (6.1 i think), and latest steam proton experimental. neither version would boot. also tried looking for some cracks, do NOT use the zippy share link, virus total did not like it, (not as bad as a reloaded version though, half the list lit up) I tried a quick google search, and i kept coming back on malware riddled steam APIs supposedly. I did try just copying the exe's and praying, no luck. and yes, i know a lot of it is false flagging. i'm just not keen on rolling the dice with my steam profile, and pretty well running manjaro install. i'll point out the issue seems to be in the steam_api.dll, as every crack replaces this, and the exes keep scanning as safe. but since all the cracked dlls show up as malware, i've avoided them. yep, i'm being overly cautious. some one wants to FIND and assemble a safe one though, great. just make sure virus total does not light up.
first launch took so long, that i actually spent around three hours trying to figure out why the game would not start. (unresponsive) trying everything other then simply waiting like 10 minutes for it to start. might be the "upnp" thing for anyone interested. barring this, the game seems to run perfectly fine. fresh character, level 8 when i left the game just now for a rough timeframe of this session
if that was the upnp thing, default should be off (commandline default maybe on proton?)
had some sort of driver issue, took two days to find the issue, amd pro... just remove the junk.
AMD_VULKAN_ICD=RADV VKD3D_CONFIG=pipeline_library_app_cache RADV_DEBUG=nodcc,nohiz %command%
used the steamdeck modified ini's, also did the max mem setting
seems to be suffering momentary audio drops, suspect game's over demanding the cpu and choking out pipewire via displayport
graphics could be better, fair amount of LOD texture load, might be steamdeck inis when i think about it. still early game, so i've not seen the world map yet. but it's holding 60fps on2k res downscaled to 720p. I also think my drivers are being funky with the game, there's a sort of halo/shimmer artifacting going on, notably the first piece of gameplay as the camera whirls a bit with fig for the wiggenweld potion, there's some notable artifact ghosting. considering the suspicion of heat damage previously, and choatic installs of gpu "drivers" for linux. i just don't know what to blame. so i'm noting it. despite not thinking it's more then a me issue.
needs esync off... or it will quickly crash, likely memory leak
if i had to guess, I think origin messes up the fullscreen initialization. this is the only game that minimises itself sometimes on startup, or has any sort of focus issues. not a big deal, once made the focus though
turn off steam controller interception or whatever it's called. don't use default. etc. I did see mention though of problems on a xbox one controller, i'm running the newest xbox's controller via a xbox dongle. once "disabled". the controller worked.
runs EXACTLY the same as windows. will run for a hour, or so, and then just locks up and dies. can't really blame proton for a fault even win 10 saw...
for whatever reason, my save data did not import from the origin cloud, I ran it back when origin gave a free month for enabling two factor. I feel origin saves should be unchanged by ea play being steam vs origin. maybe i'm wrong though?
videos, and video billboards (like the start line) don't work, due to lack of media foundation
tried it under a glorious eggroll version, and the latest experimental. 5.13-6 seems to work without the crashing. other versions may work...
no cortana... (windows only) means no talking to ghosts. spiritbox just asks random questions. (beta branch 7feb)
-screen-fullscreen 0
i was forced to use "-screen-fullscreen 0", as the game would not even start. as a multimonitor system, i suspect the game had a tantrum from trying to fullscreen across both screens. game started fullscreen anyway. (probably borderless).
a while ago i got cabinet settings unlocked. so i could rotate my screen to play, i noticed that rotation does work, bit it seems the other settings are all messed up, e.g the "backglass" was trying to access a "Z:" directory in plain text. (some sort of debug failover i guess?) (only just back on linux, thought wine/proton "z:/" was the wine game directory mapping...) game plays absolutely fine otherwise. (i marked audio as fine, but mine is muted, it seemed unfair to mark something i tested down when it's likely fine)
when i tried starting the game without tinkering. (the fullscreen command) the game did not load. i've changed my memlock for a standard manjaro-gnome install. but it's still fresh, probably not even running the latest and greatest drivers yet. so no, i don't think someone who can't get the game to launch on a fresh manjaro install could enjoy a game that did not start at all.
DXVK_FRAME_RATE=60 taskset -c 0-7 %command%
crashed after a long time.
i needed to download a community "fix" (BLACK Screen & Loading screen [FIX]) steam discussion topic for those needing the files. since the steam version lacks the files to actually work out of the box.
to enjoy playing this game, one must be able to get the game to even start. once the user does the job that the devs should have done years ago. actually including working files... it ran pretty well overall. messed around eating people and tormenting the populace like a psycho for a while, and probably an hour or two in, the game crashed. does not work without the command.
launcher only
the launcher loads, but then something black appears. maybe my memory is playing tricks, but i think it was a load bar or banner for the game. it definetely has the "shield" shape on the right side. nothing else happens if given time to do anything. (it's been a few years since i played either this or sol survivor)
still borked
PROTON_NO_ESYNC=0 PROTON_NO_FSYNC=1 %command%
well, the launcher is a bit finicky, buttons seem to be a little hard to actually hit, like when a game misaligns the mouse. running the game gives a immeidiate black screen, and that's as far as it goes. i tried it standard, and i tried with launch options.
barring the keyboard mapping. it seemed to run for a while.
had a weirdness, under windows ( a while ago), i know the keyboard used the number mappings to activate abilities. that did not seem to work today. nor did using shift to run. had to play with WSAD (indicating keyboard was working), and the mouse alone.
after 102 minutes, the game crashed. I can't tell if this is normal though. felt like it was a program error, rather then a WINE/proton glitch at least.
does not even try to start, so many options, but i feel like it's something really really stupid.
video seems my best bet (nglide? have no idea how wine handles that), maybe it's dumb and wanting a cd drive to even consider starting.. although most games throw an error at least. since it's such a old game, i'm not sure a "alternative" exe even exists to test DRM.
the launcher loads, but clicking play just exits everything.
feels like the launcher attempts to load a "invalid file" as far as wine is concerned... retrovirus gets further, showing a black "bar"... i'm about to write it's report now. some sort of mini launcher appears. just by the odd shape.
barring the build menu, the game seems to run fine. then again, i started a fresh solar system.
the build menu seems to lag and judder as it opens.
i run dual screen, i'm currently watching videos on the other screen, infrequnetly jumping screen. i feel if something was to trip it up, it'd be that. it's worth noting although i played a while, it took me a bit to remember anything about the game. lots of wasted time, not much starter progress.
runs fine mostly, fresh manjaro install compared to last time, and no longer on the pitcairn
had to use BOTH commands. otherwise i just get a black screen.
PROTON_NO_ESYNC=1 PROTON_NO_FSYNC=1 %command%
to me, it felt like bloom was slowing it down a bit. then again, maybe i just left it off on my other cards to grab some fps. (pitcairn and gtx 1050)
forged alliance forever probably runs better.
ran perfectly for me, i ran it a LONG time.
ran it dual screen with firefox, audio muted, saw no load glitches, etc.
ran either the SAME as windows, or better but crashed. only played twice on my two different machines though
I played on two machines, almost identical hardware really. this one, runs a msi b350m mortar motherboard, and 1800x cpu. while the other is a gigabyte aorus b450m and a 2400g. the ram is similar, main difference is the 1800x has fancy rgb corsair vengeance at 3000mhz max, while the 2400g runs a non rgb set at 3200mhz. the other machine ran like windows does, at about 8fps with a decent size army, interestingly, I got anywhere upto 20 fps on the 1800x machine, but it crashed about halfway through the battle. probably the biggest difference between the machines, is I run dual monitors, but i'm not sure it was connected at the time. (this was actually written nearly a week later) both were run under my steam account, with one of the storm trooper mods vs evil zombies. I turned most settings down a little, but i always enable infinite body height. something like 500 or 1000 storm troopers vs 50,000 zombies. (i know, way too high, but i like the scale...)
I tolerated the stutter for testing purposes
been a while since i ran manjaro, it's a stock install, so things like increasing the file access limit has not been done. I was having stuttering issues, turning shadows off alleviated it notably, but it was still iffy. barring performance, i saw no signs of any issues, and as stated, that could be a dumb config mistake, or esync...
ran through the training, and did a bit of level 1 after exploring the ship... but the stutter was nasty
