Jump to content
The Dark Mod Forums

Pre-Release Test - DarkRadiant 1.4.0


greebo

Recommended Posts

I'm looking for some pre-release testers again, for the next DarkRadiant 1.4.0 feature release. Anybody interested?

 

Changelog for DR 1.4.0 so far:

 

- 0002311: [GUI] Jump to selected sound (if any) upon clicking Choose Sound (greebo) - resolved.

- 0002300: [Renderer] blend blend images not displaying (greebo) - resolved.

- 0002305: [Map Editing] Some Coord settings not updated realtime for Patch Inspector (greebo) - resolved.

- 0002313: [Map Editing] Seek strings within property names (greebo) - resolved.

- 0002224: [selection System] Separate selection mode to pick a specific item part of a func_static (greebo) - resolved.

- 0002301: [Design/Coding] Update Win32 libxml2 libraries to 2.7.7 (greebo) - resolved.

- 0002299: [GUI] EClassTree too wide in multi-monitor setup (greebo) - resolved.

- 0002295: [GUI] No easily noticable feedback on failure to load a map (greebo) - resolved.

- 0002278: [Map Editing] EntityInspector chooser plugin for selecting vocal set (greebo) - resolved.

- 0001715: [Map Editing] (Non-)case sensitivity of entity property keys (greebo) - resolved.

- 0002267: [Design/Coding] Crash at shutdown in SpeakerNode (greebo) - resolved.

- 0002139: [selection System] Save selections (greebo) - resolved.

- 0002251: [Design/Coding] DR 1.3.1: Any items dragged snap back to original location (greebo) - resolved.

- 0002285: [Map Editing] Rare crash when drag-creating brushes (greebo) - resolved.

- 0002286: [Map Editing] Thicken patches function produces distorted result for bevels (greebo) - resolved.

- 0002289: [GUI] View doesn't update when manipulating patch control vertices in PatchInspector (greebo) - resolved.

- 0002277: [Design/Coding] A couple of gcc warnings (greebo) - resolved.

- 0002279: [Renderer] Snow patch and Moonbeam texture see-through: (orbweaver) - resolved.

- 0002293: [scripting] Support nicer menu titles for script commands (greebo) - resolved.

- 0000620: [General] Transparent speaker volumes (greebo) - resolved.

- 0002292: [Renderer] Add support for rendering entity boxes as transparent (greebo) - resolved.

- 0002290: [GUI] Crash in PatchInspector after removing Patch control vertices (greebo) - resolved.

- 0002048: [Design/Coding] Expose OrthoContextMenu to plugins (greebo) - resolved.

- 0002288: [Map Editing] Crashes in debug builds when transposing patches or selecting degenerate ones (greebo) - resolved.

Link to comment
Share on other sites

Here's the pre1 version:

 

32 bit: http://www.dramthethief.com/darkmod/files/darkradiant/darkradiant-1.4.0pre1.exe

64 bit: http://www.dramthethief.com/darkmod/files/darkradiant/darkradiant-1.4.0pre1.x64.exe

 

Thank you for testing.

Edited by greebo
fixed links, thanks Sneaksie
Link to comment
Share on other sites

Wow. Selection mode group/part is awesome. Trying to figure out the selection sets... don't see a menu item or shortcut yet; still looking.

 

Edit: figured it out -- you just type in the name. Coolness. Would be great if you could delete individual entries instead of all at once, and if they could be saved to the .darkradiant file :) (realizing that it was stated as "first unpolished version").

 

Edit: little issue with select group parts mode -- when in it, you can't select anything that's not part of a group (e.g. a simple worldspawn brush). Not sure if that's a bug, or a feature. Thought selection mode was broken for a few there till I realized that's what was going on.

Link to comment
Share on other sites

Edit: figured it out -- you just type in the name. Coolness. Would be great if you could delete individual entries instead of all at once, and if they could be saved to the .darkradiant file :) (realizing that it was stated as "first unpolished version").

Yep. It's a first rough version, but it's working fine for me so far. Did you find the mouseover help? I added a few instructions there for starters.

 

Edit: little issue with select group parts mode -- when in it, you can't select anything that's not part of a group (e.g. a simple worldspawn brush). Not sure if that's a bug, or a feature. Thought selection mode was broken for a few there till I realized that's what was going on.

Yes, that's intended behaviour. It enables you to drag-select multiple parts of a group, without selecting the entire worldspawn stuff behind the group.

Link to comment
Share on other sites

well as I am spending atleast 3hrs+ a day on DR Im gonna have a play with this also.

If you're going to use this for "production maps", please be sure to create regular backups of your work. It's not impossible that there is a critical bug in the pre-release packages.

 

The see-through decals are now fixed (yaah!) but brush joint lines are still visable (booo!) - http://bugs.angua.at/view.php?id=2250

Well, I don't have time to fix all issues on the tracker, I can only address a few of them each release. Maybe next time.

Link to comment
Share on other sites

I have been using the smnapshots feature of DR since 1.3.0 so no worries there. Should i go back to 1.3.2 then or will 1.4.0 hit release before the Summer deadline.?

 

Apologies for coming across as a child Greebs, I appreciate there is only so much time you have for TDM/DR etc.

:blush:

Edited by Bikerdude
Link to comment
Share on other sites

Should i go back to 1.3.2 then or will 1.4.0 hit release before the Summer deadline.?

If everything goes well, DarkRadiant 1.4.0 is out sometime next week, I guess. Depends on the amount of (critical) bugs surfacing in these pre-releases and how much time I'll have during the evenings.

Link to comment
Share on other sites

I took a copy of the pre-release.

 

I can verify that the "looking through a snow texture" bug has been fixed.

 

And thickening patches works correctly now.

 

Greebo, you want us to close issues now, or wait until the official 1.4 release?

 

Thanks!!!

Link to comment
Share on other sites

Greebo, you want us to close issues now, or wait until the official 1.4 release?

Feel free to close the issues as you confirm them as resolved. I'm not going to change the corresponding code before the actual release 1.4.0 so this step can happen right now as well, in my opinion. If anything breaks again, the issue on the tracker can be reopened any time.

 

Thanks for testing.

Link to comment
Share on other sites

Looking good from my side, playing with new features is going well and haven't spotted any regressions.

Will start looking through confirming fixes later :)

 

The selection set field is a bit fat, vertically... but functionality is great, would like a way to remove just a single set rather than cleaning all of them tho :)

Link to comment
Share on other sites

When I right-click during dragging (brush or item), the object goes back to its start position immediately, and the drop-down menu that you get when you right-click appears.

 

Ditto for resizing brush sides.

 

Is this the expected behavior?

 

I was expecting the right-click to be ignored.

Yes, the behaviour is intended. It was the easier solution, as detecting an ongoing drag operation is more complicated for the XYWnd class.

Link to comment
Share on other sites

A different problem re: weather patches and skyportal.

 

When you select a rain patch, it tints, the wording disappears, and any skyportal brushes beyond it disappear.

 

When you select a skyportal brush, it tints, but you can now see through it.

 

For the images below, #1 is normal, #2 is with the rain patch selected, and #3 is with the skyportal brush selected. You can see the skybox out in the void in #2 and #3.

post-3633-127955137489_thumb.jpg

post-3633-127955141181_thumb.jpg

post-3633-127955142719_thumb.jpg

Link to comment
Share on other sites

When you select a rain patch, it tints, the wording disappears, and any skyportal brushes beyond it disappear.

 

When you select a skyportal brush, it tints, but you can now see through it.

 

For the images below, #1 is normal, #2 is with the rain patch selected, and #3 is with the skyportal brush selected. You can see the skybox out in the void in #2 and #3.

Is the problematic shader a "blend blend" material? I recently fixed (yet) another transparency rendering issue with blend blend materials, and it's possible that this broke something else?

Link to comment
Share on other sites

Is the problematic shader a "blend blend" material? I recently fixed (yet) another transparency rendering issue with blend blend materials, and it's possible that this broke something else?

 

Sample rain shader from tdm_weather.mtr:

 

 

textures/darkmod/weather/rain_drizzle

{

deform particle2 tdm_rain_drizzle

qer_editorimage textures/editor/rain

nonsolid

noshadows

{ //needed to emit particles

blend filter

map _white

}

}

 

The sky_portal shader from tdm_portal_sky.mtr:

 

 

textures/smf/portal_sky

{

qer_editorimage textures/editor/portal_sky

forceOpaque // will still seal levels

noshadows

noimpact

sort portalSky

 

{

map _currentRender

 

clamp

screen

 

// fix up the projection based on the screen coords

translate global6 * 0.5, global7 * 0.5

scale global6 * 0.5, global7 * 0.5

}

/*

{

vertexProgram portalSky.vfp

fragmentProgram portalSky.vfp

fragmentMap 0 _currentRender

}

*/

}

 

So rain has a single blend, but sky_portal has none.

Link to comment
Share on other sites

Ok, so to get everything right: the issue at hand is a regression (it had worked before), or is it a new problem or a problem that has always been there?

 

And it does only affect selected faces, doesn't it? Unselected faces are looking ok?

Link to comment
Share on other sites

Hm. I seem to have lost track of the status of the various transparency issues. I recently fixed the blend blend images appearing black, but I don't know if this was the revision where the regression occurred. Maybe it's related to the other things (snow textures see-through, moon etc.).

 

A testmap with all possible and problematic shaders would be nice, if someone is interested in doing that.

 

Apart from that, do people agree that this pre1 version is good to go? I added one more bugfix to 1.4.0 that is not included in the pre1 package (http://bugs.angua.at/view.php?id=2284) but this shouldn't have any negative effect.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Recent Status Updates

    • taffernicus

      i am so euphoric to see new FMs keep coming out and I am keen to try it out in my leisure time, then suddenly my PC is spouting a couple of S.M.A.R.T errors...
      tbf i cannot afford myself to miss my network emulator image file&progress, important ebooks, hyper-v checkpoint & hyper-v export and the precious thief & TDM gamesaves. Don't fall yourself into & lay your hands on crappy SSD
       
      · 2 replies
    • OrbWeaver

      Does anyone actually use the Normalise button in the Surface inspector? Even after looking at the code I'm not quite sure what it's for.
      · 7 replies
    • Ansome

      Turns out my 15th anniversary mission idea has already been done once or twice before! I've been beaten to the punch once again, but I suppose that's to be expected when there's over 170 FMs out there, eh? I'm not complaining though, I love learning new tricks and taking inspiration from past FMs. Best of luck on your own fan missions!
      · 4 replies
    • The Black Arrow

      I wanna play Doom 3, but fhDoom has much better features than dhewm3, yet fhDoom is old, outdated and probably not supported. Damn!
      Makes me think that TDM engine for Doom 3 itself would actually be perfect.
      · 6 replies
    • Petike the Taffer

      Maybe a bit of advice ? In the FM series I'm preparing, the two main characters have the given names Toby and Agnes (it's the protagonist and deuteragonist, respectively), I've been toying with the idea of giving them family names as well, since many of the FM series have named protagonists who have surnames. Toby's from a family who were usually farriers, though he eventually wound up working as a cobbler (this serves as a daylight "front" for his night time thieving). Would it make sense if the man's popularly accepted family name was Farrier ? It's an existing, though less common English surname, and it directly refers to the profession practiced by his relatives. Your suggestions ?
      · 9 replies
×
×
  • Create New...