I`m not a n00b but I do NEED help

(ratty redemption) #1

I`m having a few problems with the gtkradiant 1.4 release for q3, wolf and et.

I decided I better use the latest "stable" version for any tutorials I make but the surface inspector doesn`t work the way I`m used to in gtk 1.2.13

namely when I point the cursor at a tex in the cam window and use the middle mouse button, it used to copy the name and path of the tex, and it`s shift, scale and rotation info into the surface inspector, which would stay on top of the main gtk window... now it gets moved behind the main gtk window and if I go down to the task bar and bring it to the front the surface inspector is empty.

but the patch properties window stays on top and shows all the info from a current selected patch... so I`m wondering if there is a bug in the surface inspector?

also I know the tex info is being copied, although not displayed because if I then alt+shift+middle click, then it will paste the copied tex including it`s alignment, scale and rotation, onto what ever brush face the cam window is now pointing at.

and although minor, can anyone confirm whether the detachable menus toggle works in prefs? ...because what ever I set it to, the damn things will still detach.
(ratty redemption) #2

do all you guys that use gtk 1.4 run it on win xp or linux?

perhaps the new gtk is less unstable when run on win98se?

can someone please confirm this either way?

am I the only one getting this bug? :frowning: :banghead: :blah:

(MindLink) #3

I’m using 1.4.0 on W2k and I can’t really reproduce your problem. I don’t use the surface inspector all to often anyways though.

(ratty redemption) #4

understood and thanx for replying.

I`m planning on getting xp soon, and would still like to hear if any 1.4.0 users with xp get the empty surface inspector?

(Java.Lang) #5

I tried 1.4, but had the same problems, it didn’t work as well as the 1.3s so I went back with the reliable 1.3.8.

(ratty redemption) #6

@Java.Lang, thanx man, now I know it`s not just me

is this the gtk version your using?

can anyone else offer advise on stable non buggy versions later then 1.2.13?

(Shallow) #7

I think this change occured some time late in the 1.3 series, possibly whenever it was they updated the version of the GTK that they were using for Radiant. The surface inspector does what you describe in 1.3.12 at any rate. It hadn’t ever occured to me since I never use the surface inspector that much, but this is a bit of a loss of functionality for anyone that does use it as you do. A shame, since the new inspector otherwise seems a bit better behaved than the old one. You might want to submit a report to bugzilla or post on MapCenter’s GTKRadiant forum.

1.3.8-ET has a surface inspector that should meet your needs in terms of how it behaves, and never gave me any problems.

(ratty redemption) #8

thanx for the info, and do have you a link to the et version of 1.3.8? because the only link I found was a beta 1.3.8 or is that the same?

and although I quite often just copy n paste tex without the need for the inspector, I also do need it working as other times, I check the scaling values, and tex shifting numerically, not just visually.

Im getting a 400 error when I try to use the bug report link in both the 1.2.13 version of gtk and the 1.4 ...dont they even fix their broken links? :frowning:

(Shallow) #9

Bugzilla is here: http://zerowing.idsoftware.com/bugzilla/index.cgi

1.3.8-ET is the official ET tools, there may be a later 1.3 versions that have the surface inspector as you expect but I couldn’t say. The installer program is called wolfet_tool.exe, I haven’t got a direct link on hand but knowing the filename should help you Google it more easily.

(ratty redemption) #10

great thanx again :slight_smile:

and radiant.com have this page… so that is 1.3.8? I dl it and give it a go :slight_smile:

(G0-Gerbil) #11

I have both 1.3.12 and 1.4.0 installed.
I played around a bit in 1.4.0 and haven’t touched it since - the only reason I wanted it was the ‘select surface’ feature of the surface inspector, but once surfaces are selected anything I try to do to them crashes it :confused:
1.3.12 is mostly fine, but I don’t like the new surface inspector, I simply haven’t found a way of copying surface properties from one to another - which is the issue I think you are describing here. Not to say there isn’t a way, but I get damn tired of people changing a well-known and reliable way of doing things :confused:
I’d go back further, but can’t be arsed basically :smiley:

(ratty redemption) #12

thanx for the info Gerbil

but I get damn tired of people changing a well-known and reliable way of doing things

my thoughts exactly.