#LUG

60 readers
4 users here now

Linux Users Group, playing StarCitizen and other games :)

founded 1 year ago
MODERATORS
1
 
 

The much awaited LUG Helper 3 has arrived!

  • RSI Launcher 2.0 support
  • Non-Lutris Wine installs
  • Proton support for Lutris installs
  • Support for multiple game installs
  • Lots of other improvements
2
 
 
  • Add Kron4ek wine runner source
  • Environment variables to support Open Wine Components umu proton in Lutris 5.17+
  • NVIDIA and AMD Environment variables for Star Citizen Vulkan renderer
  • Remove un-needed winetricks steps and DLL overrides
3
3
submitted 1 year ago* (last edited 1 year ago) by [email protected] to c/[email protected]
 
 

Some personal notes ..

Lyria Jumptown OM3 to OM2 until 225km Then turn about 30° left and down

Caliope Jumptown Raven`s Roost OM2 to OM4 until 320km Then turn right and point to Rayali Kaltak Research Outpost Fly to surface, search right of it

Bounty missions very often lead to POIs. Be it a cave or a crashsite, an NPC transport or other hidden places, labs and so on.

4
 
 

Hey, there is a problem over the last weeks, preventing wine to work with StarCitizen. When using it, we get an error message like this: 0024:err:environ:run_wineboot failed to start wineboot c00000e5

Its about compilation modes and a stack alignment issue with 32/64 bit SSE registers.

Searching for the issue, brings us to WineHQ, were a bug is already filed here:

Multiple applications fail to run if Wine is compiled with CFLAGS="-march=znver4"

In the end, it turned out to be a gcc bug. Zeb has filed a bugreport at the gcc bugzilla, to follow up, because it seems, we can not build wine with standard compilation modes anymore, until this is solved. Watch it here:

[12/13/14 Regression] i686-w64-mingw32 with -mavx512f generates AVX instructions without stack alignment

Just to let you know, when you run into the c00000e5 issue, it may be this.

Cheers, raw^^

5
2
submitted 1 year ago* (last edited 1 year ago) by [email protected] to c/[email protected]
 
 

Since something seems to be misbehaving with subscription, just throwing this quick test over to see if it's just a subscription issue

Edit: Was a configuration issue, wasn't routing json requests correctly.