Brendon Chung

Makes sense! Thanks.

I was wondering if there was a way to make models display differently in DarkRadiant. For example: a model that has specific material settings that make it appear dark/black in the editor (i.e. the material has something like: RGB parm5, or a fire burn effect stage, etc). The model looks fine in-game; but looks strange in the editor due to its various material settings. I was wondering if there was some sort of keyvalue like "editor_displayskin" that would make the model use a specific skin override when displayed in the DarkRadiant editor -- this keyvalue would point toward a 'sanitized' version of the material that makes it appear more correct in the editor.

Got it, thanks for taking a look! I'll make a suggestion in the bugtracker.

Oh! I didn't realize assets.lst could hide .def files. I have assets.lst working for materials, but I can't seem to get it working for .def files: Should assets.lst go into the base\ folder or the base\def folder? I couldn't get it working with either. To clarify, is the documentation in https://www.darkradiant.net/userguide outdated? "Asset paths listed on the left-hand side are interpreted relative to the directory containing assets.lst (which must be models or materials)."

I was wondering if there was a way to prevent an entity type from appearing in the Create Entity list. For example: I'd like to not show the damage_* definitions, as they're not placed in maps and sometimes muddle my search results. Is there some sort of .def keyvalue like: "editor_hidden" "1" (the assets.lst feature to hide deprecated materials/models is very similar to what I'm looking for)

Fantastic stuff!!! Thanks to you all

Got it! Thank you. Our mistake, we were accidentally setting our source control to ignore this file.

Does anyone know where, or what file, that the ctrl+shift+G Selection Groups are saved in? We just noticed that our Selection Groups are not being propagated into our source control -- so if someone creates a Selection Group, a different person is not getting that Selection Group when they get latest data via source control. Wondering if it's maybe a local file, or perhaps not a file, or if we maybe accidentally set our source control to ignore this information.

Thanks! Yup, ctrl+mmb is currently the way I do this. I wasn't sure if some sort of keybind existed for centering the 3D camera.

Is there a hotkey for focusing the 3D camera on the currently-selected entity? Right now you can bring up the Entity List (J), and then click the entity in the list to focus the camera. I was wondering if there was a hotkey to focus the camera on the currently-selected entity, without having to bring up the Entity List. Thanks!

Sure thing -- I created a new item in the bugtracker and submitted it.

Resolved! It turns out that on the machine that didn't work, "Open Map From Project..." was being used to open the map. This was somehow affecting the .lin and autosave functionality. At any rate, using "Open..." resolves the issue.

No problem. I attached the .lin from the computer that doesn't work. @stgatilov - yes, the folder structure is identical on both machines. Additionally, perhaps related (?) -- on the machine that doesn't work, the autosave functionality also doesn't work. test_combat_tworoom.lin

Yes - same game setup on both machines, and same folder structure.

I have two separate computers, and for some reason the pointfile doesn't load correctly on one of the machines. I looked into the .log file, and I noticed this difference: on the machine that works. Here's what it displays when I intentionally delete the .lin file: Command 'TogglePointfile' failed: Could not open pointfile: D:/games/monstergame/base/maps/test_combat_tworoom.lin on the machine that doesn't work. Here's what it displays when it attempts to load the .lin file: Command 'TogglePointfile' failed: Could not open pointfile: maps/test_combat_tworoom.lin On the computer that works, it prints the full absolute file path. And on the machine that doesn't work, it prints a relative path. I don't know if this has any bearing, but I couldn't find anything else pertinent. The only difference between the two computers is that on the machine that doesn't work, it has a partitioned hard drive. Has anyone experienced a similar issue?