Loading...
  OR  Zero-K Name:    Password:   

Forum index  > General discussion   > Help and bugs   >

Problems with the 1.5.9.3 release

13 posts, 1262 views
Post comment
Filter:    Player:  
sort
USrankDuffmaN
7 years ago
A few games after the update, I noticed that when I left a skirmish, the lobby was out of wack, no names visible on the people in the lobby, rank & whatever were still there, all the text missing, if I just join the lobby then leave it's ok.

Now when I try to start a game it freezes when it reaches 100% load, and I have to reboot.

I can go into Spring lobby and play it, and the older versions, 1.5.9.2, and 1.5.8.2.

The other thing noticed before it started crashing, was that when the commander, or a constructor, or a caretaker used the build/repair beam, it was only visible for a few seconds, then disappeared, but the build process continued with them just staring at it.


Thx

DuffmaN
+0 / -0

DErankChesti
7 years ago
Does the same happens in minimal performance settings? I have heard of that bug about suddenly disappearing nanosprays or beams. But I do not know how to fix it.
Also can you your infolog.txt to nopaste and the chobby debug log?
+0 / -0
USrankDuffmaN
7 years ago
(edited 7 years ago)
OK it does have something to do with my hardware, and the latest update process.

It will load and play in the zero-k lobby, in compatibility mode, any other video setting, and the crash happens.

In Spring Web Lobby, there is an older version of the 1.5.9.3 build (still uses the spray can construction beam), and that beam last the entire build time, and it's not running in compatibility mode, it looks like ultra graphics.

Here's the massive infolog:

[Spoiler]
+0 / -0
USrankDuffmaN
7 years ago
I found out, it's spring engine 104, in the spring web lobby you can choose which engine to use, I didnt see this option in chobby?

+0 / -0


EErankAdminAnarchid
7 years ago
quote:
In Spring Web Lobby, there is an older version of the 1.5.9.3 build (still uses the spray can construction beam), and that beam last the entire build time, and it's not running in compatibility mode, it looks like ultra graphics.

Spray can is part of the advanced graphics mode setting. Laser beam is what you get with low settings. They coexist simultaneously.
+0 / -0
USrankDuffmaN
7 years ago
I finally figured it out..I think.

My card is now too old, it works great with the 103 engine, but chobby stays up to date.

I can run the 104 engine in chobby as long as I click compatibility mode.
+0 / -0

JPrankgajop
7 years ago
104+ will likely use opengl 4.x so you may want to update your hardware or if possible, drivers
+0 / -0
USrankDuffmaN
7 years ago
Doesnt linux mint get the best driver with it's update manager? I have a laptop that windows crashed on so I loaded Linux Mint 18 Sarah, I
dont know it as well as I did windows 7.

Anyway it does work in chobby as long as I click compatibility mode, one thing I noticed though, the construction beam does stay on the entire build time, as long as Im playing, if I spectate, it goes to short beam.
+0 / -0

FIrankVermind
7 years ago
DuffMaN, I am on Linux Mint 18 on my desktop machine, using nVidia drivers. I often get drivers from one of the graphics update repositories when Mint is lagging behind, but I won't suggest anything until I know if you're on Intel or nVidia or ATI (since stuff might break).
+0 / -0
USrankDuffmaN
7 years ago
My video is and ATI Mobility Radeon HD 5870, the cpu is an intel i7.
+0 / -0

FIrankVermind
7 years ago
Are you on radeon or amdgpu? You can check by running
lsmod in the terminal and checking if either one is mentioned.

Looks like your card would be supported by the new amdgpu driver:
https://askubuntu.com/questions/756258/which-graphics-cards-are-supported-by-the-new-amdgpu-driver-in-ubuntu-16-04

Here's some discussion:
https://forums.linuxmint.com/viewtopic.php?t=225632

If you are on amdgpu, but it is an older one, adding this ppa and installing the amdgpu driver from there might help:
https://launchpad.net/~oibaf/+archive/ubuntu/graphics-drivers
If anything goes wrong, make a note on how to use the ppa-purge tool to clear the table afterwards, or just write down which packages were upgraded so you know which ones to downgrade to fix it.
+0 / -0
USrankDuffmaN
7 years ago
When it's updating it says AMD 64

lsmod
Module Size Used by
ctr 16384 3
ccm 20480 3
binfmt_misc 20480 1
nls_iso8859_1 16384 1
i2400m_usb 36864 0
i2400m 106496 1 i2400m_usb
wimax 36864 1 i2400m
uvcvideo 90112 0
videobuf2_vmalloc 16384 1 uvcvideo
videobuf2_memops 16384 1 videobuf2_vmalloc
videobuf2_v4l2 28672 1 uvcvideo
videobuf2_core 36864 2 uvcvideo,videobuf2_v4l2
v4l2_common 16384 1 videobuf2_v4l2
videodev 176128 4 uvcvideo,v4l2_common,videobuf2_core,videobuf2_v4l2
arc4 16384 2
media 24576 2 uvcvideo,videodev
iwldvm 233472 0
snd_hda_codec_realtek 81920 1
snd_hda_codec_generic 77824 1 snd_hda_codec_realtek
snd_hda_codec_hdmi 53248 1
mac80211 737280 1 iwldvm
snd_hda_intel 36864 5
snd_hda_codec 135168 4 snd_hda_codec_realtek,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_intel
snd_hda_core 73728 5 snd_hda_codec_realtek,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_codec,snd_hda_intel
snd_hwdep 16384 1 snd_hda_codec
snd_pcm 106496 4 snd_hda_codec_hdmi,snd_hda_codec,snd_hda_intel,snd_hda_core
snd_seq_midi 16384 0
snd_seq_midi_event 16384 1 snd_seq_midi
snd_rawmidi 32768 1 snd_seq_midi
snd_seq 69632 2 snd_seq_midi_event,snd_seq_midi
coretemp 16384 0
iwlwifi 200704 1 iwldvm
snd_seq_device 16384 3 snd_seq,snd_rawmidi,snd_seq_midi
snd_timer 32768 2 snd_pcm,snd_seq
kvm_intel 172032 0
snd 81920 21 snd_hda_codec_realtek,snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_pcm,snd_seq,snd_rawmidi,snd_hda_codec_generic,snd_hda_codec,snd_hda_intel,snd_seq_device
cfg80211 565248 3 iwlwifi,mac80211,iwldvm
soundcore 16384 1 snd
kvm 536576 1 kvm_intel
irqbypass 16384 1 kvm
mei_me 36864 0
mei 98304 1 mei_me
lpc_ich 24576 0
joydev 20480 0
input_leds 16384 0
shpchp 36864 0
serio_raw 16384 0
i7core_edac 24576 0
edac_core 53248 1 i7core_edac
mac_hid 16384 0
asus_laptop 32768 0
sparse_keymap 16384 1 asus_laptop
input_polldev 16384 1 asus_laptop
parport_pc 32768 0
ppdev 20480 0
lp 20480 0
parport 49152 3 lp,ppdev,parport_pc
autofs4 40960 2
btrfs 987136 0
xor 24576 1 btrfs
raid6_pq 102400 1 btrfs
drbg 32768 1
ansi_cprng 16384 0
xts 16384 1
gf128mul 16384 1 xts
algif_skcipher 20480 0
af_alg 16384 1 algif_skcipher
dm_crypt 28672 1
dm_mirror 24576 0
dm_region_hash 24576 1 dm_mirror
dm_log 20480 2 dm_region_hash,dm_mirror
hid_generic 16384 0
usbhid 49152 0
hid 118784 2 hid_generic,usbhid
amdkfd 122880 1
amd_iommu_v2 20480 1 amdkfd
radeon 1511424 3
i2c_algo_bit 16384 1 radeon
ttm 98304 1 radeon
drm_kms_helper 139264 1 radeon
syscopyarea 16384 1 drm_kms_helper
sysfillrect 16384 1 drm_kms_helper
sysimgblt 16384 1 drm_kms_helper
psmouse 126976 0
fb_sys_fops 16384 1 drm_kms_helper
ahci 36864 3
drm 360448 6 ttm,drm_kms_helper,radeon
libahci 32768 1 ahci
atl1c 49152 0
fjes 28672 0
video 40960 1 asus_laptop
+0 / -0
USrankDuffmaN
7 years ago
I have a weird graphic problem, not real bad. In chobby in the current version of ZK I have no shadows, everything else looks great.

In an older version of ZK 1.5.8.2, played through weblobby, I have shadows, but the weird part there is, some of the explosions, and the shield bot that emits a pulse is rendered as an expanding white sphere.
+0 / -0