Add me to the list of users where CMANO fails to start. Same problems as reported above.
Got the game from my wife for Christmas. Loaded game, upgraded to 1.02, and started playing
first tutorial. It hung (not responding), so I killed game. Unable to start again.
So, re-installed & upgraded again. Started ok, but hung again when the missiles started flying.
Killed it again and now unable to start again.
Toshiba Satellite
Windows 7 Home Premium 64-bit
Intel Core 2 Duo T6600
4GB DDR2 RAM, 500GB HDD
ORIGINAL: Baloogan
One thing I'd recommend is setting the quality settings to "Let the 3D application decide" in the NVIDIA control panel. This seems to work for me.
I've reinstalled my drivers and did the above in the NVIDIA control panel. If this helps anyone please post about it; I'm going to run some more tests to determine if this is a fix.
I'd like your attention for a moment if you are afflicted by this bug. [:)]
I have determined 2 ways to solve the bug for myself. First I would run War Thunder and then run Command while War Thunder was running.
Yesterday I reinstalled my nvidia drivers, and set the NVIDIA control panel to "Let the 3D application decide". Now the problem doesn't occur for me; at least so far.
Please try to reinstall your drivers, and (the most important step) set your NVIDIA control panel to "Let the 3D application decide".
I think the reason why the War Thunder fix was working for me was that War Thunder didn't care what the setting in the NVIDIA control panel were; and configured the video card via low level instructions. Thus War Thunder would configure my video card, and then I'd exploit how War Thunder set up my video card and use those settings for Command.
Please take a look at your NVIDIA control panel; and see if this fix fixxes it for you, please post your findings in this thread. I'll continue to monitor and update the thread as time goes on; and notify you guys if this issue reappears for me.
The problem would usually appear for me after a Reboot.
Make sure to check your process listing (Ctrl-Shift-Esc) and get rid of all running Command.exes before trying this out.
Is this something related to new purchasers? I'm convinced something isn't right with the base "1.01" full installer now provided as it reports 1.00 when I install it...maybe us new buyers are having issues due to some issue related to this?
Is this something related to new purchasers? I'm convinced something isn't right with the base "1.01" full installer now provided as it reports 1.00 when I install it...maybe us new buyers are having issues due to some issue related to this?
Hello,
The first issue is the one under investigation on this thread here.
On the latter, if anyone can produce a pre-crash autosave and post it on a new thread or mail it directly to me/us, it would be much appreciated.
I'm not a new user. I bought this first day it was for sale. I stopped using it because of this bug, in fact, and had hoped - when I came back to try again - that the patches had fixed it.
I'll try that fix, Baloogan, and let you know.
I can imagine how exhausted you all are, Sunburn. No hurry at all for me.
Ok. No difference for me, Baloogan, if I tick 'let the game decide'. By the way, I've already been through all the manually adjustable settings on the NVidia card, to no effect.
I'm sure it will get worked out in the end. Your efforts much appreciated, Baloogan.
Thanks for the info Phoenix. I was just wondering as I'm experiencing this issue and another issue on three different physical machines (from high to low spec), (and also in a VM, which ironically seems to run 1.01 okay but not 1.02).
I have the same issue trying to run it on my windows 8 laptop, kneecaps - so you're not alone there.
What would be common to them, I wonder? Not the graphics. The laptop only has crappy intel graphics. Not the same virus checkers even. The router. That's about the only thing they have in common. But does CMANO doing anything using the router when it starts? I don't think so.
But there must be something else in common, as otherwise why would some people not have this issue at all?
This may be a long shot, but could sound be a factor?
I have no problems starting CMANO, but occasionally get freezes. More than once I noticed the freeze happens when the game makes a sound, and I have also some other program making sound (e.g. music). It could be that certain hardware/driver combos are unfriendly to the game.
You could try setting the .ini to have no sound or music, to see if that makes any difference to startup.
Just thinking about if it is a graphics issue I thought I would just ask again - does everyone's image of land (in the photo below it's the Falklands) look like this? I mean is it meant to look like this - you can see the yellow land lines, the ordinary map, and the relief layer as three distinct layers, whose borders do not match at all. The camera alt is at the top of the screen. If others with this fail to start issue zoom in to, say, the Falklands, to roughly that alt, does your image look like this - ie messy?
Yes, it looks like that on mine, and I have no graphics issues.
I reckon it's just the vector data being a little out of synch with the map images. Also, check out the strange north-south line in the islands of SW Chile.
Good news guys. I am working with Sunburn to troubleshoot this issue. We have spent quite a bit of time today testing scripts and we are making progress. Stay tune. It's great to have a tech support team that teams up with players to solve the issue. They write the script and I test it on my computer. Awesome support!