HMart

I have a RX570 8GB VRAM, also using latest drivers and I didn't saw such a stark diference in performance between the two! At lest not on the "The gatehouse" mission. Can you remind me what mission is that pic from? Also do you have the RX 570 4GB? If yes could be perhaps a VRAM limitation? But would be very surprising to me, if TDM maps would stress a 4GB GPU!

Just to clarify, if someone maybe wondering, the 16 poly limit, is only for dynamic rigid body physics, not the normal static world and mesh collision mesh's. Now IMO, you can't really compare idtech 4 physics engine, to any other in the market, is a very basic and simple physics engine, done inhouse by a single developer at idSoftware, made to be more complex than Quake 3 physics but still a very performant and fast simple physics system, "good enough" for a 2003 game. In reality, is inferior to any third party physics engine on the market, ODE (used in Stalker), Newton dynamics (used by Frictional games), Bullet, Havok, PhysX and others, are way better and more complex physics engines, today any of them, are a better choice for a game engine than idtech 4 physics engine, why, because they are all multicore physics engines (not sure about ODE), while the one on idtech4, afaik still runs on a single core! And if someone is thinking this, even thou it would be awesome, I don't think the TDM physics engine will ever be replaced, the source of it, was the first thing idSoftware released in 2004 and no one, apart from AAA dev houses, have to this day, at lest that I know, improved it further or even replaced it entirely. So imo If 16 polys is the limit than so be it, time to be cleaver and creative with shapes!

Not saying this is the main cause for you to get lost, but good lever designers, use light cues to indicate the player where he should go, by calling for his attention and by playing with forced bright ambient, perhaps you could be missing that important light cues.

Holy... I also add that happen to me once, almost made me give up modding altogether, something like that can destroy someone will for a long time, hope you can recover from the situation fast! Btw on windows you can try using Recuva (from the makers of CCleaner) to try to recover some of your work or even all if you are lucky. I can only say good luck and hope that this situation don't make you give up on TDM mission making.

I seen the frob outline show hidden objects one or two times during my plays, bellow is a example on "The outpost", I can frob the hammer before even opening the chest. forgot to save the view position unfortunately, but is the chest next to the kitchen, where the single guard patrols, when you enter the castle bellow through the water. But this doesn't seem like a problem of the frob outline technique itself but the technique, showing a bug that always existed in the game but we never saw it, because the old highlight was hidden by the geometry in front. So in a sense this is helping debug the game!

I certainly comprehend that stance and see the advantages of it, more clean code means, less clutter and so better readability but if idSoftware add the same opinion, we wouldn't had found some of the cool stuff they let in the engine disabled, like the mega texture stuff that even thou unfinished, was a way to learn about it and that someone made work, partially, the ability to read MD3 files and animations that is now a option to use in TDM for "cloth" effects, the liquid surface class that someone, more or less, also made work, the disabled item highlight that I'm even using for some effects and many other stuff they let in and didn't bother to clean from the source, like a extra more realistic player motion. But you guys do what you think is best in your case.

Afaik there's nothing preventing you from being able to tweak each LOD distances individually using the method I suggested, at import time you set a reasonable default distance for each LOD, then after that you just expose entity spawnargs to the mission makers like always. Like I said this can work just like the shadow mesh and the collision mesh, the lods would just be extra surfaces for the code to manage, even thou the former are imbedded in the model file itself and even on top of the main mesh and each other, you can still access them individually.

Good thing that I'm using good old simple crosshairs for my game interactions... But Is a pity this is such a hard problem, such a "modern" effect that new gamers automatically think your game is cooler because of it. I certainly comprehend Cabalistic frustration, so much work for in the end, not have good feedback because of the glitch's and no easy solution in sight, demoralizes anyone. But like the others, please don't remove it from the engine entirely, if that is what you guys are thinking, if so please make it optional, no matter the glitch's, imo why have so much work coding this, for in the end throw it all away and if you guys don't want to spend time, messing in the menu code to support a half broken feature, just leave it has something for players messing in the game console to discover, is always cool to open games consoles and find things that the developers left in disabled, to me is a game in it self.

I add that off, changed* it but still the slider images don't work even after a restart. *I saw another imo strange behavior on this, when I changed that cvar value to 1, restarted the game, went to the console again and inputted, image_preload, just to see the current value, it showed 0, despite being changed before the restart and on the DarkMod.cfg it is 1. The value gets overridden somehow?

Yes I have a AMD GPU, hope you can solve that problem, because I don't think I will change GPU's anytime soon...

My following suggestion would need changes at the engine level and also require the team to reimport and export the models again from a 3D tool or perhaps make a special plugging for DR to mix the models into a single one, so may never happen but I think it should at lest be considered and it is the following: Some games, include the LOD models, in the main model itself, like how the engine currently uses the collision model and the shadow model, the same could be done for the LOD's, this would have the following benefits that I currently see, it would unclutter the model folder, because you would only need to export one model, all necessary info is within the model file itself, two permit DR to continue with the current model chooser and entity chooser, no need to mix the two or change DR model handling in any big way, apart from perhaps creating a special filter, to hide the LOD surfaces/models if necessary, like is done for the shadow model, and the best benefit imo, instead of the mission maker having to bother with setting up LOD's manually that would be automatically setup by the engine at model import time and so prevent the problem that Dragofer talks about, forgetting or even not bothering with setting up LOD's. How to setup the LOD's in the 3d tool? It could be done like the shadow model is done, using a special LOD material, or if possible they could be put in a different layer that you give a "_LOD_X" name and the engine would read that layer has a individual model, this would need the engine to support importing models with more than one layer, that I don't think it does (but I could be wrong) and I'm not even sure if, ASE and MD5 support extra layers, I know LWO does. My two cents on this discussion.

I've seen something similar, in my case all sliders in the menu lack the visual movable slide and the value label, also some missions lack the "start mission" string, I assume all this is because of the changes being done to the menu system by stgatilov and will be solved sooner than later.

oh yes a good internal ssd or even a nvem/M.2 ssd can be fast even with preload on, but I have the game in a external USB 3.0 2.5 HDD, so preload may impact me more I assume.

I bet you guys already know this but if you don't, just for kicks I set image_preload 0 and image_useCompression 0 and the missions I tried load way quicker! Is obvious why but I underestimated how impactful this options were! And I didn't felt any performance loss from it. I hope this is true for all! It seems I will play with those off going forward. Btw I also found that using preload 0 and compression ON, causes the game to start with no textures for a few micro seconds, similar to some UE3 games! TDM is now among the big league engines! ;D kd Is not a big problem and the same happens with compression off but for a lower time, unfortunately, the game has visible pauses, when opening doors and the game as to load and compress the textures on the fly. edit: I didn't played the latest version with stgatilov new RGTC compressor in SIMD, so things could be different on it.

Used Avast before, today, I use windows defender add no need for another anti-virus.

IMO this would be more a "marketing" tool than anything, would be cool to see lets play youtubers play TDM and scare the crap ot them selves because they talked at a inconvenient time.

I see this used more for youtube lets plays' thou.

geegee, IMO (even thou I sometimes fail at that) the best way to not reach this stage, is to ignore threads that touch subjects where you have a strong opinion on, is a sure way for you to find people that totally disagree with you or to read posts from others that you may find very offensive, my advice stick to the threads about the game that are mostly on topic. Personally I've add very few instances were I've add to totally ignore someone in a forum and on this forum even less, imo is the most mature mod community I ever seen.

That is how my own simple LOD system works, it does a origin to origin float distance number and I have yet to see any major problem with it, but I will not claim that I have tested it that much, specially in a complex scene with hundreds of LOD entities. I do make sure to do the check, only when the player is within the same area has the LOD object and the player is moving, no need to do it, if the player is stationary or the distance value didn't changed that much between frames. I also do the check in a larger interval, if the entity itself is totally hidden. Btw would love to do the LOD, based on size of object in pixel/screen space, (size of object on screen) like Unreal Engine does but currently I don't know how to do that, if someone has a hint...

You are certainly right, but I was not saying that assert substitutes code for runtime user error handling, it can be used for such a thing (in debug builds) but I use it mostly to catch my own errors, for frontend user errors I use mostly goto; I know goto is hill advised and disliked by many programmers but I use it and I've yet to see any problem with it, but in no way am I saying is the best way to program. b32 somefunc(void) { if(this check fails) goto Error; .... Error: { print("Error message!") return 0; } } I know is not always the best option but it works and idtech 4 besides exceptions also seems to use goto for error handling, personally, I've yet to find the need to use exceptions.

I'm not a programmer of the caliber of any of you, being coding in c++ on and off for 3 years only but I've heard from expert programmers that I have total confidence (Jonathan Blow and Casey Muratori) that exceptions are bad and they do more harm than they help, John Carmack does seem to use them, as anyone can see by looking at the idtech 4 code but is also apparently used very sparingly, like you advise. But your find reinforces the advice from Jonathan and Casey, don't use them at all, so personally even thou Jonh Carmack may have used them and he is a master programmer, personally I haven't been using exceptions at all, only assert or even just a simple goto (this last one I've read, some high level languages like JAVA, masquerade as exceptions). https://youtu.be/UNXHK8O-B_g?t=5630 http://xahlee.info/comp/why_i_hate_exceptions.html Jonathan Blow about his JAI language

"so I'd imagine support for gamepads might have existed in vanilla idTech 4" No vanilla idtech 4 has no gamepad support, is possible to go around that by using some emulation/translation software, that maps gamepad cmds to keyboard cmds but the code itself has no idea about gamepads. (that can be easelly changed today) idSoftware were not fans of those for FPS's when Doom 3 was made (that I totally agree), they were openly against gamepads (that has of course changed now) the game was also PC exclusive for years, they were a very PC centric company in the past.

Oh ok thanks for the info cabalistic, thanks for trying to solve it at lest. Btw I did all in my power, trying to make AMD aware of this problem, I exposed the problem on twitter to the official driver guy and I sent two bug reports on this problem, using the driver bug report feature, but unless many other AMD users do the same, I don't think they will prioritize this particular bug, if only a few complain.

Did something changed in the latest dev 2.10 dev16330-9508 version about bindless textures? I didn't updated my AMD RX 570X driver and when I enabled bindless textures before they were broken and today just because, I enabled it and textures are fine! Are you guys just silently disabling the feature in AMD GPU's now or is it really working? How can I tell?