q3map2.x86(2.5.9 or above) oddness

(QESTUDENT) #1

Its size is odd(much bigger than previous ones).
To make matters worse, it runs slow!
Please explain why!? :banghead:

(obsidian) #2

2.2.0-b14-pr ~300 KB
2.5.7 ~420 KB
2.5.8 ~410 KB (actually got smaller)
2.5.12 ~450 KB

Naturally, you can expect Q3Map2 to get larger, there is, after all new code that needs to be included. Overall, it’s file size increase has been minimal - we are, after all, talking about kilobytes and not megabytes. Some of the later versions do require some additional .dll files that were included in the zip. This accounts for some additional file size increase (marginal) of the zip file.

In terms of running slower, are you benchmarking it using the same map, same system, same shaders, same compile options? You’ll have to explain how you’re getting slower results. Overall, I’ve found the latest versions faster.

(QESTUDENT) #3

In terms of running slower, are you benchmarking it using the same map, same system, same shaders, same compile options? You’ll have to explain how you’re getting slower results. Overall, I’ve found the latest versions faster.

Yes, of course.
The sample map, museum.map, takes about 2 times longer to be baked at light stage, with the same switch on the same pc. :disgust:
If you have both 2.5.9 or above and below, please try.
It’s apparently noticeable.
This is a comparison of 2.5.9 (or above) with 2.5.7 which was recommended lately by the moderator at quake3world.

Please note the main topic here is “Why the size has suddenly grown up!?” :bash:
Please don’t ask me why the latest or newer version is needed.

BTW, I’m talking about q3map2.x86, not q3map2.exe.
(x86 is intended to be an extension)

(QESTUDENT) #4

Com’on!
Why!?
Why!?
W
h
y ! ? :banana:

(michi.be) #5

where is the problem? the newer versions are only some kb bigger.
and in newer versions the compiler have more to calculate because the code is better.

good things need time to complete. :wink:

(ydnar) #6

  1. If someone offers help, don’t insist on ramming your specific topic down their throat, especially when you mention multiple issues in your initial post.

  2. Do not throw a tantrum.

While I know what you mean, you didn’t specify you were using Linux.

Newer versions have different libraries and substantially more code. Lightwave support is statically linked in, for instance.

What are the exact compile options you are using and the full logs of the two compiles?

If you want, you can try a development build of 2.5.13 available here: http://akiba.shaderlab.com/GtkRadiant/install/q3map2.x86

y

(QESTUDENT) #7

where is the problem? the newer versions are only some kb bigger.
and in newer versions the compiler have more to calculate because the code is better.

Yes, the latest q3map2.exe ran faster also on my pc with the same map & option.
Just a few seconds, but definitely happy. :moo:

  1. If someone offers help, don’t insist on ramming your specific topic down their throat, especially when you mention multiple issues in your initial post.
  2. Do not throw a tantrum.
    While I know what you mean, you didn’t specify you were using Linux.

Yes, sir.

Newer versions have different libraries and substantially more code. Lightwave support is statically linked in, for instance.
What are the exact compile options you are using and the full logs of the two compiles?
If you want, you can try a development build of 2.5.13 available here: http://akiba.shaderlab.com/GtkRadiant/install/q3map2.x86

:blah: :frowning: :blah:

(ydnar) #8

This is going nowhere. I’m closing this thread. If you’d like to try again in a reasonable manner, be my guest.

y