datiswous
-
Posts
2440 -
Joined
-
Last visited
-
Days Won
32
Posts posted by datiswous
-
-
On 5/12/2021 at 10:47 PM, Frost_Salamander said:
I'd like to use the containers/openable/MerryChest1.pfb prefab in TDM prefabs. However, for some reason the lid doesn't open. I've tried various things to try and fix it, but I can't figure out what's wrong with it. I even tried re-creating the lid (revert to worldspawn, then convert back to a mover_door and re-adding the properties), but same issue.
Has anyone else tried using it? I realize the other 'footlocker' prefabs work fine, but I like the look of this one as it looks a bit more like a travel trunk, which is what it's supposed to be in the map.
Don't know if you managed to find it by now, but what you have to do:
- Select the chest and click on: Edit -> Ungroup Selection
- Select only the lid and go to the Entity details
- Check what name is given. Then only select the body and change the frob_peer and target to the name of the lid.
MerryChest2 has the same issue. Also, the naming of MerryChestBody and MerryChestLid etc. is not consistent with the naming of the MerryChest prefabs.
-
1
-
Clive Barkers Undying. A game with such great atmosphere and the awesome weapon + spell combo.
I also noticed just now that there are some recent improvement mods available:
-
With a lot of missions I got the error (after download) that the mission on the server is outdated. With message: Please inform mod owners, or something. Since I got a lot of crashes during downloads I assumed that missions were incorrectly downloaded. I deleted the specific fm folder and with a new download there was no error.
-
What I noticed btw. is that when more missions are downloaded already and so the mission list is smaller, there are less crashes. I guess there is less to index?
-
The coredump file is pretty big and I can't find a way to directly read it. Could the debug info (GDB) be useful? ( coredumpctl gdb 3129 )
SpoilerGNU gdb (GDB) 10.1 Reading symbols from .../darkmod/thedarkmod.x64... (No debugging symbols found in .../darkmod/thedarkmod.x64) warning: Can't open file /memfd:/.glXXXXXX (deleted) during file-backed mapping note processing warning: Can't open file /memfd:/.nvidia_drv.XXXXXX (deleted) during file-backed mapping note processing warning: Can't open file /memfd:pulseaudio (deleted) during file-backed mapping note processing [New LWP 3163] [New LWP 3129] [New LWP 3136] [New LWP 3131] [New LWP 3135] [New LWP 3138] [New LWP 3133] [New LWP 3132] [New LWP 3130] [New LWP 3134] Warning: couldn't activate thread debugging using libthread_db: Cannot find new threads: generic error warning: File "/usr/lib/libthread_db-1.0.so" auto-loading has been declined by your `auto-load safe-path' set to "$debugdir:$datadir/auto-load". To enable execution of this file add add-auto-load-safe-path /usr/lib/libthread_db-1.0.so line to your configuration file ".../.gdbinit". To completely disable this security protection add set auto-load safe-path / line to your configuration file ".../.gdbinit". For more information about this security protection see the "Auto-loading safe path" section in the GDB manual. E.g., run from the shell: info "(gdb)Auto-loading safe path" warning: Unable to find libthread_db matching inferior's thread library, thread debugging will not be available. [Thread debugging using libthread_db enabled] Using host libthread_db library "/usr/lib/libthread_db.so.1". Core was generated by `.../darkmod/thedarkmod.x64'. Program terminated with signal SIGABRT, Aborted. #0 0x00007f6c3c202ef5 in raise () from /usr/lib/libc.so.6 [Current thread is 1 (Thread 0x7f6bf6ffd640 (LWP 3163))] (gdb) bt #0 0x00007f6c3c202ef5 in raise () from /usr/lib/libc.so.6 #1 0x00007f6c3c1ec862 in abort () from /usr/lib/libc.so.6 #2 0x00007f6c3c244f38 in __libc_message () from /usr/lib/libc.so.6 #3 0x00007f6c3c24cbea in malloc_printerr () from /usr/lib/libc.so.6 #4 0x00007f6c3c24e03c in _int_free () from /usr/lib/libc.so.6 #5 0x00007f6c3c251ca8 in free () from /usr/lib/libc.so.6 #6 0x000000000075c254 in ?? () #7 0x0000000000b42059 in ?? () #8 0x000000000072368c in ?? () #9 0x00000000008d8206 in ?? () #10 0x00000000004bd921 in ?? () #11 0x00000000004bda20 in ?? () #12 0x00000000004b736a in ?? () #13 <signal handler called> #14 0x00007f6c3c202ef5 in raise () from /usr/lib/libc.so.6 #15 0x00007f6c3c1ec862 in abort () from /usr/lib/libc.so.6 #16 0x00007f6c3c244f38 in __libc_message () from /usr/lib/libc.so.6 #17 0x00007f6c3c24cbea in malloc_printerr () from /usr/lib/libc.so.6 #18 0x00007f6c3c24d01c in munmap_chunk () from /usr/lib/libc.so.6 #19 0x00007f6c3c251cdb in free () from /usr/lib/libc.so.6 #20 0x0000000000cb3b8a in ?? () #21 0x00000000008f000e in ?? () #22 0x00000000009030db in ?? () #23 0x00000000011aff7f in ?? () #24 0x00007f6c3c629299 in start_thread () from /usr/lib/libpthread.so.0 #25 0x00007f6c3c2c5053 in clone () from /usr/lib/libc.so.6
How do I get debug symbols?
-
Log of execute in terminal
Spoiler--- Common Initialization Complete --- ------------- Warnings --------------- during The Dark Mod initialization... WARNING:Cannot detect SVN version! WARNING:No 'startingmap.txt' file for the current mod: newmiss 2 warnings WARNING: terminal type 'xterm-kitty' is unknown. terminal support may not work correctly terminal support enabled ( use +set in_tty 0 to disabled ) pid: 11046 Async thread started Couldn't exec autocommands.cfg - file does not exist. Found 0 new mission packages. Found 108 mods in the FM folder. Found 5 new mission packages. Found 112 mods in the FM folder. Successful downloads: 5 Failed downloads: 0 Found 2 new mission packages. Found 112 mods in the FM folder. signal caught: Segmentation fault si_code 1 Trying to exit gracefully.. double fault Segmentation fault, bailing out shutdown terminal support About to exit with code 11coredumpctl info 3129
SpoilerMessage: Process 3129 (thedarkmod.x64) of user 1000 dumped core. Stack trace of thread 3163: #0 0x00007f6c3c202ef5 raise (libc.so.6 + 0x3cef5) #1 0x00007f6c3c1ec862 abort (libc.so.6 + 0x26862) #2 0x00007f6c3c244f38 __libc_message (libc.so.6 + 0x7ef38) #3 0x00007f6c3c24cbea malloc_printerr (libc.so.6 + 0x86bea) #4 0x00007f6c3c24e03c _int_free (libc.so.6 + 0x8803c) #5 0x00007f6c3c251ca8 __libc_free (libc.so.6 + 0x8bca8) #6 0x000000000075c254 n/a (thedarkmod.x64 + 0x35c254) #7 0x0000000000b42059 n/a (thedarkmod.x64 + 0x742059) #8 0x000000000072368c n/a (thedarkmod.x64 + 0x32368c) #9 0x00000000008d8206 n/a (thedarkmod.x64 + 0x4d8206) #10 0x00000000004bd921 n/a (thedarkmod.x64 + 0xbd921) #11 0x00000000004bda20 n/a (thedarkmod.x64 + 0xbda20) #12 0x00000000004b736a n/a (thedarkmod.x64 + 0xb736a) #13 0x00007f6c3c633960 __restore_rt (libpthread.so.0 + 0x13960) #14 0x00007f6c3c202ef5 raise (libc.so.6 + 0x3cef5) #15 0x00007f6c3c1ec862 abort (libc.so.6 + 0x26862) #16 0x00007f6c3c244f38 __libc_message (libc.so.6 + 0x7ef38) #17 0x00007f6c3c24cbea malloc_printerr (libc.so.6 + 0x86bea) #18 0x00007f6c3c24d01c munmap_chunk (libc.so.6 + 0x8701c) #19 0x00007f6c3c251cdb __libc_free (libc.so.6 + 0x8bcdb) #20 0x0000000000cb3b8a n/a (thedarkmod.x64 + 0x8b3b8a) #21 0x00000000008f000e n/a (thedarkmod.x64 + 0x4f000e) #22 0x00000000009030db n/a (thedarkmod.x64 + 0x5030db) #23 0x00000000011aff7f n/a (thedarkmod.x64 + 0xdaff7f) #24 0x00007f6c3c629299 start_thread (libpthread.so.0 + 0x9299) #25 0x00007f6c3c2c5053 __clone (libc.so.6 + 0xff053) Stack trace of thread 3129: #0 0x00007f6c3c6359ba __futex_abstimed_wait_common64 (libpthread.so.0 + 0x159ba) #1 0x00007f6c3c62a7a3 __pthread_clockjoin_ex (libpthread.so.0 + 0xa7a3) #2 0x0000000000bd577e n/a (thedarkmod.x64 + 0x7d577e) #3 0x0000000000c73743 n/a (thedarkmod.x64 + 0x873743) #4 0x0000000000c76a55 n/a (thedarkmod.x64 + 0x876a55) #5 0x00007f6c3c633960 __restore_rt (libpthread.so.0 + 0x13960) #6 0x00000000008e4250 n/a (thedarkmod.x64 + 0x4e4250) #7 0x00000000008d7d4a n/a (thedarkmod.x64 + 0x4d7d4a) #8 0x000000000057d4ec n/a (thedarkmod.x64 + 0x17d4ec) #9 0x000000000057f8a6 n/a (thedarkmod.x64 + 0x17f8a6) #10 0x00000000005f1266 n/a (thedarkmod.x64 + 0x1f1266) #11 0x000000000051a648 n/a (thedarkmod.x64 + 0x11a648) #12 0x000000000051d587 n/a (thedarkmod.x64 + 0x11d587) #13 0x0000000000511b9f n/a (thedarkmod.x64 + 0x111b9f) #14 0x00000000004ba184 n/a (thedarkmod.x64 + 0xba184) #15 0x000000000047fa3d n/a (thedarkmod.x64 + 0x7fa3d) #16 0x00007f6c3c1edb25 __libc_start_main (libc.so.6 + 0x27b25) #17 0x0000000000483e7a n/a (thedarkmod.x64 + 0x83e7a) Stack trace of thread 3136: #0 0x00007f6c3c6359ba __futex_abstimed_wait_common64 (libpthread.so.0 + 0x159ba) #1 0x00007f6c3c631b98 __new_sem_wait_slow64.constprop.0 (libpthread.so.0 + 0x11b98) #2 0x0000000000d491fc n/a (thedarkmod.x64 + 0x9491fc) #3 0x0000000000d58f98 n/a (thedarkmod.x64 + 0x958f98) #4 0x00000000011b0130 n/a (thedarkmod.x64 + 0xdb0130) #5 0x00007f6c3c629299 start_thread (libpthread.so.0 + 0x9299) #6 0x00007f6c3c2c5053 __clone (libc.so.6 + 0xff053) Stack trace of thread 3131: #0 0x00007f6c3c6359ba __futex_abstimed_wait_common64 (libpthread.so.0 + 0x159ba) #1 0x00007f6c3c62f260 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0 + 0xf260) #2 0x0000000000c76d7a n/a (thedarkmod.x64 + 0x876d7a) #3 0x00000000004f2ebe n/a (thedarkmod.x64 + 0xf2ebe) #4 0x00007f6c3c629299 start_thread (libpthread.so.0 + 0x9299) #5 0x00007f6c3c2c5053 __clone (libc.so.6 + 0xff053) Stack trace of thread 3135: #0 0x00007f6c3c2ba37f __poll (libc.so.6 + 0xf437f) #1 0x00007f6c39f72306 n/a (libasound.so.2 + 0x4d306) #2 0x00007f6c39f72604 snd_pcm_wait (libasound.so.2 + 0x4d604) #3 0x0000000000d32d81 n/a (thedarkmod.x64 + 0x932d81) #4 0x00000000011b0130 n/a (thedarkmod.x64 + 0xdb0130) #5 0x00007f6c3c629299 start_thread (libpthread.so.0 + 0x9299) #6 0x00007f6c3c2c5053 __clone (libc.so.6 + 0xff053) Stack trace of thread 3138: #0 0x00007f6c3c28d125 clock_nanosleep@@GLIBC_2.17 (libc.so.6 + 0xc7125) #1 0x00007f6c3c292357 __nanosleep (libc.so.6 + 0x -
1 minute ago, stgatilov said:
Oh, I guess I was too confident to remember all Linux members
I learn things on a case basis, only when I need the info. I guess this is something I should know, I was already searching for it.
-
25 minutes ago, stgatilov said:
Do I understand you correctly that you have experienced occasional crashes many weeks ago (before FM database changes), and you still get them now?
Indeed, but I did not try versions before 2.09 (at least not on this system and that was long ago anyway). I guess I could try to install 2.08 to see if that makes a difference.
24 minutes ago, stgatilov said:Meanwhile, the best thing you can do it record crash dumps with Task Manager and share them here:
Ok, although those guides don't work in Linux. So I'll have to search how that works.
-
1
-
-
A while now I have the problem that the TDM in-game mission downloader crashes during downloads. Usually if I download 1 mission it's ok, but if I que downloads there is a chance of crashing. I waited for the database upgrade, to see if anything changed. I cannot pinpoint where it goes wrong. Is there a logfile somewhere where you can see where it chokes and then crashes?
-
1
-
-
2 hours ago, Acolytesix said:
Remember those days 40kb/s ?
I remember when 5kb/s was considered (by me) as (relatively) fast.
Edit: Actually, that was 5KB/s , so it's the same..
-
1
-
-
1 hour ago, StudentManiac said:
Right chaps, the gist appears to be that my graphics hardware and software is no longer advanced enough for TMD.
But did you try installing the driver from the AMD website? Sometimes the Windows supplied driver is not the correct and/or up to date driver.
-
Maybe irrelevant, but have you done the Game/Project Setup (in DarkRadiant) correctly on both machines?
-
I think the discussion/talk about the new frob shader is over here:
https://forums.thedarkmod.com/index.php?/topic/19915-208-new-frob-shader/-
1
-
-
@JackFarmer can you still tell the meaning of this text?
Spoilerhe ordered us what we did not understand to come after each other and after all.
-
6 hours ago, cabalistic said:
I really have to ask, though - why not Unity or Unreal? Or Godot, if open source is important? All three of them are much more modern engines and probably a lot easier to work with, in general. You'd have to find a very specific advantage in using idTech4 to justify that route, imho.
I was thinking especially at Godot too, but had the idea that their 3d engine part is less sophisticated than idTech4, but I could easily be wrong. But in general even if the 3d engine isn't as powerful it's still probably easier to get all the other aspects of a game right.
-
On 5/5/2021 at 2:56 PM, Acolytesix said:
Took forever to get that unlocked with the robot guard & once inside that key too is unfrobbable. Those keys are important right?
I also had this one time, but when played later (a new run), I could frob it.
SpoilerThis specific key is not vital. It opens one of two routes, so you can still take the other route.
-
Thanks that worked
-
On 3/26/2021 at 1:26 PM, OrbWeaver said:
With the next version you can use the wxAUI-based Dockable layout
Can you have more XY views as dockable windows? I try to do that (in DR 2.12), but when I choose "New XY view" I get an undockable window.
Btw. if the camera dockable window is placed outside of the main window (I thought this is nice to have on a second monitor), the keyboard doesn't work in that area. So I guess I can't use it that way. Strange enough the Properties dockable window does allow keyboard control for moving through the list of textures.
-
Is there a way to manually fix this after install? I just did an install from source and have the same issue.
-
What is the aimed improvement of this upgrade?
-
10 hours ago, greebo said:
your personal settings and preferences are shared between all DR builds, they are always saved to and read from ~/.darkradiant/ IIRC
I think that is ~/.config/darkradiant (in my case). That folder has the following files:
- colours.xml
- darkradiant.language
- filters.xml
- input.xml
- user.xml
Is that the correct folder?
I have to remember to make a backup of the main bitmap folder because I made custom icons for use with a dark theme.
-
Hi thanks for the new edition.
Questions:
How much time is there roughly between releases?
When I build from source (I have no other choice) will this just overwrite the previous installation and settings etc?
-
Just noticed that although https://wiki.thedarkmod.com/index.php?title=How_to_pack_your_Mission states that the image install_splash.tga should be 256x256, the image is streched to 4:3 in the fm selection in TDM if the image is 1:1. So that wiki info should be changed. Maybe it's just outdated info. Also the image canvas can be much larger px wise, don't know why it should be 256 px.
-
Stability improvements to the in-game mission installer (mine crashes a lot)
In the file mainmenu_newgame.gui (part of tdm_gui01.pk4) I would like that the transparency of the install_splash.tga is modified slightly from 0.2 to 0.3 . This means an overall improvement on the look of these images (you can then actually see what they are most of the time), there is no real downside. 0.3 should be the default.
See:Edit: a darkmod.cfg config setting would be better so that the transparency level could be set on a personal basis.
-
1
-
Newbie DarkRadiant Questions
in TDM Editors Guild
Posted
In missions I often get a short scary moment because I hear a door opening, when I actually open a chest. I guess these chest prefabs are based on door-behavior, because the sounds are still the same.