Comments on: Lilium Voyager 1.40 released https://clover.moe/2019/11/02/lilium-voyager-1-40-released/ Sat, 01 Jun 2024 21:53:00 +0000 hourly 1 https://wordpress.org/?v=6.6.2 By: brazzjazz https://clover.moe/2019/11/02/lilium-voyager-1-40-released/#comment-6452 Mon, 01 Feb 2021 22:39:51 +0000 https://clover.moe/?p=1225#comment-6452 Update: Some other file or setting in my installation that I later added must be causing some conflict, because Lilium works with a Vanilla installation.

]]> By: brazzjazz https://clover.moe/2019/11/02/lilium-voyager-1-40-released/#comment-6451 Mon, 01 Feb 2021 21:01:33 +0000 https://clover.moe/?p=1225#comment-6451 I’ve been trying both Lilium Voyager 1.39 and 1.40, and with OpenGL 1 I get ~ 1 fps in the menu (CPU and GPU being almost idle). When I set cl_renderer to opengl2 and restart the video, it stays with OpenGL 1. When I set OpenGL 2 in Lilium’s config file, it will give me an error message “Unsupported OpenGL version (1.1.0). OpenGL 2.0 is required.” Any ideas what could be causing this? I’m on Windows 10 x64 (GTX 970). Thanks

]]> By: ZTM https://clover.moe/2019/11/02/lilium-voyager-1-40-released/#comment-5905 Sat, 29 Feb 2020 00:40:49 +0000 https://clover.moe/?p=1225#comment-5905 In reply to frh187.

You could try using a border-less fullscreen window by opening the console using shift+escape and pasting `r_noborder 1; r_fullscreen 0; r_mode -2; vid_restart` and then pressing enter. I don’t have a Mac capable of running macOS Catalina or a retina display so I’m unable to investigate this issue.

]]> By: frh187 https://clover.moe/2019/11/02/lilium-voyager-1-40-released/#comment-5903 Thu, 27 Feb 2020 13:41:37 +0000 https://clover.moe/?p=1225#comment-5903 Great work on the Lilium voyager. I am having issues with the full screen mode on version 1.4 when playing on a retina Macbook air running macOS catalina – the game appears way off centre no matter what resolution i select with only a small portion of the game visible on screen. i therefore have to play in windowed mode or else reboot into macOS Mojave where the same issue does not occur. can you advise?

]]>