Looks like spacesuit is already equipped by default.

Hm, looks like the only way to mine anything, is to make enough money on contracts and buy a Prospector ship.

Heh, I exited the game while being in space, and when restarted, ended up on the station, while the ship remained in space. Rather strange, and I had to "claim" the ship back through insurance.

Same thing happens on disconnects.

Quite buggy overall. During quantum drive operation it often hangs, while sound continues working. So it has to be force exited. And it's annoying that after each such hang, you need to restart from the station, and wait five minutes for recovery of the ship.

Getting to Daymar seems impossible. It always crashes somewhere in mid flight :)

Hm, looks like my current value for vm.max_map_count is 65530

cat /proc/sys/vm/max_map_count
65530

Never had such kind of issues with Wine. Is that something specific to Cry Engine?

I get this distortion in the HUD, since it's probably not handling 16:10 aspect ratio properly. Basically some elements of the HUD are outside the screen. Is there any fix for it?

After setting that max_map_count workaround - it runs quite smoothly with Mesa aco! I managed to land on Daymar and visit some hydroponics station. Looks like no one is around, not sure what to do there. Interesting to explore though :)

Hm, looks like my current value for vm.max_map_count is 65530

cat /proc/sys/vm/max_map_count
65530

Never had such kind of issues with Wine. Is that something specific to Cry Engine?

Looks like a case of "64k ought to be enough for anyone"...

From /usr/src/linux/Documentation/sysctl/vm.txt

max_map_count:

This file contains the maximum number of memory map areas a process
may have. Memory map areas are used as a side-effect of calling
malloc, directly by mmap, mprotect, and madvise, and also when loading
shared libraries.

While most applications need less than a thousand maps, certain
programs, particularly malloc debuggers, may consume lots of them,
e.g., up to one or two maps per allocation.

The default value is 65536

PS.: BTW, it's 65530 on my system as well, so "the default" seems to be more of a... guideline

They generally need to wear a spacesuit instead of a suit.
And about how to open the locker - you had to pick up the guard Kareah mission.

Is there a way to set waypoint in some area that's not a station or planet? I didn't figure out how to do it. I had to fly from one moon to another, and Crusader planet itself was obstructing direct course. But I only managed to set a waypoint on a space station in between, which wasn't the optimal way to do it.

Landing on a pad is pretty tricky. I crash half the time :)

Trying to update Start Citizen launcher, but it crahses like this:

Error: Error: spawn UNKNOWN
    at _errnoException (util.js:1024:11)
    at ChildProcess.spawn (internal/child_process.js:323:11)
    at exports.spawn (child_process.js:514:9)
    at Promise (C:\rsi_launcher\resources\app.asar\node_modules\electron-updater\out\NsisUpdater.js:263:54)
    at new Promise (<anonymous>)
    at C:\rsi_launcher\resources\app.asar\node_modules\electron-updater\out\NsisUpdater.js:261:14
    at Generator.next (<anonymous>)
From previous event:
    at NsisUpdater._spawn (C:\rsi_launcher\resources\app.asar\node_modules\electron-updater\out\NsisUpdater.js:276:7)
    at C:\rsi_launcher\resources\app.asar\node_modules\electron-updater\out\NsisUpdater.js:240:26
    at Generator.throw (<anonymous>)
    at runCallback (timers.js:789:20)
    at tryOnImmediate (timers.js:751:5)
    at processImmediate [as _immediateCallback] (timers.js:722:5)
From previous event:
    at NsisUpdater.doInstall (C:\rsi_launcher\resources\app.asar\node_modules\electron-updater\out\NsisUpdater.js:250:7)
    at C:\rsi_launcher\resources\app.asar\node_modules\electron-updater\out\BaseUpdater.js:97:29
    at Generator.next (<anonymous>)
From previous event:
    at NsisUpdater.install (C:\rsi_launcher\resources\app.asar\node_modules\electron-updater\out\BaseUpdater.js:103:7)
    at C:\rsi_launcher\resources\app.asar\node_modules\electron-updater\out\BaseUpdater.js:41:39
    at Generator.next (<anonymous>)
From previous event:
    at NsisUpdater.quitAndInstall (C:\rsi_launcher\resources\app.asar\node_modules\electron-updater\out\BaseUpdater.js:52:7)
    at EventEmitter.ipc.on (C:\rsi_launcher\resources\app.asar\src\main\auto-update.js:48:17)
    at emitOne (events.js:116:13)
    at EventEmitter.emit (events.js:211:7)
    at WebContents.<anonymous> (C:\rsi_launcher\resources\electron.asar\browser\api\web-contents.js:286:13)
    at emitTwo (events.js:126:13)
    at WebContents.emit (events.js:214:7)
[19:40:17.528] [error] Error occured auto-updating Error: spawn UNKNOWN
    at _errnoException (util.js:1024:11)
    at ChildProcess.spawn (internal/child_process.js:323:11)
    at exports.spawn (child_process.js:514:9)
    at Promise (C:\rsi_launcher\resources\app.asar\node_modules\electron-updater\out\NsisUpdater.js:263:54)
    at new Promise (<anonymous>)
    at C:\rsi_launcher\resources\app.asar\node_modules\electron-updater\out\NsisUpdater.js:261:14
    at Generator.next (<anonymous>)
From previous event:
    at NsisUpdater._spawn (C:\rsi_launcher\resources\app.asar\node_modules\electron-updater\out\NsisUpdater.js:276:7)
    at C:\rsi_launcher\resources\app.asar\node_modules\electron-updater\out\NsisUpdater.js:240:26
    at Generator.throw (<anonymous>)
    at runCallback (timers.js:789:20)
    at tryOnImmediate (timers.js:751:5)
    at processImmediate [as _immediateCallback] (timers.js:722:5)
From previous event:
    at NsisUpdater.doInstall (C:\rsi_launcher\resources\app.asar\node_modules\electron-updater\out\NsisUpdater.js:250:7)
    at C:\rsi_launcher\resources\app.asar\node_modules\electron-updater\out\BaseUpdater.js:97:29
    at Generator.next (<anonymous>)
From previous event:
    at NsisUpdater.install (C:\rsi_launcher\resources\app.asar\node_modules\electron-updater\out\BaseUpdater.js:103:7)
    at C:\rsi_launcher\resources\app.asar\node_modules\electron-updater\out\BaseUpdater.js:41:39
    at Generator.next (<anonymous>)
From previous event:
    at NsisUpdater.quitAndInstall (C:\rsi_launcher\resources\app.asar\node_modules\electron-updater\out\BaseUpdater.js:52:7)
    at EventEmitter.ipc.on (C:\rsi_launcher\resources\app.asar\src\main\auto-update.js:48:17)
    at emitOne (events.js:116:13)
    at EventEmitter.emit (events.js:211:7)
    at WebContents.<anonymous> (C:\rsi_launcher\resources\electron.asar\browser\api\web-contents.js:286:13)
    at emitTwo (events.js:126:13)
    at WebContents.emit (events.js:214:7)

Update installer has already been triggered. Quitting application.

Any idea how to work around that?

Vulkan renderer is coming!

https://www.youtube.com/watch?v=SV9_chUpDgc

Linux is mentioned in the video.

Last edited by Shmerl on 19 Nov 2021 at 12:02 am UTC

Ohh .. nice. I backed this year's ago. I wonder how it compares to Elite: Dangerous? I tried that two years ago and was a little underwhelmed ( I think I need more plot/direction, if that makes sense)

I don't think it's ready from that standpoint. They are mostly focusing on technical aspects for now. There was some plan also to develop a single player game based on their settings / engine (Squadron 42). But nothing came out so far.

The question to be answered is, will it still work after the new patch this afternoon will introduce EAC. Free fly will be starting at about the same time, so I'll be attempting my luck tonight.

I am beyond amazed that there's still life in this project.

I am beyond amazed that there's still life in this project.

Why? I see a battlefield game with about 20% positive reviews and still a 100 thousand people playing it. If that is the competition, maybe people want something completely different that isn't driven corporate agendas. It's more surprising that there is room for something that plays so slowly as SC does while all the kids seem to want every fast fast fast.

However, the good news is that everything still works. In fact, the number of technical issues is noticeably lower than last patch. And I honestly can't tell if EAC is even running. Although better this time, it still seems to underperform a bit. Maybe wine/dxvk is not liking the partial transition to the new renderer and that's what causing the high cpu loads.