jonri

I found light/Renderables.cpp and was able to hard-code in an alpha value, I mostly like it: The intersection with another translucent material got a bit wonky, but that's not totally unexpected. I tried to set the alpha on the colour variable in RenderableSpeakerRadiiFill::generateSphereVertices but it didn't seem to have any effect. @greeboany idea why that one would be different? At a first glance, the rendering code looked very similar for the light and speaker gizmos.

The "MD5 Animation Viewer" from the Entity menu is my go-to. I don't know of any lists in the wiki or anywhere else.

The lights are a LOT easier to find now compared to the wireframes, but being fully opaque also blocks your view of smaller model lights. Making them solid but translucent might be a nice compromise, although you wouldn't see the true color of the light any more. Same with the sound sphere, but without the downside. Would this be hard for me to try myself?

Adding the property isn't the hard part, figuring out the right value is I had an idea in the back of my mind for a feature, it would be nice if the anim property had a button to open the animation dialog so you could preview and then select the one you wanted.

I've noticed that light and sound markers are now opaque, is this a bug or a feature?

I've noticed the anim property missing on path_anim nodes.

I confirmed my new loot counter script still works and dropped it into Github so it'll ship with the final release. I'll be spending some decent mapping time this weekend on Linux, so I'll keep up with the master branch and be able to test any additional fixes.

You sure you don't have an old glprogs hanging around? I did that to myself during the 2.10 betas and it looked just like that.

I finally got a chance to update the script. If you have nothing selected it shows the total loot, and if you have at least one piece of loot selected it will show you both the selected and overall total loot. You can grab the updated script from the exact same place as the original, and if everyone likes this version I'll add it into Darkradiant so it can be available by default when the next version comes out.

I would If it was just a couple days, but since I won't be able to make any additional progress at all until after next week I didn't think it would be fair to ask for that long of an extension. This was entirely my reason for participating as well, and on that front the contest has indeed been a success for me. I'd rather see the finished missions get put out there in time for 2.10 to get the extra testing, and for those who have much more solid entries than myself to get scored fairly. Definitely! With two FMs nearing beta it might even be a double feature!

Unfortunately, it looks like my FM is not going to meet the deadline. We had a pretty big health scare in my family over the course of the past month which has (rightfully) been the focus of most of my free time. Building out this FM has been a nice escape from the stress when I got some free moments, and I'd hoped to scale back and release something beta-quality for the contest that I could polish up later. I got 95% of the way to that goal but won't have any time to get back to this until after next week. Thankfully it's sounding like our situation is going to turn out OK, but I wanted to pop in and wish everyone the best of luck finishing off their FMs.

If you find where your DarkRadiant is installed (i.e. C:\Program Files\DarkRadiant), you'll find a scripts/commands directory. Just drop the .py file in there and it should show up in the Scripts menu.

Here's a little script that totals up the value of all selected loot in your map: https://github.com/jonri/darkradiant-scripts/blob/main/count_loot.py I made it count selected loot only so that I could select sections of my map and get partial totals in order to make sure the amount of loot is balanced across the map the way I want it to be. Of course, you can also select your entire map and get the full total that way. If this script sounds like it would be valuable to others, I'm thinking about the following additions: If nothing is selected, display the total loot in the whole map If there is a selection, calculate and display both the selected and total amount of loot. I'll get back to making a final version after the contest is over, but just wanted to share it now in case anyone else might find it useful for beta testing. If anyone has any feedback, let me know!

This can be done by binding a few commands to your screenshot button. I have done it to give map feedback before, I'll see if I can dig up how I did it later... ...and here it is: bind "KP_SLASH" "con_noprint 0;wait;wait;wait;getviewpos;wait;wait;wait;screenshot;con_noprint 1" I bind all my various development commands to keypad buttons, change the KP_SLASH to whatever you'd like.

Could you use particles just to mask the seam in your transition area? I had some success in my current map doing this for some fogged-out geometry that was showing against the skybox at a distance, not sure how well it would do up close though. Maybe spilling a volumetric light out of your foggy area and over the seam would help mask it. I haven't had the occasion to try it, so it may or may not help at all.

It is supposed to point to the material name (which might be different from the texture name). In this case, I think you want "wbottle01": Instead of hacking the exported file, you can also name your material in Blender the same as the TDM material, and it will be exported correctly. The only time this causes a problem is if the TDM material name is too long for Blender to handle (it has a 64-character limit IIRC).

I'll make use of however much extension time is decided upon. I think being closer to the 2.10 release makes sense, maybe add the month of January to the contest. This would still leave a couple post-deadline weeks before the 2.10 release. If beta testers for the contest maps shake out additional bugs that get fixed during January, it might work out that an official beta or release candidate build could be timed to coincide with the contest deadline.

I'm really digging the cabinet1 extension pack, the new pieces really tie the room together! With one month left in the challenge, I'm not sure I'll get everything the way I want it, but I'm aiming for at least beta quality with the primary objectives.

Thanks, not sure how I missed it. It's right there when you check "Show inherited properties" in DR...

While I'm here, does anyone know if there is a way to set the phase of a func_pendulum? I have some things I want to be out-of-sync with each other. If there's no direct solution, I could probably set the speed to be slightly different on each one and they should get sufficiently jumbled up by the time the player gets there.

If you select your light and go into vertex mode (hit "v"), you can set the origin of your light to be off-center. You can then place the light such that the origin is near your wall and the entirety of the light volume is where you want it. The downside is that the center of the falloff texture does not get moved to your new origin, so you might need to make a new one for things to look right. If you're not quite sure what I mean, build a little test room where you can compare a regular light to one with a moved origin. I ended up making a texture like this: And since I reused this light a bunch of times I made an entitydef for it with this falloff texture and the origin already at the correct offset.

It does OK a lot of the time, the two exceptions I found are textures with both light and dark sections being used as trim sheets, and metal textures that are probably right around that 50% mark: I think a button next to the light/dark modes to toggle auto-detection would be perfect, so you can temporarily disable it while you're working with such textures. I'll add 2 feature requests to the tracker.

I'm really enjoying using the improved Texture Tool, and I've noticed a few other minor polish items: The selection of dark/light mode gets lost when you deselect and select a face. This one actually can get annoying if you're texturing several faces with something that's only usable in the opposite mode, or selecting/deselecting/tweaking something several times to see how it looks. There doesn't seem to be a limit on how far you can zoom in or out. Not a practical issue but I'm not sure how far you would go before crashing or getting side effects from a lack of precision. You already took care of the grid not getting small enough, thanks for anticipating this one If you're considering additional features, having a free scale button that lets you drag the corners to scale might be easier than using the panel on the right side in some cases, and it would complement the free rotate feature.

Given the great work on the texture tool in 2.14 lately, I wanted to ask about something with texturing patches that I run into from time to time: Sometimes you want the texture to flow around the corner of a patch (the default, and the left half above), but sometimes you'd rather have it flow with the surrounding geometry (right half). This is possible to take care of manually, although in this case it's cumbersome to separate the UV vertices that are on top of each other: Is there a way to easily match the UVs up with the patch geometry in this fashion? Basically a cross between UV projection from a 3D modeler and the "Natural" button. Such a button would be a nice addition EDIT: Since trying this in DR 2.14, it seems like a regular (non-natural) paste does this. I swear I had tried everything in the past to make this work, have there been any fixes in the past couple versions or am I just dumb?

The backstory to my still-WIP warehouse FM contains a few loose connections already, so I've decided to flesh it out a little more and turn the story into its own little FM for the challenge. I've given myself a cap on the number of "rooms" to avoid feature creep, and I'm about 80% done with the blockout. Hopefully the deadline will help me push this one over the finish line, plus having a prequel will let me cut back on the intro and readables in the following FM.