Search the Community

Is it possible the forum is showing you the decompressed file size? EDIT: nope, that's not the case, if I full screen the image and download it, it's twice the size in MB, but it's image size is smaller, so the forum is resizing and recompressing, but probably doing it as fastest path instead of smallest path.

I would expect both approaches have roughly similar speed in general, with the exception that stencil shadows are culled to light screen size projection while shadow maps are usually fixed in size. E.g. when player is a room fully lit by a couple lights (Officer Lounge in Fence) stencil light will draw in full screen size twice, while shadow map could draw in 512x512 buffer. But then player is in the street with many small lights stencil could draw each light in a screen region as small as dozens of pixels, while shadow map is still 512x512 (not that there's no way to add LOD's to that as well)

freyk, I performed the following from the link you noted: sudo dpkg --add-architecture i386 sudo apt-get install libc6:i386 libstdc++6:i386 libx11-6:i386 libxext6:i386 libxxf86vm1:i386 libpng12-0:i386 libasound2-plugins:i386 libgl1-mesa-dri:i386 libgl1-mesa-glx libgl1-mesa-glx:i386 libglapi-mesa:i386 libglu1-mesa:i386 wget unzip sudo mkdir -p /usr/share/games/darkmod sudo chown -R nobody:users /usr/share/games/darkmod sudo chmod uga+w /usr/share/games/darkmod exitI moved all of my darkmod files to the new directory (which makes sense), reran 'tdm_update.linux', made 'thedarkmod.x86' executable, and tried to run it again. Again, black screens, which were mirroring each other when I exited the program. I changed the darkmod.cfg as shown in my first post, and ran 'thedarkmod.x86' again. This time, a black window. Here is my new console dump: Any thoughts?

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)?

Check for in game video resolution? And what is system wide screen resolution?

So I was playing a mission when TDM decided to shoot itself and lock up. After resetting my computer, I found that the screen was smaller: Now I have two black bars on both sides, with the actual screen compressed between them. I tried playing with the screen size and aspect ratio, but all I can seem to do is make the graphics sharper or force TDM into a window instead of the full screen. Is there some ideal to get the screen back to where it was? Or should I just go with this, since the game seems to run a little better. Essentially, I've gone from this: http://imgur.com/a/mV6Hr to this: http://imgur.com/a/a43xn Apologies for the poor quality, I'm mainly trying to show screen compression. First one is wider, second one is narrower. EDIT: Current settings for the second pic. 4:3 for aspect ratio. 1024X786 for screen size

Personally I recommend people to start with C instead of C++, imo C is much easier to learn, i also think functional programming is easier to grasp initially than OOP. Btw idScript and in some parts the idtech4 engine itself, imo look more C like than C++ like, the engine is indeed written using C++ and OOP, but i just think that John Carmack was so used to the C ways that he still used it for many things. For example this is how you print to screen: in idScript: float someNumber = 10; string someString = "Hello World!!"; sys.println("I'm printing" + someString + "and the number" + someNumber); in C. unsigned int someNumber = 10; const char* someString = "Hello World!!"; printf("I'm printing %s and the number %d\n", someString, someNumber); in c++ (if i'm recalling well) unsigned int someNumber = 10; const char* someString = "Hello World!!"; cout >> "I'm printing" >> someString >> "and the number" >> someNumber >> endl in idtech 4 "c++" unsigned int someNumber = 10; idStr someString = "Hello World!!"; gameLocal.Printf("I'm printing %s and the number %d", someString, someNumber); Btw I don't claim i'm a good coder i started to seriously learn coding only about 6 months now, hardly any time to call my self a real programmer. I learned idtech 4 script before starting to learn c and now i'm learning idtech 4 c++ and i most say, idtech 4 scripting is much more simple, coding in the engine c++ is really not the same. Learning scripting will indeed help you gain a "programmers mind" but will not make you proficient in C or C++ or any other low level language. For example this is what you normally do on idscript to call some function: someEntity.callFunction("function_name"); This is what you do on the c++ side: const function_t *func; idThread *Thread; func = Entity->scriptObject.GetFunction("signalOn"); Thread = new idThread(); Thread->CallFunction(Entity, func, true); Thread->Start(); Thread->End();Much more verbose and complex. Without help anyone good at idScript would do the C++ version. So imo learning one is not guaranty that you will immediately fully understand the other, but it certainly helps.

And if you get a black screen, there is a error in your gui-code. And the console will display the number of the codeline.

So I was following a tutorial on GUIs, and I since discovered that my installation (or TDM itself) seems unable to load both the custom GUIs (when you use the console command "testgui xxxxx.gui"), or the GUI editor that is supposed to come included in DOOM. The first simply fails, saying that the game cant load the gui, and the screen turns black (I´ve tried with a few different ones, even stuff from the startmap pack, and the results are the same), and the editor actually loads up, but when you click "new", nothing happens; when you try to load any gui, it says it cant import it or load it, and when you exit the program, TDM crashes, is unable to continue. Is that only on my end, or has the gui functionality somehow changed during the standalone process? Perhaps some of it hasnt been ported yet?

Yes, the proper way to do this is to take advantage of shader branching. I remember looks at the backend awhile back and seeing that it creates black textures for any stage not supplied in a material so that the ARB shaders always have a texture input... (and I thought that was pretty dumb). Branching would also solve the issue were TGA normal maps require a different interaction than RGTC or other compressed formats.

I dont see any this-problemrelated-errors in the log. Could you create another log using full screen? Set r_fullscreen from 0 to 1 in darkmod.cfg Then run tdm with arguments: thedarkmod.exe +condump pbhallamlog2.txt +quit upload the new log To solve this screen problem, i think you have to change the screenresolution(s) of the game to lower settings. But first you have to detect the screenresolution that works. First set a small screensize in darkmod.cfgChange to following values in darkmod.cfg: seta r_customHeight "600" seta r_customWidth "800" seta r_fullscreen "1" If this works without any problems, then go the videosettings of the game and change them.To play it safe, start first with a low screenresolution, test it. If it works set a higher screenresolution.(to reset the settings, delete darkmod.cfg)

Nothing explicit there but Windows 10 has problems with DPI scaling. Try the workarounds here: http://wiki.thedarkmod.com/index.php?title=FAQ#Does_TDM_support_widescreen_resolutions.3F also, it's worth creating an autoexec.cfg with seta r_displayRefresh "60" (or whatever your screen refresh is) to ensure that your video driver recognizes the correct refresh rate.

Hey! Thanks for the great help! I was able to get it running in windowed mode. There wasn't an existing darkmod.cfg file, so I created one with the seta r_fullscreen "0" command as the only line in the file. This allowed TDM to run successfully in a small window, from which I was able to adjust the video settings to run in a larger window. The game is now playable and runs great even at a 'Very High' LOD. (And, it is a spectacular and very worthy continuation of the Thief series!) Prior to getting TDM running in windowed mode, I did not see a darkmod.log file (that doesn't mean there wasn't one). I re-edited the darkmod.cfg file to contain the seta r_fullscreen "1" command, which does still cause the black screen/frozen computer issue if TDM is run normally. Then, I ran the command you posted to this thread and in the 'Debugging TDM systemerrors' online manual: thedarkmod.exe +gfxinfo +condump mylog.txt +quit. The resulting file, pbhallamlog.txt is attached to this reply. Any thoughts on how to get TDM running in fullscreen mode? Thanks again! pbhallamlog.txt

That above to run TDM in a window, instead of a full screen. Thanks for the update log, but that is for the updater and not for the darkmod executable. Are there any darkmod.log-files in the folder? If not, here is a manual to create them. And use the command to create a appropriate log for us: thedarkmod.exe +gfxinfo +condump pbhallamlog.txt +quit (this will automatically launch TDM, generate a log and close tdm)

I am unable to get TDM to run. I installed TDM using The Dark Mod Updater v0.66 into the C:\darkmod directory. When executing the TheDarkMod.exe application, the screen goes black, my monitor indicates that there is a 'HDMI' cable connection and then briefly brings up the monitor menu buttons overlay for a few seconds. After which, the screen is completely black. At this point, neither Control-Alt-Delete nor Alt-Control-Tilde work, the computer is frozen, and the computer requires a hard power down and reboot. A second reinstall of TDM shows the same results and behavior. I have attached a .txt file of the TDM Update Log Window. My system configuration is: ASUS Desktop PC CM6850 Series Intel Core i7-2600 CPU, 3.4 GHz 8 GB RAM Windows 10 Home, 64 Bit NVIDIA GeForce GT 530 (Driver Date:5/17/2017) 6134 MB Total Available Graphics Memory Any help on getting TDM running would be greatly appreciated. Thanks! TDM Update Log Window.txt

The blue windows, the multi-colored windows, and the black windows are all back to normal now. Good work. Thanks!

Another mission to look at is Lords & Legacy. The transparent windows in the opening poor section of town are now a mix of things: okay, rainbow-colored, bright blue, etc. A good example is where the open window where the female is wandering around is clear, but the closed window on the other side of the door from it is blue. Go to the central part of the map where the guard station is and look at the surrounding transparent windows. They're all black. Lots of problems in this map.

I edited my previous post with the updated log. I can only dump the log when I'm on the first screen after loading the mission. The console won't open when the screen goes black.

Don't need the DMAP log. Just open TDM, try to run the mission as normal. When you get to the black screen, then drop down console.

Still this lol. The console will usually show the cause of such issues, black screens are sometimes caused by failures to load textures or gui files etc.

Ok, apparently the problem isn't solved. The mission worked fine on my laptop, when trying again on my desktop, I get the same issue. I have tried reinstalling the Dark Mod with no luck either. When deleting the mission from the fms folder and just loading the mission from console, everything works fine as it should. It is only when I make a .pk4 file and load it via new game that I get the black screen when hitting objectives... When I put that .pk4 mission in my laptop, it worked fine... very confusing...

I know that engine is the most modern but also more similar to the original one, it has full support for all vanilla idtech 4 features and tools, for example the vanilla GUI system, where all engines based on Doom 3 BFG source require Flash, at lest for fullscreen GUI's. There's other stuff on it that is cool has well imo, support for Qt GUI based tools, for example the fhDoom engine light editor is made with it, and looks very nice imo, unfortunately is the only converted tool for now plus i don't know if you can do game based GUI's with it. It also has direct support for GLSL shaders, their usage in materials is very similar to the ARB ones. Btw MirceaKitsune is just a technicality, but fhDoom has support for Parallax Occlusion Mapping or POM (off by default), that is a different tech from Parallax Mapping, that is a older and imo uglier technique (makes everything look like molten glass), POM is similar to Horizon Mapping for example. Also vanilla Doom 3 has support for POM as well but you need to install a modified ARB interaction shader, if i'm not mistaken SIKKmod has one, POM also requires a bump map (black and white texture) in the case of fhDoom that bump map most be put onto the alpha channel of the specular map, btw not confuse with the bump keyword for TDM materials that only convertes a bump map into a normal map.

I'm having a weird issue where I get a black screen whenever I click on objectives before jumping into my mission. I'm not sure what's causing this, and can't find anything on the wiki/forums on this glitch. Any help is appreciated.

That was weird. The difference between vsync on and off was basically that when it was on, it looked more or less as if it was off, just without screen tearing. Only when I used com_fixedTic 1 command, the movement was smooth again. That helped, thanks.

the texture files are not the same size so it looks like one has been altered. maybe the alpha channel has been removed on the later texture. it might depend on a texture editor some use 0 as transparent value and some use 255 as transparent value, if they've been swapped then the alpha channel would appear black.