Vanir Ausf B Posted February 15, 2015 Share Posted February 15, 2015 (edited) Several people have reported a problem with a couple of QB maps. Some of us beta testers have the same issue, but a few others don't. We are not sure why, but what we need to know is if everyone with the public version of the game has it or if only some have it. In other words this is a survey. Should you choose to participate this is what you need to do.1) Load CMBS and go into the Scenario Editor2) Load QB map "Open-Rough (1536x992) 061r" (click Load button, go to Quick Battle Maps folder, scroll down till you find it)3) Enter 3-D Preview mode (click on where it says Mission and select it from the pull down menu). Once the map loads look around for sharp, spikey-looking ridges that are clearly out of place. Reference the pic below. Then please post in this thread stating whether or not you see the problem terrain or if the map looks normal. Thanks! Edited February 15, 2015 by Vanir Ausf B 0 Quote Link to comment Share on other sites More sharing options...
AttorneyAtWar Posted February 15, 2015 Share Posted February 15, 2015 (edited) When I load that QB map in the editor it looks like the OP. Specs: Windows 7 64-bit Nvidia GTX 770 2GB 4GB RAM CMBS V1.01 Edited February 15, 2015 by Raptorx7 0 Quote Link to comment Share on other sites More sharing options...
Kieme(ITA) Posted February 15, 2015 Share Posted February 15, 2015 (edited) When I load that QB map it looks like the OP. Specs: Windows 7 64 bit Nvidia GTX 780 8GB RAM (CMBS patched) Edited February 15, 2015 by Kieme(ITA) 0 Quote Link to comment Share on other sites More sharing options...
Markus86 Posted February 15, 2015 Share Posted February 15, 2015 I can see the problem terrain, too. Specs: Windows 7 64-bit Nvidia GeForce GTX 770 16 GB RAM Intel i5-4670 CMBS V1.01 0 Quote Link to comment Share on other sites More sharing options...
Pete Wenman Posted February 15, 2015 Share Posted February 15, 2015 I see it too. Just to add although I'm sure you've already noticed it, but it looks like the terrain incline calculation is not working. So any tile that does not have a specific height allocated (black or blue) is defaulting to 22m for some reason whereas it should be adjusting to create slopes and inclines to match the surrounding locked in heights. P 1 Quote Link to comment Share on other sites More sharing options...
rocketman Posted February 15, 2015 Share Posted February 15, 2015 I get that too. Specs: Win 8.1 Intel Core i7-3630 QM nVidia GeForce GTX 670 MX CMBS 1.01 So far, all of us have nVidia. 0 Quote Link to comment Share on other sites More sharing options...
Vanir Ausf B Posted February 15, 2015 Author Share Posted February 15, 2015 I forget to mention that if for some reason you have not installed the 1.01 patch you shouldn't respond since the bug is not in 1.00, as far as we can tell. 0 Quote Link to comment Share on other sites More sharing options...
Wicky Posted February 15, 2015 Share Posted February 15, 2015 (edited) Mac CMBS 1.01 (OS X 10.10.2) Landscape not effected. ATI Radeon HD 5770 Edited February 15, 2015 by Wicky 0 Quote Link to comment Share on other sites More sharing options...
agusto Posted February 15, 2015 Share Posted February 15, 2015 (edited) Specs: Win 7 x64 CMBS 1.01 Intel CPU NVIDIA graphics card (dont ask which) I observed the bug OP described and i also took a look at the map editor. The transitions between action spots with fixed elevation and neighbouring action spots seem to be broken, they are non existant. If you give an action spot a fixed elevation of lets say 50, normally all adjunct action spots that dont have a fixed elevation themselves should automatically adjust so that elevation transitions are smooth (which means getting values like 49,48,47 and so on). That simply doesnt happen anymore. I think it has nothing to do with graphics cards or CPUs, it is the game that is somehow broken. Edited February 15, 2015 by agusto 0 Quote Link to comment Share on other sites More sharing options...
rocketman Posted February 15, 2015 Share Posted February 15, 2015 I think it has nothing to do with graphics cards or CPUs, it is the game that is somehow broken. In that case, wouldn't it affect all maps? 0 Quote Link to comment Share on other sites More sharing options...
agusto Posted February 15, 2015 Share Posted February 15, 2015 (edited) It doesnt seem to be graphical issue. The map files are broken. The engine just shows you the elevation levels that are specified in the map files, and they are broken. The way the elevation levels are rendered seems to be ok. Edited February 15, 2015 by agusto 0 Quote Link to comment Share on other sites More sharing options...
antaress73 Posted February 15, 2015 Share Posted February 15, 2015 I see them too... 0 Quote Link to comment Share on other sites More sharing options...
whitehot78 Posted February 15, 2015 Share Posted February 15, 2015 yup, it's messed up for me too windows 7 64, 12 gigs RAM 0 Quote Link to comment Share on other sites More sharing options...
DrDon Posted February 15, 2015 Share Posted February 15, 2015 Mac CMBS 1.01 (OS X 10.10.2) Landscape not effected. ATI Radeon HD 5770 Nearly the same specs as me: landscape is not affected. Mac CMBS 1.01 (OS X 10.10.2) ATI Radeon HD 5750 (instead of 5770). 0 Quote Link to comment Share on other sites More sharing options...
Lille Fiskerby Posted February 15, 2015 Share Posted February 15, 2015 When I load that QB map it looks like the OP. Specs : Win 7 (x64) Intel i7-2600-3.40 nVidia GTX 560 Ti CMBS 1.1 0 Quote Link to comment Share on other sites More sharing options...
RCE_Spr Posted February 15, 2015 Share Posted February 15, 2015 I see it as well 0 Quote Link to comment Share on other sites More sharing options...
Jim1954 Posted February 15, 2015 Share Posted February 15, 2015 Yes they are there. Win 7 (x 64) i7-3930 3.20 16 gb ram Nvidia GTX 690 CMBS 1.01 0 Quote Link to comment Share on other sites More sharing options...
Captain Mike Posted February 15, 2015 Share Posted February 15, 2015 Landscape not affected. Seems to be a windows only problem :-() MacOS 10.10.2, Radeon 6770M 0 Quote Link to comment Share on other sites More sharing options...
ridethe415 Posted February 16, 2015 Share Posted February 16, 2015 (edited) Um...I don't even see that map file in the menu. It is in my Quick Battle Maps folder, but I only have two open rough files listed? Mac based Edited February 16, 2015 by ridethe415 0 Quote Link to comment Share on other sites More sharing options...
bobo Posted February 16, 2015 Share Posted February 16, 2015 I have it too. Bob 0 Quote Link to comment Share on other sites More sharing options...
Rokossovski Posted February 16, 2015 Share Posted February 16, 2015 I have the problem as well. Not sure if it's related, but I've noticed the elevations are behaving oddly in the editor. Usually they key into the surrounding set elevations, but they now don't. My specs: Windows 7 Home Premium; Intel Core i7-4770 CPU @ 3.40 GHz; 16.0 GB RAM; 64-bit OS; GeForce GTX 760 video card. 0 Quote Link to comment Share on other sites More sharing options...
dan/california Posted February 16, 2015 Share Posted February 16, 2015 OSX 10.2, nvidia 750m. Do not have the problem. there seems to be a mac no/windows yes trend thus far. To state the bleeding obvious. 0 Quote Link to comment Share on other sites More sharing options...
Michael Emrys Posted February 16, 2015 Share Posted February 16, 2015 OSX 10.2... Is this what you meant to write? I'm finding it a bit incredible that you would be running CM on an OS nearly 15 years old! Michael 0 Quote Link to comment Share on other sites More sharing options...
Vanir Ausf B Posted February 16, 2015 Author Share Posted February 16, 2015 If you are starting a QB you will have to set the QB to Meeting Engagement for it to show in the map list.Um...I don't even see that map file in the menu. It is in my Quick Battle Maps folder, but I only have two open rough files listed? Mac based 0 Quote Link to comment Share on other sites More sharing options...
Vanir Ausf B Posted February 16, 2015 Author Share Posted February 16, 2015 OSX 10.2, nvidia 750m. Do not have the problem. there seems to be a mac no/windows yes trend thus far. To state the bleeding obvious. It looked like a good theory there for a while, but another beta tester who doesn't have this problem is on Windows. 0 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.