Testers needed: DarkRadiant + wxWidgets

[SteveL 1042]

I've installed the new one. Updates on prev issues:

• Lighting preview is now working
  
• The camera view window placement is partially fixed. The size is now remembered, but it's still being moved from my second monitor back to the main one. I notice that size and position are restored ok if I place it on the main monitor.
  
• Keyboard shortcuts are still being wiped when changing between 1.8.1 and 2.0. Lots get replaced with "VoidSymbol".
  

I spent a few hours last night doing some intricate patch work in 2.0. It all worked splendidly, and I have only 1 new issue to report. I'll report back with a list of dialogs that I used extensively later so that you can add them to the "tested" list.

 

That new issue: the Media browser usually doesn't show any previews if you have nothing selected when you click on a new texture name. You get a blank grey square. Sometimes I'm seeing odder behaviour:

The bottom 30% only of each texture preview is being shown in the top 30% of the preview pane. And it's slightly displaced to the left, leaving an empty grey stripe to the right of the preview panel. This only happens when I've got nothing selected. When I select an object in the map and click on a new texture, it corrects itself and shows the full preview properly positioned, so the workaround is easy enough.

 

I'll file a report.

Edited July 20, 2014 by SteveL

[SteveL 1042]

I've just crossed out the line above on keyboard shortcuts. I only just read your message from this morning on the tracker issue, to the effect that changing from 1.8.1 to 2.0 is supported, but not the other way round. My problem this morning was caused by going back and forth.

 

I just refreshed the 1.8.1 file and then opened and closed DR2 a couple of times, to simulate an upgrade from 1.8.1. I can confirm that that works fine now: the main shortcuts listed above are stable. I did lose at least one custom binding (CTRL+\ for SelectionModeGroupPart), but that's no big deal.

[greebo 29]

In the input.xml you sent me, there's no shortcut is assigned to "SelectionModeGroupPart". Can you send me the one with Ctrl-\ assigned?

[SteveL 1042]

Hmmm. I just checked it and you're right. Which is a complete mystery, because that file is the unchanged since I backed it up before my 2.0 install, and I use that shortcut frequently. But it must have gone missing prior to the install. I've mainly been using DR for LOD testing in the last couple of weeks, not modelling, so it could have got reset a few days earlier somehow.

 

I'm completely confused about how that happened, but I did just try it again by pasting in the line from a previous backup and it did get wiped out when I opened 2.0pre2. Here's the line from my previous backup:

<shortcut command="SelectionModeGroupPart" key="backslash" modifiers="CONTROL"/>

 

after opening DR2, the line is changed to:

<shortcut command="SelectionModeGroupPart" key="" modifiers="CONTROL"/>

[greebo 29]

OK, thanks, I've added "backslash" to the mapping.

[nbohr1more 1883]

Light preview now works but the z-fighting artifacts still exist. I'm hesitant to open a tracker on this since it's not reported

elsewhere and I have a crappy Intel GPU at the moment. That said the latest 1.8.1 build does not have this artifact problem...

[SteveL 1042]

... the z-fighting artifacts still exist.

Could you try opening up a published fm so we can compare screenshots?

The only z fighting I have seen is with clip textures where they exactly coincide with visible surfaces.

[nbohr1more 1883]

I'll try to grab a screen tonight. Z-fighting is everywhere. Clip textures, vertex blend transitions, alpha transitions, etc. As you move around you see striped what look like

animated stripes scrolling across surfaces. If it works properly for ATI and Nvidia cards then I really feel bad about prompting any further investigation since we all know

that Intel's OpenGL compliance sucks and Greebo (et al) should not be forced to use legacy render methods to overcome these shortcomings.

[nbohr1more 1883]

OK, I've attached a screen.

 

It seems that this can fairly be narrowed down to transparency behavior, as this may is mostly devoid of the artifacts except

where Biker used some extra grime decals.

[SteveL 1042]

I love that you can now minimize the camera view independently of the other DR windows. No more having to readjust the camera window or constantly alt+tab when trying to copy spawnargs from a web page into DR

[greebo 29]

The next pre3-build is being uploaded as I type. See the first post for linkage and the bugtracker for changelog.

[nbohr1more 1883]

Any chance that 0002350 (blendLight render) gets into this release since there are currently some bugs around positioning these in combined entities?

[greebo 29]

Combined entities aren't shown correcly in DR in the first place, are they? Anyway, I can look into it briefly, but I haven't touched any rendersystem code for a long time now.

[greebo 29]

Ok, I screwed up big time with the pre3 build, I introduced two major problems. While fixing the MediaBrowser preview I messed up the context-specific texture bindings - textures will be mixed up in the camera view even though the user selects the correct one in the MediaBrowser.

 

Also, Refresh Shaders doesn't work when a map is loaded, because it's disallowed to call glBindTexture from a thread, it appears.

 

I have to think about how to fix these two while keeping the benefits of the changes.

[greebo 29]

Ok, new build is being uploaded, forget about pre3, use pre4 instead.

[SteveL 1042]

Here's another minor but weird one. I'll post a pic here since I haven't found out how to do it on the tracker. I thought it was impossible tbh until I saw grayman do it last week. Anyway, the entity inspector misaligns the team spawnarg:

[Bikerdude 3736]

Downloaded pre4

1. As per the latest build of 1.8.1 there is a delay and then a stutter for while if you look around in camera view.
   
2. This may have been reported already but, loading a lap takes a very long time (2x as long as 1.8.1) and when shutting down DR looks like its doing a save and taking as long to shutdown as it did to load the map it opened.
   

[grayman 2695]

I haven't been using these new beta versions, but I found a problem that appeared between pre1.8.1 and 1.8.1.

 

Here's the thread.

 

And here's the tracker issue for it.

[SteveL 1042]

The texture tab has got a bit broken in the latest fixes. When I switch between tabs and switch back to the texture tab, it'll often make the texture previews very small. Sometimes the grid of preview panels will slip partly out of the viewable area, like the preview pane in the media browser did before. But the mouse-click detection still thinks the preview panels are big and placed centrally. When I right-click blank grey areas of the texture tab, I see the names of textures that *should* be there.

 

Plus, only a minority of the textures will paste to my selected patch. The same textures that won't paste from the browser won't paste using CTRL+MMB either, so I'm possibly stumbling on 2 unrelated issues here. Other textures will paste ok.

 

I'll file a tracker issue if I can isolate any of the behaviour and come up with a coherent report.

 

Edit: And the previous bug pictured above, media browser with displaced texture, is still happening.

[greebo 29]

Here's another minor but weird one. I'll post a pic here since I haven't found out how to do it on the tracker. I thought it was impossible tbh until I saw grayman do it last week. Anyway, the entity inspector misaligns the team spawnarg:

Fixed in source.

 

Downloaded pre4

1. As per the latest build of 1.8.1 there is a delay and then a stutter for while if you look around in camera view
   

Are you talking about 2.00 or 1.8.1? Is this right after map loading or anytime you switch into camera freelook mode?

 

This may have been reported already but, loading a lap takes a very long time (2x as long as 1.8.1) and when shutting down DR looks like its doing a save and taking as long to shutdown as it did to load the map it opened.

Which map and what size are we talking about exactly? On shutdown (even in debug builds), I can confirm that the brush counter is going down to 0, but this doesn't take near as long as loading the map, so I don't experience it as bad as you. After that brush-count-down step DarkRadiant quits pretty much immediately.

[Bikerdude 3736]

Which map and what size are we talking about exactly? On shutdown (even in debug builds), I can confirm that the brush counter is going down to 0, but this doesn't take near as long as loading the map, so I don't experience it as bad as you. After that brush-count-down step DarkRadiant quits pretty much immediately.

Its happening on ANY large map, in this example my WIP map (thief - 15Mb, 12k brushes, 4k patches, 3.5k entites) in the beta mapper folder. Also I have noticed the additional delay is being caused direcly before you get the 'loading shaders popup', you see a load of counting hapening in the "brushes : patches : entites" box. And you see this same counting activity after closing DR.

 

And I was refering to 2.0 in comparison to 1.8.1

[Bikerdude 3736]

Some more feedback on the interface wqith a comparison between 181 & 20p4

 

 

[IZaRTaX 27]

Hello, i have a problem in 2.00 pre alpha version, i use windows layout "regular" :

 

for this sreen i use version 1.8.1 (work good)

 

but in 2.00 impossible to open media browser in windows layout "regular", work only for windows layout "regular left" (default) .

[greebo 29]

Hello, i have a problem in 2.00 pre alpha version, i use windows layout "regular" :

 

for this sreen i use version 1.8.1 (work good)

 

but in 2.00 impossible to open media browser in windows layout "regular", work only for windows layout "regular left" (default) .

I can confirm that the GroupDialog is not showing when trying to switch to the EntityInspector or the MediaBrowser in "Regular" layout. Can you please add an entry to the bugtracker, I'll check it out.

[own3r 0]

I've noticed that since 1.8x and the switch to VC++12, I have not been able to get darkradiant to start on XP SP3, investigating.

 

I have VC++12 and 13 installed as well as various windows sdks

 

EDIT:

It appears to be a solvable problem with VC++12 and "multitargeting" xp and later versions of windows, see here:

more details are here:

http://stackoverflow...754251#14754251

 

Filing a bug report.

Edited August 6, 2014 by own3r