Jump to content
Forum Login Changes ×
The Dark Mod Forums


  • Posts

  • Joined

  • Days Won


Posts posted by greebo

  1. You will run into problems with worldspawn geometry, since the engines are usually working with single-precision floats. You'll not be able to distinguish anymore from planes that are 0.5 units apart (which sounds ok, but for angled intersections and sealing geometry this might not cut it, literally).

    (This question really is not so much about the editor, which is working with doubles to store geometry - even though the DR renderer is also operating on single precision floats - this provides a huge performance benefit over doubles).

    • Like 2
  2. Changing the project/game setup and paths is a pretty massive change from DR's perspective. Almost everything needs to be re-initialised when setting the paths, which sometimes takes longer than a clean restart. (For similar reasons, the TDM engine itself needs to be restarted completely when you install a FM.) DR is able to make that leap while keeping the same process alive, but it's a very expensive step, and it's better to restart to clean up any resources that are left behind when switching configs (for instance, all defs that have been loaded from another map/project are kept in memory.)

    From a design perspective, I'd rather not have loading a map implicitly change the whole project setup. At some points it might not be deducible or even wanted to have the paths changed on map load.

    When regularly switching between projects, a possible help might be to create separate DarkRadiant shortcuts, passing the FM project path as argument to DarkRadiant.exe.



    • Thanks 1
  3. 4 hours ago, datiswous said:

    This issue still remains in 3.6 (under Linux) . If I remember correctly this doesn't happen in Windows (10). Should I create a bugreport in the tracker?

    Since it only affects the Model Selector window, I might have fixed that a few commits back. The Model Selector didn't have a parent window set (since it is initialised very early during startup), that's why it had also been possible to focus on the main window even with the Model Selector open.

    • Like 1
  4. 1 hour ago, cvlw said:

    Usability:  the windows risk docking quite aggressively even if not intended.  I am liking that the properties parent window holds all of these child windows in one place rather than in separate windows.  Perhaps make docking the parent Properties window optional?  I like moving this window around and even moving partially off the screen if I don't close it.  If I move it too far in any direction, it gets sucked into a dock.

    Not much I can change about the docking "magnetism", but as a workaround you can hold down Ctrl or Alt to prevent docking of moved windows.

    1 hour ago, cvlw said:

    Actual bug:  the sizing of the objects within the Entity window (N key) resets when closed and needs to be dragged back out every time it is opened.  This is the area shown in the attached screenshot.

    That should go to the bugtracker please, then I'll look into it for the next release.

  5. On 11/8/2022 at 12:00 AM, joebarnin said:

    However, I did notice something in this version of DR. The Camera view does not behave as expected. Examples:

    • In Camera view, the ESC key no longer deselects. In ortho views, ESC deselects fine, but in the Camera window, it doesn't do a thing.
    • Undo doesn't seem to redraw in the camera window either. 
    • Selecting an object in ortho view doesn't highlight it in the camera window.

    Are these known issues?

    I can't reproduce this. Anything you need to do before this happens? Any layout/camera adjustments that I might not have on my end?

  6. On 11/10/2022 at 2:31 AM, thebigh said:

    I've been having trouble getting version 3.5 to run properly on Linux. As of a few updates ago, it takes up to ten minutes to start, equally long to load even the smallest map, and then lags like crazy in the 3D view. Quitting DR takes another few minutes and then it leaves keyboard input suppressed entirely- I need to log out to be able to so much as type into a terminal again. I'm not sure what I'm doing wrong here. I'm running on Linux Mint 20.2 Uma 64-bit, MATE 1.24.0.  DR isn't producing any log files or giving me any error messages that might help me figure out what's going on.

    10 mInutes, seriously? Any hint on when this started to happen? Everything else is working without lag, once it finally started?

  • Create New...