Done. The fixed builds are up.Myrd wrote:The last recording bug is a big issue. I've re-uploaded the Mac builds which should no longer experience the bug. Melekor will update the Windows builds later today.
If you've downloaded the older versions, please re-download to have your films work save correctly. Thanks, and sorry for the inconvenience.
Official 1.7 Public Beta Bug Reporting Thread
-
Giant Killer General
- Posts: 32
- Joined: Sun May 03, 2009 12:38 pm
Okay, so here are my system specs:
Operating System: Microsoft Windows XP Professional (5.1, Build 2600)
Processor: Intel(R) Core(TM)2 CPU 6600 @ 2.40 GHz (2 CPUs)
Graphics Card: NVIDIA GeForce 7950
Memory: 2046MB RAM
Direct X Version: DirectX 9.0c
I tried it on OpenGL, still at a pretty consistant 60 fps
I tried finding the VSync option for my graphics card to make sure it was disabled, but I do not know how to find it. I do not think I am getting any limit to my FPS though, because like I said before, under v1.6 I was getting 300+ fps and my graphics card is specifically listed next to Direct3D in the preferences under rendering, as if it was recognizing it and using it.
The max FPS option is NOT enabled.
Tex Cache is set at 20 MB (whatever that is.)
To recap:
My FPS with v1.6 rendering set at Direct3D (NVIDIA GeForce 7950 is 320+ FPS
with v1.6 OpenGL rendering it is 26 FPS
with v1.7 Direct3D rendering (video card not listed here with 1.7) it is 60 FPS
with v1.7 OpenGL rendering it is 60 FPS
Hope this helps.
Operating System: Microsoft Windows XP Professional (5.1, Build 2600)
Processor: Intel(R) Core(TM)2 CPU 6600 @ 2.40 GHz (2 CPUs)
Graphics Card: NVIDIA GeForce 7950
Memory: 2046MB RAM
Direct X Version: DirectX 9.0c
I tried it on OpenGL, still at a pretty consistant 60 fps
I tried finding the VSync option for my graphics card to make sure it was disabled, but I do not know how to find it. I do not think I am getting any limit to my FPS though, because like I said before, under v1.6 I was getting 300+ fps and my graphics card is specifically listed next to Direct3D in the preferences under rendering, as if it was recognizing it and using it.
The max FPS option is NOT enabled.
Tex Cache is set at 20 MB (whatever that is.)
To recap:
My FPS with v1.6 rendering set at Direct3D (NVIDIA GeForce 7950 is 320+ FPS
with v1.6 OpenGL rendering it is 26 FPS
with v1.7 Direct3D rendering (video card not listed here with 1.7) it is 60 FPS
with v1.7 OpenGL rendering it is 60 FPS
Hope this helps.
Hi GKG,
1.7 no longer lists the card name next to D3D in the prefs. That is normal.
The fact that you are getting a consistent 60fps when MaxFPS is not enabled does indicate that VSync is on, as you thought.
One question you might consider is do you actually need to go faster than 60fps? The game will not be any faster or smoother than it is now, and it might actually look worse because you'll see screen tearing when VSync is disabled.
If you insist on disabling VSync, you can do so through the NVidia control panel. Instead of explaining all the steps, here's a screenshot that hopefully makes it clear: disable_vsync_winxp_nvidia.png.
1.7 no longer lists the card name next to D3D in the prefs. That is normal.
The fact that you are getting a consistent 60fps when MaxFPS is not enabled does indicate that VSync is on, as you thought.
One question you might consider is do you actually need to go faster than 60fps? The game will not be any faster or smoother than it is now, and it might actually look worse because you'll see screen tearing when VSync is disabled.
If you insist on disabling VSync, you can do so through the NVidia control panel. Instead of explaining all the steps, here's a screenshot that hopefully makes it clear: disable_vsync_winxp_nvidia.png.
Last edited by Melekor on Sun May 03, 2009 5:21 pm, edited 1 time in total.
-
Giant Killer General
- Posts: 32
- Joined: Sun May 03, 2009 12:38 pm
Okay, I just wanted to make sure. 60 FPS is plenty, however that is just when I was testing by myself with no real fighting, fire effects, rain effects, etc. As long as it is using my video card it won't bog down and lag me under any conditions. That was all I wanted to be sure of, I have had that problem in the past. Thanks though.
There is no installer. It's just an exe.Viktor wrote:I'm having trouble with the installer. Says some smack32.dll file is missing.
See this thread for more info:
http://tain.totalcodex.net/forum/viewtopic.php?t=4300
-
Baron LeDant
- Posts: 364
- Joined: Mon Mar 22, 2004 9:14 pm
Bug reporting in
1. When in the southwest region of the ww2 recon deluxe map, my sounds were weird. The ambient sounds might have been repeating constantly or something to that effect.
Also lagged but I don't think its a 1.7 issue
2. Just go SW on the map, if that doesn't reproduce it try it with another player in the game.
3. Vista
3gb RAM
9600T Geforce 512 mb
quad core processor
4. I have a film of it occurring, would you like me to send it and where?
1. When in the southwest region of the ww2 recon deluxe map, my sounds were weird. The ambient sounds might have been repeating constantly or something to that effect.
Also lagged but I don't think its a 1.7 issue
2. Just go SW on the map, if that doesn't reproduce it try it with another player in the game.
3. Vista
3gb RAM
9600T Geforce 512 mb
quad core processor
4. I have a film of it occurring, would you like me to send it and where?
I wear a plastic ass on my bag ~ Da Cheeze
Windows XP Pro SP3
2.5 GHz Pentium 4
2 GB of DDR SDRAM
ATI Radeon X1650 Pro 512 MB DDR2 (AGP)
Benchmarks in Willow Creek without moving camera. MaxFPS is off. Vsync is off. Tex Cache left as 20 which is the default. Resolution set to 1024x768. Detail Textures on.
Windows Modern 317:
OpenGL -
Dtex on: Started with 10 fps but normalized at 19-20.
Dtex on: While paused it went down to 16-17. (23-24 away from Mill)
Dtex on: When not looking at the Mill it went to 24-40.
Dtex off: Used F11 to turn dtex off and it went to 32-34.
Dtex off: While paused it went down to 22-23. (26-28 away from Mill)
Dtex off: When not looking at the Mill it went to 41-44 up to 50 at times.
Direct3D -
Started with 60 fps but normalized to 90 after being 70-90.
While paused it went down to 78-80. (166-168 away from Mill)
When not looking at the Mill it went to 110-280.
Windows Modern 1.6 (290):
OpenGL -
Hi Res on: Started with 7 fps but normalized at 26-27.
Hi Res on: While paused it went down to 20. (27-28 away from Mill)
Hi Res on: When not looking at the Mill it went to 35-41.
Hi Res off: Started with 7 fps but normalized at 32-33.
Hi Res off: While paused it went down to 23-24. (27-28 away from Mill)
Hi Res off: When not looking at the Mill it went to 35-44.
Direct3D -
Started with 60 fps but normalized to 70 sometimes going up to 108.
While paused it went down to 60-67. (160-180 away from Mill)
When not looking at the Mill it went to 160-256.
2.5 GHz Pentium 4
2 GB of DDR SDRAM
ATI Radeon X1650 Pro 512 MB DDR2 (AGP)
Benchmarks in Willow Creek without moving camera. MaxFPS is off. Vsync is off. Tex Cache left as 20 which is the default. Resolution set to 1024x768. Detail Textures on.
Windows Modern 317:
OpenGL -
Dtex on: Started with 10 fps but normalized at 19-20.
Dtex on: While paused it went down to 16-17. (23-24 away from Mill)
Dtex on: When not looking at the Mill it went to 24-40.
Dtex off: Used F11 to turn dtex off and it went to 32-34.
Dtex off: While paused it went down to 22-23. (26-28 away from Mill)
Dtex off: When not looking at the Mill it went to 41-44 up to 50 at times.
Direct3D -
Started with 60 fps but normalized to 90 after being 70-90.
While paused it went down to 78-80. (166-168 away from Mill)
When not looking at the Mill it went to 110-280.
Windows Modern 1.6 (290):
OpenGL -
Hi Res on: Started with 7 fps but normalized at 26-27.
Hi Res on: While paused it went down to 20. (27-28 away from Mill)
Hi Res on: When not looking at the Mill it went to 35-41.
Hi Res off: Started with 7 fps but normalized at 32-33.
Hi Res off: While paused it went down to 23-24. (27-28 away from Mill)
Hi Res off: When not looking at the Mill it went to 35-44.
Direct3D -
Started with 60 fps but normalized to 70 sometimes going up to 108.
While paused it went down to 60-67. (160-180 away from Mill)
When not looking at the Mill it went to 160-256.
-
Propagandhi
- Posts: 33
- Joined: Sat Oct 14, 2006 11:11 pm
Great patch and stuff
This isn't so much a bug, just a feature you may want to rethink:
"[in capslock mode]...selection boxes are no longer shown - only unit health and mana."
This is not optimal, the faint blue outline of teamate units is not sufficient to determine whether the units belong to you or them without close-ish inspection. Can we have a preference setting for this? Or turn the yellow outlines on when you have teamates (that's maybe more pain than its worth)
Myrk also mentioned it, so I thought I'd post.
Great patch, guys. The smoother camera movement is a big "WOW" for me.
Edit: heh, my quote snippet was pretty confusing... hopefully better now.
"[in capslock mode]...selection boxes are no longer shown - only unit health and mana."
This is not optimal, the faint blue outline of teamate units is not sufficient to determine whether the units belong to you or them without close-ish inspection. Can we have a preference setting for this? Or turn the yellow outlines on when you have teamates (that's maybe more pain than its worth)
Myrk also mentioned it, so I thought I'd post.
Great patch, guys. The smoother camera movement is a big "WOW" for me.
Edit: heh, my quote snippet was pretty confusing... hopefully better now.
-
adrenaline
- Posts: 100
- Joined: Tue Feb 13, 2007 6:46 pm
I've noticed the caps lock feature got changed. Before, my units were highlighted in yellow and allied units were in blue. Now, my units aren't highlighted, they just have a health bar. I find this makes it very hard to distinguish my units from teammates' units using this feature and it should be changed back to how it was.
-
phordicus2
- Posts: 13
- Joined: Mon May 04, 2009 12:01 am