Jump to content
The Dark Mod Forums

Search the Community

Searched results for '/tags/forums/graphics/' or tags 'forums/graphics/q=/tags/forums/graphics/&'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • General Discussion
    • News & Announcements
    • The Dark Mod
    • Fan Missions
    • Off-Topic
  • Feedback and Support
    • TDM Tech Support
    • DarkRadiant Feedback and Development
    • I want to Help
  • Editing and Design
    • TDM Editors Guild
    • Art Assets
    • Music & SFX

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

  1. I just tested on the other system. v1.1 didn't seem to change much from v1.0 on the i5-6600T + HD 530 Graphics system, but I delved further into the mission. Interior portions obviously have much better performance. My performance target for this system is basically 720p 30 FPS. I tested the beginning on the 5700G + GTX 970 system for a minute just now and I can get it to hold at as low as 20 FPS at 1080p, e.g. on the starting boat looking out past where the rope is. Wild swings between 20-60 FPS (locked to 60) as I look around. I haven't made adjustments to other settings like AA yet, that could likely boost performance. I'm still on TDM 2.11. I don't want to upgrade to a dev build right now, but I'm interested to see what kind of performance boost 2.12 can bring.
  2. There's a group of players who have meticulously tested and adjusted ghosting rules for The Dark Mod. Please see: Official Ghosting Rules: https://www.ttlg.com/forums/showthread.php?t=148523 Ghost Rules Discussion: https://www.ttlg.com/forums/showthread.php?t=148487 Why alienate an established group of dedicated players?
  3. Hm, looking at the mainmenu_briefing.gui file it might actually be possible to make a gui with navigation buttons, make the navigation buttons move to a new page with possible graphics, but also list the second page of the xdata file. Because it does this: windowDef scrollDown { rect 292,390,57,27 background "guis/assets/briefing/nextpage" visible ("gui::ScrollDownVisible" == 1) onMouseEnter { set "cmd" "play sound/meta/menu/mnu_hover;"; } onAction { // Send the request to the script set "cmd" "play sound/meta/menu/mnu_select; briefing_scroll_down_request"; } } So you remove the scrolldown button and when you do the next page action, you activate: set "cmd" "play sound/meta/menu/mnu_select; briefing_scroll_down_request"; Edit: Actually you can also keep the normal navigation but include graphics, etc. and when you do the scroll down action, you can change the page, add new graphics, etc. and also move to the next xdata page. I think. But it doesn't seem like you can specify a certain xdata page.
  4. Why not? It's a regression that introduced an annoying stuttering. It seems to be graphics rendering related. The stuttering can be made worse or better by adjusting "com_maxFPS". I don't see how that issue is related to this rendering performance issue.
  5. Finally got around to playing this, and I'm happy to see new fan missions on the download list. Exploring the map was very enjoyable, and I liked the verticality... also the opportunity to "cheat" and get around with rope arrows made me glad I invested in them at mission start. The sense of scale in the map, particularly crawling around scaffolding under the bridge, was cool and I enjoyed the view of the city in the fog. That said, I mirror some of the comments here that even with a pretty beefy graphics card I had the whole game freeze for almost half a minute whenever I faced out into the skybox view while standing on top of the ground floor outhouse (just in front of the sitting guard outside, by the door). I never had any of the bridge problems others have reported, so I guess that might be a sporadic issue. At any rate, a fun map. Very enjoyable!
  6. OK I think I've got to the bottom of this. I've created this forum thread (with bug report): https://forums.thedarkmod.com/index.php?/topic/22221-bug-drowning-ai-in-shallow-water/ I can apply a workaround, although it won't be perfect and the bug itself needs fixing in the engine. There are a few other things that need fixing so will put an update together soonish.
  7. If any mappers have encountered weirdness with kill objectives not working with drowning AI, I think I've found out why. I don't think it would be a particularly difficult one to fix either. I've raised this bug report: https://bugs.thedarkmod.com/view.php?id=6323 Some context here: https://forums.thedarkmod.com/index.php?/topic/21837-fan-mission-the-lieutenant-2-high-expectations-by-frost_salamander-20230424/&do=findComment&comment=487316 I think this is a bug, but just raising here in case some people think otherwise.
  8. I dom't use it, i found it here with the filter set to OpenSource. the TOS and PP isn't excluding for an OpenSource app, if they use ads mean that they also need to pay an server for this online service. OpenSource is not synonymous with free either, perhaps after the beta phase it is no longer free, so perhaps you can take advantage of the fact that it is still free to create a series of textures that can be used or search another one in Futuretools. AI generated textures and assets, by definition, don't have any copyright, so you can use them as you want. https://www.futuretools.io/?pricing-model=free|open-source&tags-n5zn=gaming
  9. HP Elitedesk 800 G3 with i5 6500, 8gb dual channel , 256Gb SSD and 1 GB VRAM allocated to intel skylake integrated graphics. The result was disappointing, i got all-time low fps in TDM, stutters all time, my lowest fps was 7-8 fps and the highest i can get was 70 iirc. Thinkpad T480(yep i know business laptop isn't supposed to run games and i use it mainly for development purposes) with core i5 8250u , 8gb ram and 512GB SSD : minor improvement from above spec, probably around 5-6% Ryzen 3 3200G APU with 8GB dual channel 2666mhz DDR4 RAM, 1GB VRAM and 512 nvme SSD+ 512GB SATA SSD : able to hit above 60-80+ fps without much effort
  10. jaxa

    2016+ CPU/GPU News

    i5-6600T here which is virtually identical or slightly slower, same Intel HD 530 graphics, paired with 32 GB dual-channel DDR4-2133, and a M.2 SSD. With my 720p display (which is set to 1360x768 for whatever reason) I was getting around 40 FPS in High Expectations beta testing, with dips to the 20s. But the internal TDM/Doom3 FPS counter seems very erratic. I've ended up getting a much better experience in TDM by locking it to 30 FPS. Dips are less common, the experience is playable. It's clearly faster than the old A6-3400M APU I used to use to play TDM a decade ago, which was not always bad but would sometimes crater down to 4-5 FPS. I'm pretty much always getting around 28-30 FPS when locked. I think I can upgrade the CPU itself to at least an i7-7700T which is slightly better all around (maybe i7-7700 if I have the correct 65W-capable Dell motherboard), but the prices I've seen on ebay suck. If it's significantly more than $30 shipped, I might as well stick with the 6600T and put that cash towards the next mini PC.
  11. My core i5 6500 with SSD and dual channel 8gb RAM slapped on it barely hit above 80 fps on the dark mod(lowest setting, 768p resolution) , framerate is crazily high on loading screen, sometime it suffers dramatical fps drop on certain spot and freezes for a second and goes back to normal. I have tried playing with all non essential program shut down to minimize background process but to no avail. This applies not limited to the darkmod itself, strange lag spikes also occur when i play decade old games such as far cry 2, splinter cell double agent and SC: conviction, sleeping dogs, hitman absolution and Just cause 2 , all of which could be handled easily by modern intel integrated graphics. I know i have budget to upgrade but i am trying to push my pc to its limit. i borrowed my sister's pc yesterday and tried running latest dark mod on ryzen 3 3200g with 8gb ram and 1GB vram allocated to its IGP , the difference was night and day. Gonna purchase ryzen 5 5xxx with cheapest AMD/Nvidia GPU and this HP elitedesk 800 G3 would be repurposed as my next homelab
  12. Hello TDM-ers. I am encountering an issue where textures seem to partially disappear. I tried searching the forums, but, I don't know what to search for. The missing textures are a worldspawn brush acting as a roof with {for now} flat iron texture. There are other worldspawn brushes right below to create an attic ceiling with roof framework board texture. These gaps appeared a few edits ago. I can't "undo" to get back before whatever edit did this. The gaps are only visible during play and are not visible during editing. Closing and reopening DR and TDM do not fix anything. Some of the brushes overlap in areas behind the play area but I have never seen an issue doing that. The attached image has the effect I am now seeing. Ideas on where to start debugging this? Very much appreciated. Clint
  13. Yes, naturally it demands more resources at higher settings, but due to its minimal requirements there should be no problem on current equipment even at the highest settings, at least not on my laptop, which isn't exactly a NASA PC either. The same thing happens with the Tomb Raider 2013 that I have, which runs smoothly on maximum settings, without my laptop exploding into spontaneous combustion. They are exquisitely optimized games with graphics that you would not expect with such low system requirements. I have tried games with much more rudimentary graphics that I was not able to put above 15 FPS, due to how poorly they were optimized.
  14. I think it's the game not allocating enough Ram. Maybe it isn't an issue for you depending on your game settings. The game obviously consumes more Ram when you crank up the graphics settings.
  15. Awesome! Post is up! https://forums.thedarkmod.com/index.php?/topic/22200-beta-testing-the-house-of-delisle/#comment-487365 Thanks!
  16. Complaint From Players The player must pick up candles before extinguishing them, and then the player must remember to drop the candle. The player must drag a body before shouldering it (picking it up), and the player must remember to frob again to stop dragging the body. The player finds this annoying or easy to make mistakes. For players who ghost, some of them have the goal of returning objects back to their original positions. With the current "pick up, use item, and drop" system, the item might not return easily or at all to its original position. For example, a candlestick might bounce off its holder. (See player quotes at the bottom.) Bug Tracker https://bugs.thedarkmod.com/view.php?id=6316 Problems to Solve How can the "pick up" step be eliminated so that the player can directly use or interact with the item where it is in the game world? How can so much key pressing and mouse clicking be eliminated when the player wants to directly use an item? How can candles be extinguished and lanterns toggled off/on without first picking them up? How can bodies be shouldered without first dragging them? Solution Design Goals Make TDM easier for new players while also improving it for longtime players. Reduce tedious steps for common frob interactions. Make it intuitive so that menu settings are unnecessary. Do not introduce bugs or break the game. Terms frob -- the frob button action happens instantly. hold frob -- the frob button is held for 200ms before the action happens. (This can be changed via cvar: 200ms by default.) Proposed Solution Note: Some issues have been struckthrough to show changes since the patch has been updated. Change how frobbing works for bodies, candles, and lanterns. For bodies: Frob to shoulder (pick up) a body. Second frob to drop shouldered body, while allowing frob on doors, switches, etc. Hold frob (key down) to start drag, continue to hold frob (key down) to drag body, and then release frob (key up) to stop dragging body. Also, a body can be dragged immediately by holding frob and moving the mouse. For candles/lanterns: Frob to extinguish candles and toggle off/on lanterns. Hold frob to pick it up, and then frob again to drop. Frob to pick it up, and then frob again to drop. Hold frob to extinguish candles and toggle off/on lanterns. For food: Frob to pick it up, and then frob again to drop. Hold frob to eat food. For other items: No change. New cvar "tdm_frobhold_delay", default:"200" The frob hold delay (in ms) before drag or extinguish. Set to 0 for TDM v2.11 (and prior) behavior. Solution Benefits Bodies: New players will have less to learn to get started moving knocked out guards. With TDM v2.11 and earlier, some players have played several missions before realizing that they could shoulder a body instead of dragging it long distances. Frob to shoulder body matches Thief, so longtime Thief players will find it familiar. Second frob drops a shouldered body. Players still have the ability to both shoulder and drag bodies. Compatible with the new auto-search bodies feature. Dragging feels more natural -- just grab, hold, and drop with a single button press. There is no longer the need to press the button twice. Also, it's no longer possible to walk away from a body while unintentionally dragging it. Set "tdm_frobhold_delay" cvar to delay of 0 to restore TDM v2.11 (and prior) behavior. Candles: New players will have less to learn to get started extinguishing candles. With TDM v2.11 and earlier, some players didn't know they could extinguish candles by picking them up and using them. Instead, they resorted to throwing them to extinguish them or hiding them. Hold frob to extinguish a candle feels like "pinching" it out. Once a candle is picked up, players still have the ability to manipulate and use them the same way they are used to in TDM v2.11 and earlier. For players who ghost and have the goal of putting objects back to their original positions, they'll have an easier time and not have to deal with candles popping off their holders when trying to place them back carefully. Set "tdm_frobhold_delay" cvar to delay of 0 to restore TDM v2.11 (and prior) behavior. Solution Issues Bodies: Frob does not drop a shouldered body, so that might be unexpected for new players. This is also different than Thief where a second frob will drop a body. "Use Inv. Item" or "Drop Inv. Item" drops the body. This is the same as TDM v2.11 and earlier. This is the price to pay for being able to frob (open/close) doors while shouldering a body. Patch was updated to drop body on second frob, while allowing frob on doors, switches, etc. Candles: Picking up a candle or lantern requires a slight delay, because the player must hold the frob button. The player might unintentionally extinguish a candle while moving it if they hold down frob. The player will need to learn that holding frob will extinguish the candle. The player can change the delay period via the "tdm_frobhold_delay" cvar. Also, when the cvar is set to a delay of 0, the behavior matches TDM v2.11 and earlier, meaning the player would have to first "Frob/Interact" to pick up the candle and then press "Use Inv. Item" to extinguish it. Some players might unintentionally extinguish a candle when they are trying to move it or pick it up. They need to make sure to hold frob to initiate moving the candle. When a candle is unlit, it will highlight but do nothing on frob. That might confuse players. However, the player will likely learn after extinguishing several candles that an unlit candle still highlights. It makes sense that an already-extinguished candle cannot be extinguished on frob. The official "Training Mission" might need to have its instructions updated to correctly guide the player through candle manipulation training. Updating the training mission to include the hold frob to extinguish would probably be helpful. Similar Solutions In Fallout 4, frob uses an item and long-press frob picks it up. Goldwell's mission, "Accountant 2: New In Town", has candles that extinguish on frob without the need of picking them up first. Snatcher's TDM Modpack includes a "Blow / Ignite" item that allows the player to blow out candles Wesp5's Unofficial Patch provides a way to directly extinguish movable candles by frobbing. Demonstration Videos Note: The last two videos don't quite demonstrate the latest patch anymore. But the gist is the same. This feature proposal is best experienced in game, but some demonstration videos are better than nothing. The following videos show either a clear improvement or that the player is not slowed down with the change in controls. For example, "long-press" sounds long, but it really isn't. Video: Body Shouldering and Dragging The purpose of this video is to show that frob to shoulder a body is fast and long-press frob to drag a body is fast enough and accurate. Video: Long-Press Frob to Pick Up Candle The purpose of this video is to show how the long-press frob to pick up a candle isn't really much slower than regular frob. Video: Frob to Extinguish The purpose of this video -- if a bit contrived -- is to show the efficiency and precision of this proposed feature. The task in the video was for the player to as quickly and accurately as possible extinguish candles and put them back in their original positions. On the left, TDM v2.11 is shown. The player has to highlight each candle, press "Frob/Interact" to pick up, press "Use Inv. Item" to extinguish, make sure the candle is back in place, and finally press "Frob/Interact" to drop the candle. The result shows mistakes and candles getting misplaced. On the right, the proposed feature is shown. The player frobs to extinguish the candles. The result shows no mistakes and candles are kept in their original positions. Special Thanks @Wellingtoncrab was instrumental in improving this feature during its early stages. We had many discussions covering varying scenarios, pros, and cons, and how it would affect the gameplay and player experience. Originally, I had a completely different solution that added a special "use modifier" keybinding. He suggested the frob to use and long-press frob to pick up mechanics. I coded it up, gave it a try, and found it to be too good. Without his feedback and patience, this feature wouldn't be as good as it is. Thank you, @Wellingtoncrab! And, of note, @Wellingtoncrab hasn't been able to try it in game yet, because I'm using Linux and can't compile a Windows build for him. So, if this feature isn't good, that's my fault. Code Patch I'll post the code patch in another post below this one so that folks who compile TDM themselves can give this proposal a try in game. And, if you do, I look forward to your feedback! Player Complaints TTLG (2023-01-10) Player 1: TDM Forums (2021-03-13) Player 2: Player 3: TDM Forums (2023-06-17) Player 4: TDM Discord (2021-05-18) Player 5: TDM Discord (2023-02-14) Player 6: Player 7: Player 8:
  17. The *DOOM3* shaders are ARB2 ('cause of old GeForce support) carmack plan + arb2 - OpenGL / OpenGL: Advanced Coding - Khronos Forums
  18. There is a whole mess of graphics mods for Doom 3 you could peek at. Sikkmod for example is not based off BFG and has a depth of field effect when reloading weapons which sounds like basically what you are looking for and I doubt it requires engine level changes to work: At a minimum you could download one of these mods and given doom3 stuff is typically all text formats in .pk4s there might be enough there you can just read to figure out how it works. As far as it’s potential inclusion in the game I have no real opinion - though given it would likely be optional I don’t see it hurting anything either.
  19. Seems to confirm: https://bugs.thedarkmod.com/view.php?id=5718 does it happen in the latest dev build: https://forums.thedarkmod.com/index.php?/topic/20824-public-access-to-development-versions/
  20. I just read@motorsep Discovered that you are able to create a brush, then select it and right click "create light". Now you have a light that ha the radius of the former brush. Just read it on discord and thought it may be of use for some people in the forums here too.
  21. I just found this thread on ttlg listing Immersive Sims: https://www.ttlg.com/forums/showthread.php?t=151176
  22. Recently revisiting the forums after a longer period of time I wanted to check the unread content. I don't know if I am doing this wrong since.. ever... but on mobile (visiting the unread content page on my smartphone) you have to click on that tiny speech bubble to go to the most recent post in a thread. If you don't click correctly you'll hit the headline and end up at post 1 in the beginning of the thread. It's terrible on mobile, since not only the speech bubble is really small and was to miss. But also the thread headline is just millimeters away from it so you go right to the first post that was ever made instead of the most recent ones. Am I doing it wrong? I just want to go through u read content a d the to the newest post from that topic.
  23. A@datiswous Ah yeah, well sorry, I was quiet busy and only visiting discord. First time here on the forums since months now I think.. Thank you for the subtitles. I encourage everyone who is interested in using them to download it from here as I'm not sure when I'll be able to implement them myself into the mission. Again, thank you for your work.
  24. Though this is related to PBR as a component in getting it done right (like reflection probes) I thought it's an improvement of its own that's worth discussing. I don't know if this is implemented or estimated in some form, but working with light entities in my own FM's I haven't seen any spawnargs for it so I presume it's not. At the moment lights in TDM act as zero-scale points, light sources have no actual radius. I know what you might be thinking: Of course lights have a radius, it's the box that decides how far a light shines and what it affects! What I'm referring to is not the range but the emission radius, representing the scale of the bulb itself: Think of it as a minimum radius... at the moment lights only have a maximum radius, the minimum is currently a point. In modern engines this affects both specularity and shadow softness as well as how the light is distributed. Like most engines we shouldn't need anything more than a float describing the size of the bulb, a simple sphere ought to be enough... given we already work with radius boxes, we could instead use a separate box which would give us better control with unevenly shaped bulbs. Every default light entity should of course be updated to use this: Torches / candles would set it to the average size of their flame particles, gas / electric lamps should have it represent the scale of the light bulb or the lamp head. If done right this can greatly improve our graphics and add more realism, but as with most things it's not going to be that simple. Also this would create changes to the lightgem in all FM's but very minuscule ones that shouldn't even be detectable. There's 3 different components I presume we have to tackle independently. Soft shadows: Shadowmap softness is probably the easiest, just add the average bulb radius to their value. Specularity: At the moment all lights seem to produce specular orbs of the same fuzziness on shiny surfaces. What we probably want is for lights that keep their min radius 0 to produce a fully sharp orb or dot, softness is added to each light's ball based on this radius. Light projection: The biggest aspect is changing how light is distributed, the projection texture / falloff material would emanate very differently. Everything inside the bulb would shine at the intensity of the center pixel and should start fading from the min radius toward the max, the projection texture would get slightly inflated like a balloon. The best solution (which also accounts for blur) seems like a 2D shader that copies the light texture onto itself at slightly different offsets to make it fuzzy: There's already a blur filter that does just that when you're underwater for example, we could to get away with doing the same thing to light textures using the min radius as the offset parameter. As lights typically don't change scale, this should be possible to do only once at map start rather than every frame including for moving lights like torches, this way we should have no performance loss.
  25. Alas, that is Fedora for you. Yes, updates are routine, and I think my graphics card support has been a bit dodgy for a while now, possibly since Fedora 37; suspect the card support is busily rotting . My graphics card is 12 years old now, and I guess whatever special support it needs is progressively getting forgotten. It was working perfectly well a month or two ago. Will do this evening and report back.
×
×
  • Create New...