Search the Community
Showing results for tags 'linux'.
-
Since upgrading my gpu to an nVidia RTX 3060, I can only set v-sync via driver setting Sync to Vblank. At least I thought that's what that setting does. Enabling V-sync in TDM does nothing. I use Manjaro Linux xfce Both TDM 2.11 and 2.12
-
This post differentiates between "gratis" ("at no monetary cost") and "libre" ("with little or no restriction") per https://en.wikipedia.org/wiki/Gratis_versus_libre * A libre version of TDM could: ** Qualify TDM for an article on the LibreGameWiki *** TDM is currently listed as rejected https://libregamewiki.org/Libregamewiki:Rejected_games_list because "Media is non-commercial (under CC-BY-NC-SA 3.0). The engine is free though (modified Doom 3) (2013-10-19)" ** Qualify for software repositories like Debian *** TDM is currently listed as unsuitable https://wiki.debian.org/Games/Unsuitable#The_Dark_Mod because 1) "The gamedata is very large (2.3 GB)", and 2) "The license of the gamedata (otherwise it must go into non-free with the engine into contrib)" and links to https://svn.thedarkmod.com/publicsvn/darkmod_src/trunk/LICENSE.txt Questions: 1) tdm_installer.linux64 is 4.2 MB (unzipped), which is far from the 2.3 GB which is said to be too large. Yes, the user can use it to download data that is non-libre, but so can any web browser too. If the installer itself is completely libre, does anyone know the reason why it cannot be accepted into the Debian repository? 2) If adding the installer to the repository is not a viable solution, would it be possible to package the engine with a small and beginner friendly mission built only from libre media/gamedata into a "TDM-libre" release, and add user friendly functionality to download the 2.3 GB media/gamedata using "TDM-libre" (similar to mission downloading)? 3) Would such a "TDM-libre" release be acceptable for the Debian repository? 4) Would such a "TDM-libre" release be acceptable for LibreGameWiki? 5) Would the work be worth it? * Pros: Exposure in channels covering libre software (e.g. the LibreGameWiki). Distribution in channels allowing only libre software (e.g. the Debian repository). * Cons: The work required for the modifictions and release of "TDM-libre". Possible maintenance of "TDM-libre". I'm thinking that the wider reach may attract more volunteers to work on TDM, which may eventually make up for this work and hopefully be net positive. 6) Are there any TDM missions that are libre already today? If not, would anyone be willing to work on one to fulfill this? I'll contribute in any way I can. 7) I found the following related topics on the forum: * https://forums.thedarkmod.com/index.php?/topic/16226-graphical-installers-for-tdm/ (installing only the updater) * https://forums.thedarkmod.com/index.php?/topic/16640-problems-i-had-with-tdm-installation-on-linux-w-solutions/ (problems with installation on Linux) * https://forums.thedarkmod.com/index.php?/topic/17743-building-tdm-on-debian-8-steamos-tdm-203/ (Building TDM on Debian 8 / SteamOS) * https://forums.thedarkmod.com/index.php?/topic/18592-debian-packaging/ (Dark Radiant) ... but if there are other related previous discussions, I'd appreciate any links to them. Any thoughts or comments?
-
So I thought this is normal TDM behaviour. But then I found it's not happening on Windows. Also, when I alt-tab to desktop, the mouse is still gone, keyboard navigation is possible. Why is this happening on mission load? What is the purpose?
-
https://en.wikipedia.org/wiki/Raspberry_Pi https://www.raspberrypi.org/products/raspberry-pi-4-model-b/ https://www.raspberrypi.org/products/raspberry-pi-4-model-b/specifications/ https://www.tomshardware.com/reviews/raspberry-pi-4-b,6193.html https://www.anandtech.com/show/14581/raspberry-pi-4-launched-quad-cortex-a72-project-board-for-35-dollars https://www.raspberrypi.org/magpi-issues/MagPi83.pdf Major improvements across the "board". The quad-core Cortex-A72 with other improvements is anywhere from 25% to 300% faster than the A53 used in the Raspberry Pi 3 . No eMMC but an SSD could be used with one of the two new USB 3 ports (booting from USB or Ethernet not supported at launch, should be ready within weeks). There are three RAM options: 1 GB ($35), 2 GB ($45), 4 GB ($55). The RAM is now LPDDR4 instead of LPDDR2. The 2 GB option is a bit unnecessary IMO and seems to be the least popular, as it's the model least likely to be sold out online (as far as I can tell). Ethernet speed can actually hit close to 1 Gbps (943 Mbps), up from 237 Mbps. There is Bluetooth 5.0 support but I haven't seen any testing related to that (I would love to use it for longer range audio transmission to BT 5.0 headphones). RasPi 3 cases are incompatible due to some port shuffling. There are now two micro-HDMI ports instead of one full size HDMI, so you probably need a new cable. The device can output to two 4K displays at 30 FPS, or one 4K display at 60 FPS (presumably two 1080p displays @ 60+ FPS, and so on). Although the new GPU has 4K@60Hz H.265 decode support, actually streaming 4K and even lower resolutions on Raspbian had issues in testing, that will hopefully be resolved with updates soon. LibreELEC developers have been working with the Pi Foundation for months to support the Pi 4, and have an alpha version out. Power draw and heat are up. You'll probably want a FLIRC case or something that can provide cooling. Power is now provided using a USB Type-C cable. Due to a screw up by the Raspberry Pi Foundation, some USB-C cables don't work. But the ones that do work should be the cheapest. Can it run TDM? The CPU and GPU are much better and the potentially quadrupled RAM could be a big help. The 4 GB version can be a legitimate desktop replacement for many users, albeit with some quirks.
- 13 replies
-
- raspberry pi
- raspi
-
(and 6 more)
Tagged with:
-
Question: I was wondering if installation with Flatpak is something that is considered for the future. Motivation: I recently installed Linux Mint on my laptop and found installing DR 3.0 relatively easy (ppa), so I was thinking about figuring out how to create a package for Manjaro (which I use on my main pc), but then I thought about Flatpak. Isn't that the way forward for if you want to support multiple distro's but don't have a large group of interested Linux maintainers? Currently it is: Debian: There is a maintained package, Ubuntu: There's a ppa All other distro's: built from source While with Flatpak it seems you just need one way of installation for all distro's. I could be wrong though.
-
Clean out build from source install
datiswous posted a topic in DarkRadiant Feedback and Development
I successfully installed DR Flatpak version 3.2 (Linux). There are still files remaining from the previous build from source installation. What do I have to remove to properly uninstall? -
After a system update, where python 3.9 got updated to 3.10, I get an error with startup of DR: Error opening library: libpython3.9.so.1.0: cannot open shared object file: No such file or directory Error opening library: libgit2.so.1.2: cannot open shared object file: No such file or directory Aborted (core dumped) So I cannot start it anymore. If I would currently rebuild DR from source, would that help? I think I currently revert the update, but maybe not forever.
-
This was discussed briefly on Discord some time ago, I wanted to bring it up here as well for consistency. I don't believe it's an emergency but do consider it an important change especially later down the road, as Linux is slowly moving away from x11 with many distros already going full Wayland by default. In my case I'm pretty much waiting for KDE Plasma to fix a few bugs left with the DE before permanently switching from X11 to wayland too, I might be able to make use of it rather soon if they do. With the new input and rendering system introduced after 2.09 and available for testing in the dev builds (GLFW) we're on our way to having a Wayland compatible build of our engine. Meaning the engine is able to render natively to the WL pipeline, without having to go through the fake x11 server simulated by the Wayland session for compatibility with X exclusive apps. This not only offers proper compatibility for Wayland users, but may improve performance on various fronts which was one of the goals of the new rendering framework. From what I remember @cabalistic telling me, we can't have the same engine for both x11 and Wayland: It must be compiled against different system packages to produce one version or the other. For Linux users the installer may need to offer two engine binaries in this case, or an option to pick which version you'd like to install if that's better. Other than that I understand it should be able to produce in theory, as SDL2 and GLFW both offer Wayland compatible libraries to compile the engine against. I'm not familiar with the C++ code in the slightest so I'll let the experienced developers complete this with the proper technical additions.
-
There seems to be a limitation regarding controllers (2.09 release, Linux / X11). The engine appears to not detect special mouse keys: In the Settings - Controls menu, I cannot map actions to some mouse buttons, they aren't being sensed at all. Tilting the mouse wheel sideways seems to register (as "mouse4" and "mouse5") but the forward and backward navigation keys do not. I noticed this a while ago but I don't need those buttons. However I'm trying to introduce the game to someone close: He needs to use a mouse with special buttons for gaming due to medical reasons. If non-standard mouse keys can't be mapped, I'm afraid this is a game we won't be able to enjoy. For this reason I'd like to ask if others can confirm this limitation, and if so can the engine be patched to solve it please? Thank you.
-
Hi guys, First of all (it's my 1st message), I would say thank you so much for TDM (all your work is amazing)! I love you (big fan of Thief series from first one, just discovered & playing now TDM since weeks). I want to help. I'm Arch Linux user & IT cybersecurity engineer. I would like to submit something I did try to troubleshoot. As said I use multi screens (3 screens). When running TDM (<=2.09), only main monitor display run TDM, others turns black I did try several things, using CLI, windows manager, TDM CVARS, etc... nothing worked. Then I did use nvidia-settings GUI and when running TDM i did see that X config is rewritten. 2 screens got resolution turned off (that's why they turns black). Maybe it should be a great thing to improve that behavior? improving screen parsing & using? Set an option to select a screen? I don't know what is the best solution. May I help? And how? Trying to create a new build on my own? Thanks again. S3ph
-
With the newer (and updated) version of TDM (2.07) the esc key, it's not working anymore. It seems that the key it's not recognized. I already tried on renaming my Darkmod.cfg, but the newer *.cfg created on start has the same problem. The first lines are: unbindall bind "0x00" "_impulse48" bind "ESCAPE" "togglemenu" bind "SPACE" "_moveup" ... Any idea/suggestion/faq to solve this? [I'm with Linux, Kubuntu 18.04, TDM has always worked lovely on Linux for me] [UPDATE] Maybe it's this bug on bugtracker? https://bugs.thedarkmod.com/view.php?id=4963 But I have problems only with the ESCAPE key. Any suggestion will be appreciated ?
-
im running Arch Linux, i installed this game from the AUR. i added my user in games user group as suggested in during the installation of the game, when i try to launch the game nothing happens, so i tried running is through the terminal to get some output, i got this TDM 2.07/64 #8079 (8079) linux-x86_64 Apr 12 2019 18:24:35 found interface lo - loopback found interface wlp13s0 - ( i removed the ip ) found interface wlp13s0 - ( i removed the ip ) Found Generic CPU, features: MMX SSE SSE2 SSE3 tdm using MMX & SSE & SSE2 & SSE3 for SIMD processing. no 'darkmod' directory in exe path /opt/thedarkmod, skipping WARNING: using hardcoded default base path ------ Initializing File System ------ Current search path: /opt/thedarkmod/ /opt/thedarkmod/tdm_textures_wood01.pk4 (376 files) /opt/thedarkmod/tdm_textures_window01.pk4 (389 files) /opt/thedarkmod/tdm_textures_stone_sculpted01.pk4 (463 files) /opt/thedarkmod/tdm_textures_stone_natural01.pk4 (130 files) /opt/thedarkmod/tdm_textures_stone_flat01.pk4 (295 files) /opt/thedarkmod/tdm_textures_stone_cobblestones01.pk4 (224 files) /opt/thedarkmod/tdm_textures_stone_brick01.pk4 (520 files) /opt/thedarkmod/tdm_textures_sfx01.pk4 (69 files) /opt/thedarkmod/tdm_textures_roof01.pk4 (72 files) /opt/thedarkmod/tdm_textures_plaster01.pk4 (142 files) /opt/thedarkmod/tdm_textures_paint_paper01.pk4 (63 files) /opt/thedarkmod/tdm_textures_other01.pk4 (127 files) /opt/thedarkmod/tdm_textures_nature01.pk4 (281 files) /opt/thedarkmod/tdm_textures_metal01.pk4 (496 files) /opt/thedarkmod/tdm_textures_glass01.pk4 (51 files) /opt/thedarkmod/tdm_textures_fabric01.pk4 (43 files) /opt/thedarkmod/tdm_textures_door01.pk4 (177 files) /opt/thedarkmod/tdm_textures_decals01.pk4 (461 files) /opt/thedarkmod/tdm_textures_carpet01.pk4 (92 files) /opt/thedarkmod/tdm_textures_base01.pk4 (395 files) /opt/thedarkmod/tdm_standalone.pk4 (4 files) /opt/thedarkmod/tdm_sound_vocals_decls01.pk4 (28 files) /opt/thedarkmod/tdm_sound_vocals07.pk4 (1111 files) /opt/thedarkmod/tdm_sound_vocals06.pk4 (696 files) /opt/thedarkmod/tdm_sound_vocals05.pk4 (128 files) /opt/thedarkmod/tdm_sound_vocals04.pk4 (2870 files) /opt/thedarkmod/tdm_sound_vocals03.pk4 (743 files) /opt/thedarkmod/tdm_sound_vocals02.pk4 (1299 files) /opt/thedarkmod/tdm_sound_vocals01.pk4 (82 files) /opt/thedarkmod/tdm_sound_sfx02.pk4 (605 files) /opt/thedarkmod/tdm_sound_sfx01.pk4 (948 files) /opt/thedarkmod/tdm_sound_ambient_decls01.pk4 (8 files) /opt/thedarkmod/tdm_sound_ambient03.pk4 (24 files) /opt/thedarkmod/tdm_sound_ambient02.pk4 (163 files) /opt/thedarkmod/tdm_sound_ambient01.pk4 (220 files) /opt/thedarkmod/tdm_prefabs01.pk4 (960 files) /opt/thedarkmod/tdm_player01.pk4 (125 files) /opt/thedarkmod/tdm_models_decls01.pk4 (103 files) /opt/thedarkmod/tdm_models02.pk4 (2020 files) /opt/thedarkmod/tdm_models01.pk4 (3043 files) /opt/thedarkmod/tdm_gui_credits01.pk4 (49 files) /opt/thedarkmod/tdm_gui01.pk4 (715 files) /opt/thedarkmod/tdm_fonts01.pk4 (696 files) /opt/thedarkmod/tdm_env01.pk4 (152 files) /opt/thedarkmod/tdm_defs01.pk4 (179 files) /opt/thedarkmod/tdm_base01.pk4 (197 files) /opt/thedarkmod/tdm_ai_steambots01.pk4 (24 files) /opt/thedarkmod/tdm_ai_monsters_spiders01.pk4 (82 files) /opt/thedarkmod/tdm_ai_humanoid_undead01.pk4 (50 files) /opt/thedarkmod/tdm_ai_humanoid_townsfolk01.pk4 (95 files) /opt/thedarkmod/tdm_ai_humanoid_pagans01.pk4 (10 files) /opt/thedarkmod/tdm_ai_humanoid_nobles01.pk4 (48 files) /opt/thedarkmod/tdm_ai_humanoid_mages01.pk4 (8 files) /opt/thedarkmod/tdm_ai_humanoid_heads01.pk4 (100 files) /opt/thedarkmod/tdm_ai_humanoid_guards01.pk4 (379 files) /opt/thedarkmod/tdm_ai_humanoid_females01.pk4 (172 files) /opt/thedarkmod/tdm_ai_humanoid_builders01.pk4 (91 files) /opt/thedarkmod/tdm_ai_base01.pk4 (8 files) /opt/thedarkmod/tdm_ai_animals01.pk4 (82 files) File System Initialized. -------------------------------------- Couldn't open journal files ----- Initializing Decls ----- WARNING:file materials/tdm_epi_shader_2.mtr, line 462: material 'wizard_cloth_001' previously defined at materials/tdm_epi_shader_2.mtr:366 WARNING:file materials/tdm_water.mtr, line 1189: material 'textures/particles/ripple_1' previously defined at materials/tdm_particles_ripple.mtr:1 WARNING:file skins/tdm_epi_skins.skin, line 86: skin 'steam_engine_003_off' previously defined at skins/steam_engine_003.skin:1 WARNING:file skins/tdm_epi_skins.skin, line 97: skin 'steam_engine_003_on' previously defined at skins/steam_engine_003.skin:18 ------------------------------ /proc/cpuinfo CPU frequency: 1895.94 MHz signal caught: Segmentation fault si_code 1 Trying to exit gracefully.. --------- Game Map Shutdown ---------- --------- Game Map Shutdown done ----- idRenderSystem::Shutdown() I18NLocal: Shutdown. ------------ Game Shutdown ----------- Shutdown event system ...not started -------------------------------------- About to exit with code 0
-
Hello folks, I'm a Linux (Mint) user and in games I'm using the arrow keys for movement (probably the worst kind of gamer to most of you) since I'm left-handed. On both my Linux machines (Mint 18 and 19) TDM does not recognize the arrow keys and instead sets it to zero (0x00) on each arrow key pressed, making it impossible to configure the controls to use this scheme. However, the arrow keys on the numpad (8, 4, 6 and 2) are recognized as such, which is not what I want. I've also tried different keyboards and different system layouts (since I'm using a german keyboard with the respective layout), but no success. On Windows this is no problem, as all the keys are recognized correctly. Any ideas regarding this issue?
-
I got the following error when building in Ubuntu 19.10: make[3]: Entering directory '/home/biel/games/src/DarkRadiant/plugins/script' CXX ScriptingSystem.lo CXX ScriptCommand.lo CXX ScriptModule.lo CXX ScriptMenu.lo CXX ScriptWindow.lo CXX SceneNodeBuffer.lo CXX PythonModule.lo In file included from /usr/include/pybind11/pytypes.h:12, from /usr/include/pybind11/cast.h:13, from /usr/include/pybind11/attr.h:13, from /usr/include/pybind11/pybind11.h:49, from PythonModule.h:5, from PythonModule.cpp:1: PythonModule.cpp: In static member function ‘static void script::PythonModule::RegisterToPython(const ModuleRegistrationCallback&)’: PythonModule.cpp:30:13: error: ‘dev0’ was not declared in this scope 30 | PYBIND11_VERSION_PATCH << std::endl; | ^~~~~~~~~~~~~~~~~~~~~~ make[3]: *** [Makefile:674: PythonModule.lo] Error 1 make[3]: Leaving directory '/home/biel/games/src/DarkRadiant/plugins/script' make[2]: *** [Makefile:442: all-recursive] Error 1 make[2]: Leaving directory '/home/biel/games/src/DarkRadiant/plugins' make[1]: *** [Makefile:751: all-recursive] Error 1 make[1]: Leaving directory '/home/biel/games/src/DarkRadiant' make: *** [Makefile:492: all] Error 2
-
The still ongoing Windows 10 topic sparked my curiosity why people do not just switch to Linux. But users of other OSes are also allowed to vote.
-
I've seen major slowdown of the kind i experience on menus on the darkmod also on retroarch and the root cause of that was using XWayland and was solved by compiling Wayland support in. The 'xeyes test' (xeyes move if the xeyes can capture the mouse over the window being focused over is not Wayland) fails, so apparently the context is not x11, but the command line says things like: ----- Initializing OpenGL ----- Setup X display connection dlopen(libGL.so.1) Initializing OpenGL display Using XFree86-VidModeExtension Version 2.2 Free86-VidModeExtension Activated at 1366x768 ... (much later) Fatal X Error: Major opcode of failed request: 153 Minor opcode of failed request: 18 Serial number of failed request: 74 BadValue (integer parameter out of range for operation) Couldn't exec autocommands.cfg - file does not exist. Shutting down sound hardware idRenderSystem::Shutdown() I18NLocal: Shutdown. So it appears xeyes fails for another reason.
-
Internal errors cause the engine to freeze on Linux
MirceaKitsune posted a topic in TDM Tech Support
http://bugs.thedarkmod.com/view.php?id=4893 I found a very problematic issue in the engine. I'm running TDM 2.06, 64bit executable, Linux version (openSUSE Tumbleweed x64). The issue is as follows: Previously, if a bad script or definition or missing asset error occurred, TDM would crash back to the main menu and the error would appear in the console. It seems this is no longer the case and something worse happens instead: Errors will now cause the process to freeze, shortly followed by a permanent black screen. The reason why this is annoying is because alt-tab switching still doesn't work. To recover the operating system, I need to hit Control + Alt + F1 to go to a different runlevel then use 'top' to find the TDM process followed by a 'kill -9 PID'. Can anyone else confirm this and fix the engine locking up on internal errors? -
Moving the gamma and the brightness sliders does not do anything if I have set the Nvidia GPU in Nvidia X Server Settings, but they work with the Intel HD GPU. This is very annoying since I think the Intel HD GPU is a lot slower than the Nvidia one so I mostly use later, but if I want to play The Dark Mod (and I want to see the level (the default brightness and gamma is very dark)) I have to switch to the Intel HD GPU. What should I do to make the brightness and the gamma changeable with the Nvidia GPU. I am using Ubuntu 16.04, GeForce 820M/PCIe/SSE2(I guess).
-
Hello all, I am trying to compile and play The Dark Mod under my platform (Gentoo Linux). After patching the patchable to make it compile, it turns out that no rendering is shown on screen at all: black screen (with resolution change), mouse is responsive and I can hear the reaction of the GUI to its movement (clicks and all); also the background music (soothing, charming, beautiful... but that you know already) cuddles my ears. I started the bisection of the code from version 2.05 (I think... it was r6753) to r7203. It took me a while (none of the commits compiles out of the box, and different ones require different patches), and in the end I found that r6834 works for me (at least the menu screen!), while r6835 does not any more (as above). I have the output to screen of two runs. In thedarkmod-r6834.txt, I started it with no arguments, and then quit. In thedarkmod-r6835.txt, I started it with no arguments, then I switched to a text console and killed it (because I could not see the GUI to quit). The only files that changed between the two runs are thedarkmod.x86, gamex86.so and tdm_game02.pk4. Any suggestion for me to have this work?
-
I am trying to compile The Dark Mod (r7203) under Linux. It appears commit r7128 calls GLimp_DeactivateFrontendContext() (framework/Session.cpp line 3017), whose implementation is not provided for Linux (sys/linux/glimp.cpp), while it is provided for Windows (sys/win32/win_glimp.cpp). Any solution to this?
-
When playing The Dark Mod I can not use system keyboard shortcuts like Alt-Tab, Esc or Alt-F4. This means that the only way to exit the game is by going to the main menu and quiting there. And there is no way to just minimize it. This is extremely annoying, particularly when I accidentally click an other window after I run the game, but before it loads its window because that means that the game window will appear under the current window and it will lock my mouse and I don't see anything from it, my only option in this case is long holding the power button to turn off the computer. The another problem is that the brightness and the gamma slider does not do anything, there is no way to set them which makes the game annoying to play, because everything is very dark. When I was using Windows these never happened. If I run the .exe using Wine it has no problem (except that the frame rate is decreased to its half). Why is it happening? What should I do?
-
Yesterday I installed 'The Dark Mod' version 2.05 on my computer. ('tdm_update.linux' worked great, but took FOREVER. The resultant 'thedarkmod.x86' file is 6.5 MB in size.) My issues: When starting the program (./thedarkmod.x86), I get great audio, but only a black screen (window).When running on full desktop mode (not in a window), both monitors go black.I can hear clicking when I move the (invisible) mouse pointer within the black screen. Unfortunately, the only way I found to get things back to 'normal' is to do a 'CTRL+ALT+BACKSPACE', since I cannot get the mouse pointer to my desktop (when running in window mode).I cannot see what errors I may have gotten when launching from the command line, because of having to re-start my session (see line above). My computer system: OS: Linux Mint 17.3 (64 bit) CPU: Intel Core i7-3610QM @ 2.30 GHz x 4 System RAM: 8 GB Video Controller: Intel 3rd Gen Core processor Video Card: AMD / ATI Heathrow PRO [Radeon HD 7850M/8850M] Video RAM Available: 2048 MB Displays: Laptop [1920 x 1080 (16:9)], Standalone monitor [1920 x 1080 (16:9)] Anyway, from searching the forum for possible things to do to get video, I changed the following lines in my Darkmod.cfg file: seta com_videoRam "2048" seta r_aspectRatio "1" seta r_fullscreen "0" seta r_customHeight "900" seta r_customWidth "1600" seta r_mode "-1" seta sys_videoRam "0" Still, I get the black screen (window). My Darkmod.log shows: Any thoughts on how to actually 'see' what is hiding inside the black screen (or window)?
- 17 replies
-
We have some internal changes happening in the TDM source code now. As a result of these changes, Linux build is not working in the latest SVN version. This is not appropriate of course The idea is to fix Linux build incrementally, step by step. But the problem is: I have only 64-bit Linux in virtual machine, and it cannot run TDM there. I would be very grateful if some Linux geeky player could help me with testing the builds. In order to do this, you need: Real Linux OS installed (i.e. not in VM) Running native Linux build of TDM Some skill to build TDM (I think this point follows from the previous one) Basic SVN skills Unlimited internet access The last point is needed because testing should be done against uncompressed assets (instead of pk4 archives). Note that I would fix compilation problems myself, so C++/programming skills are not necessary If you can help, please let me know.