Jump to content
The Dark Mod Forums

DarkRadiant 1.2.1 released


greebo

Recommended Posts

I'm glad to announce the availabilty of the next DarkRadiant version 1.2.1. The most prominent feature in this release is the new Readable Editor, offering a WYSIWYG editor for TDM readables. I don't think I need to stress how cool this is, so I strongly recommend upgrading to the this newest version. Grab it from our project website:

 

Update: DarkRadiant 1.2.1 fixes a recently discovered critical bug preventing the Readable Editor from working properly.

 

http://darkradiant.sourceforge.net/

 

Important: if you haven't installed DarkRadiant before, be sure to install the VC++ 2008 Redistributable Package in order to run this release.

 

The list of changes can be found on the website: Changes since 1.1.0 and on our bugtracker changelog.

 

As usual, please report any bugs or feature requests here in these forums, following these guidelines:

  • Bugs (including steps for reproduction) can go directly on the tracker. When unsure about a bug/issue, feel free to ask.
  • Feature requests should be suggested (and possibly discussed) here in these forums before they may be added to the tracker.

As probably not everybody is reading the changelogs, here it is for reference:

 

New Features / Changes

 

  • New Plugin offering a WYSIWYG Readable Editor for The Dark Mod.
  • New "Reload Selected Models" command
  • New "Merge Entities" command

Bugfixes

 

  • Fixed negative zeros being written to the map file.
  • Fixed: Selecting brushes/entities on linux selects behind first brush/entity.
  • Fixed: Target Connection lines stay behind after deleting entities
  • Fixed: Invert Selection includes worldspawn
  • Fixed: Drag-selecting a func_static can fail
  • Fixed: Crash when moving entire map (in Octree implementation)
  • Fixed: DarkRadiant cannot parse old brushDef maps.
  • Fixed: Crash when undoing create entity from brush "atdm:mover_door_sliding"

Tweaks

 

  • Changed default keyboard shortcut for "Far Clip Plane In/Out"
  • Available scripts are now listed in the main menu

Coding / Internal Design

 

  • BrushTokenIm-/Exporter is now located in the mapdoom3 module
  • Fixed: ModelFileFunctor is using hardcoded model file extensions.
  • Added basic parsing and rendering support for Doom 3 GUIs
  • Win32 GTKGLExt modules are now dynamically linked

Link to comment
Share on other sites

Hooray! Currently compiling it for Ubuntu Karmic 64bit, will upload it to the repository when it is done.

"The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore, all progress depends on the unreasonable man." -- George Bernard Shaw (1856 - 1950)

 

"Remember: If the game lets you do it, it's not cheating." -- Xarax

Link to comment
Share on other sites

Update: DarkRadiant 1.2.1 fixes a recently discovered critical bug preventing the Readable Editor from working properly. All users of 1.2.0 are encouraged to download the update.

Link to comment
Share on other sites

Hooray! Currently compiling it for Ubuntu Karmic 64bit, will upload it to the repository when it is done.

 

"...when it's done."

 

Updating the repo would be really nice. 32bit also. Lamers like me (who are too lazy to bother with compiling) are still stuck with 1.1.0 -- the one with the show-stopping selection bug. :(

Link to comment
Share on other sites

"...when it's done."

 

Updating the repo would be really nice. 32bit also. Lamers like me (who are too lazy to bother with compiling) are still stuck with 1.1.0 -- the one with the show-stopping selection bug. :(

 

Yeah, sorry, but DR doesn't compile here under Linux - I posted the error somewhere else. Unfortunately I neither have the time, the skills nor the access to DR SVN to fix the problem - all I can do is hit "compile" and wait to see if it finishes.

"The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore, all progress depends on the unreasonable man." -- George Bernard Shaw (1856 - 1950)

 

"Remember: If the game lets you do it, it's not cheating." -- Xarax

Link to comment
Share on other sites

Thanks for the big support greebo, angua and others. I always find Dark Radiant very user-friendly from the begining and you still update & develop it. However, as you can guess after this much appreciation I have a trouble with it. For some reason I can't play sound files while I'm choosing from the list. I have to try "play" many times to hear them. I checked last version and still same. Is this a known bug?

Link to comment
Share on other sites

For some reason I can't play sound files while I'm choosing from the list. I have to try "play" many times to hear them. I checked last version and still same. Is this a known bug?

Nope, works fine on my end here. DarkRadiant is using OpenAL to play those sounds, maybe your sound driver doesn't fully support that API(?).

Link to comment
Share on other sites

  • 2 weeks later...

I just DL'ed DR 1.2.1.

 

I had a number of readables before the Readable Editor came out in 1.2.0. The Editor read them just fine, and I could change them, but I had a problem in that no text was displayed in the preview window.

 

I assume this is the bug that was fixed in 1.2.1.

 

However, when I bring up the 1.2.1 Editor on an existing readable, DR crashes. I tried it with two different readables; one I created prior to 1.2.0 and one I created using 1.2.0. Both crashed while trying to paint the Editor window.

 

I tried to create a new readable using 1.2.1, and got as far as typing in the text. At the first character, DR crashed.

 

So I assume the crash is related to displaying text in the text field (not in the Preview window).

 

Anyone else having this problem?

 

Thanks.

Link to comment
Share on other sites

Found a new problem that effects DR and the latest nVidia gfx driver (197.xx)

 

Got back home, fired up the main PC and DR was coming up blank where the grid should be I've uninstalled and was unresponsive. I wiped the prefs folder, rebooted and reinstalled and it still did the same thing. I checked that I had VC++2008 sp1 installed etc.

 

Fix attempt 1: I went back to a previous ghost backup of windows, ad thought it was a system service that i had switched off......

 

Fix attempt 2: It was actually a setting in the latest nVidia gfx driver(197.xx) that was causing the problem - "Threaded optimization" and this needs to be set to off. Leaving the setting on default (Auto, or On) causes DR not to load correctly and you get what I like to call the "white screen of death" or WSOD...... Yet the same setting left on default on previous driver versions was/is fine, e.g. Vista Sp2 and Forceware 176.44 on my laptop had no problems at all.......................

 

.............................

Edited by Bikerdude
Link to comment
Share on other sites

  • 2 weeks later...

I'm looking for some volunteers for a DarkRadiant pre-release test (the upcoming version 1.2.2). Jdude reported that the new version is crashing occasionally when vertex-editing brushes and patches, but so far I couldn't reproduce it. I'd be interested in more testers to see whether this problem is happening more than once.

 

Let me know if you're interested.

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

    • 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
    • nbohr1more

      Looks like the "Reverse April Fools" releases were too well hidden. Darkfate still hasn't acknowledge all the new releases. Did you play any of the new April Fools missions?
      · 5 replies
×
×
  • Create New...