DarkRadiant 1.2.2 released

[greebo]

Well I carried on using 1.2.2 and all is fine, so i can only assume it was windows being a shit as I may have been trying to do too many things at once - although I wouldn't call running DR, DM3 and streaming MP3 radio doing to many things at once on my system...

 

Ok. Try to keep an eye open on this, it's possible that it happens again. Next time this occurs, try to remember what steps you did right before it crashed, I need as much info as possible, otherwise I can not even try to reproduce it.

[vlad]

It seems that rev 5542 works good.

 

There is one minor bug:

http://img217.imageshack.us/img217/4271/screendro.jpg

But it's rather old, can be spotted on Windows and can not prevent anyone from map editing.

[greebo]

Yeah, the transparency issue has been there for the last few releases, it will be addressed sometime.

[OrbWeaver]

Is that a relatively new transparency bug, or has it been there from way back? I did make an attempt to get alphatest materials rendered correctly, but didn't succeed. I might have another bash at it some time.

[greebo]

It's the one from way earlier, I think version 0.10.0. It's the draw order which is wrong for alphatested materials, it seems.

[shadow_ibix]

In another (opensource) 3d engine alpha-stuff was solved by having different draw phases. One phase draws all solid materials to set up the Zbuffer, and the next phase draws all alphatest (and alpha without testing as well) in back-to-front (in reference to the screenspace) order. This draws the transparent objects fine (with some exceptions that do not happen a lot unless you make everything transparent; to make even better you'd want the 'stencil type' alpha to fill Zbuffer (a railing) and for 'blend style' alpha to not fill Zbuffer (for glass or fog, its fine to underlap; perhaps with pixel shaders you can make it test and if alpha=99% solid for a pixel then fill Zbuffer)). If the engine uses blend_add and blend_mult apart from simple 'png-style' alpha you can make passes for that as well, so that add and mult and alphablend give the desired color formula; like: alphablend(railings, windows), mult(shadows) then add(fireworks). Anyway, all this complication is not really needed, for an editor, sort back-to-front with the octree and render another pass for the alphastuff with ztest. Sorry if this is too much detail on it

[SiyahParsomen]

Don't know if it's a new bug, but I found out patches of prefabs don't appear in the viewer.

[greebo]

Any filter switched on?

[SiyahParsomen]

no.

[greebo]

Ah, yes. I can confirm that on my end.

 

Please file a bug report about this.

[SiyahParsomen]

Done.

[Komag]

I just upgraded to 1.2.2 yesterday (from 1.0.2, I skipped a few releases), and now DR won't remember my window size/position. It remembers my other settings, such as SplitPane view and having the Cubic clip turned off. Is there anything I can check to fix this?

 

(BTW, I deleted my C:\Documents and Settings\Owner\Application Data\DarkRadiant folder after uninstalling 1.0.2 and a new one was created upon installing 1.2.2)

[greebo]

Maybe it's crashing at shutdown?

 

Is somebody else using Splitpane and able to confirm that?

[OrbWeaver]

In another (opensource) 3d engine alpha-stuff was solved by having different draw phases. One phase draws all solid materials to set up the Zbuffer, and the next phase draws all alphatest (and alpha without testing as well) in back-to-front (in reference to the screenspace) order. This draws the transparent objects fine (with some exceptions that do not happen a lot unless you make everything transparent; to make even better you'd want the 'stencil type' alpha to fill Zbuffer (a railing) and for 'blend style' alpha to not fill Zbuffer (for glass or fog, its fine to underlap; perhaps with pixel shaders you can make it test and if alpha=99% solid for a pixel then fill Zbuffer)). If the engine uses blend_add and blend_mult apart from simple 'png-style' alpha you can make passes for that as well, so that add and mult and alphablend give the desired color formula; like: alphablend(railings, windows), mult(shadows) then add(fireworks). Anyway, all this complication is not really needed, for an editor, sort back-to-front with the octree and render another pass for the alphastuff with ztest. Sorry if this is too much detail on it

 

The DR renderer does use ordered drawing like you mention, and does have code-level support for transparent material drawing. I don't think any substantial re-designing is needed to get this working, it's just a question of tracking down the bug.

[SneaksieDave]

Is somebody else using Splitpane and able to confirm that?

I'm using splitpane, and what it seems to me (and has since 1.02 and perhaps earlier) is that the size settings are not remembered if you're not in fullscreen mode. If you're windowed, you do seem to have to reset sizes on each startup. But that could be a dual monitor thing; read on.

 

I normally use fullscreen only, but have been exposed to this problem because of getting two monitors and flipping sometimes between dual view mode and horizontal stretch mode. Each mode seems to have its own share of problems, either graphic glitches in one or performance issues in the other. DR works best for me (unfortunately -- since I use the other mode the other 99% of the time) in Horiz Stretch mode. I can put it fullscreen, and on each restart, it's restored. But! If I open in dual view mode at all, the settings get messed up, because now my two-monitor maxxed view has been scrunched down to one monitor, so everything's thrown off. Quite a pain in the ass, really, but how to address it (if it's even possible)? Remember two sets of sizes for each layout?

 

Anyway, I'm rambling. In short: yes it seems like in non-maximized view, settings get lost esp on two-monitor systems (I believe Komag does that too). When maxxed, it seems to be behaving for me.

 

Then again... I still sometimes get that no-camera-update-without-explicit-click issue and don't know what to do to fix it. Sometimes it fixes itself through changing modes, sometimes I can't seem to force it to fix. I can confirm the invert patch refresh seems fixed, but earlier today had the issue where I wasn't seeing surface inspector changes until after a separate click (making the inspector basically useless)... so I'm not sure what to say. But I'm going to keep an eye out for the refresh problem. Well, in truth, it'll find me. :-|

 

(This info ^ was using 1.02 and then confirmed with 1.3 beta build from SVN.)

[Komag]

But my 1.0.2 DID remember my size and position when not maximized. (although I don't remember if I had deleted the DarkRadiant folder before I originally upgraded to the 1.0.2 last winter, so maybe some of those files worked differently before and still worked to remember my window size/position and they are actually from an earlier version of DR)

 

I did use dual monitors in years past, but not for a long time now, so in my case it's not that - though I guess it could still be SOMEHOW related, with the ATI Catalyst Control Center (currently showing only one monitor)

[SneaksieDave]

Hm. Well, I'd definitely be in favor of it remembering non-maximized settings, in dual and single monitor setups (if that's possible), because I'd prefer to use dual mode, as in horizontal stretch it (among other issues) puts all of the dialogs (splash scree, save confirm, create entity, etc) dead center in the screen every time.

 

I'll check and see if there's an issue for non-max being forgotten and/or track one.

 

 

Edit: didn't see one. Tracked here: http://bugs.angua.at/view.php?id=2206

[CorwinWeber]

Is there any chance of the Linux version getting into the repository any time soon?

 

Thanks!

[OrbWeaver]

Is there any chance of the Linux version getting into the repository any time soon?

 

Thanks!

 

I'll see if I can make time to build the DEBs in the next few days.

[OrbWeaver]

Lucid packages are up. I will build other Ubuntu versions individually on request.

[CorwinWeber]

Lucid packages are up. I will build other Ubuntu versions individually on request.

 

Thanks, seriously appreciate it. I'm still on Karmic, should the Lucid package work anyway?

[OrbWeaver]

I'm still on Karmic, should the Lucid package work anyway?

 

It probably won't, but I can hopefully build the Karmic package tonight.

[OrbWeaver]

Karmic packages are up.

[CorwinWeber]

Aw, yeah.

 

Upgraded and the new version fixed the media browser issue I was having. Yay! ** happy dance **

 

Thanks!

 

[vlad]

Something is wrong with portal_sky and some other textures in Linux: these textures are black and transparent to entities.

 

 

 

 

 

Edited May 25, 2010 by vlad