Shadrach
-
Posts
43 -
Joined
-
Last visited
Posts posted by Shadrach
-
-
For anyone encountering this, the solution (at least on Win10+11) is to override DPI scaling in the executable properties, setting it to "Application". I need to do this for all CM games. There is no need to turn off DPI scaling to run the game. See attached screenshot.
For instance, running CM on a 2560x1440 display, the UI is too small for my eyes, so I want to run it at 1920x1080, so I set this in "display size.txt":
1920 1080 60But with 150% DPI scaling set in Windows, the game does not handle this at all, thinking I'm running at 1080/1.5 = 720.
If the game engine had supported DPI scaling this would of course not be necessary, as any program that support it will automatically scale accordingly. But for games it's often necessary to override scaling.
It might be possible for Battlefront to fix this by compiling the executable with a manifest telling the OS the application does not support scaling, it will then fall back to using Application scaling:
https://docs.microsoft.com/en-us/windows/win32/hidpi/setting-the-default-dpi-awareness-for-a-process
-
2 hours ago, Taranis said:
I like the guy at the end there
-
8 minutes ago, Ultradave said:
I opened a new ticket with this detailed info and referred back to the previous one. Looks like the full path to the save game is being appended rather than the relative path from the user's game directory in Documents.
Dave
Thanks a lot Dave. If they want a full capture from Process Monitor, I'd be happy to create one. However I'd have to share it somewhere private or through PM, since I don't want to share full ProcMon logs in public.
-
Just to make sure, I made a log using Process Monitor when saving a game in Black Sea 2.16 - same thing, it tries a CreateFile to a duplicated path:
20:39:41,4484432 CM Black Sea.exe 9132 3060 CreateFile C:\Users\Stian\Documents\Battlefront\Combat Mission\Black Sea\C:\Users\Stian\Documents\Battlefront\Combat Mission\Black Sea\Game Files\Saved Games\Quick Battle 002.bts 0.0000165 NAME INVALID File System Desired Access: Write Attributes, Synchronize, Disposition: Open, Options: Synchronous IO Non-Alert, Open Reparse Point, Attributes: n/a, ShareMode: Read, Write, Delete, AllocationSize: n/a F:\Games\Battlefront\Combat Mission Black Sea\CM Black Sea.exe CRAPSTATION\stian
20:39:41,4485218 CM Black Sea.exe 9132 3060 CreateFile C:\Users\Stian\Documents\Battlefront\Combat Mission\Black Sea\C:\Users\Stian\Documents\Battlefront\Combat Mission\Black Sea\Game Files\Saved Games\Quick Battle 002.bts 0.0000132 NAME INVALID File System Desired Access: Read Attributes, Delete, Disposition: Open, Options: Non-Directory File, Open Reparse Point, Attributes: n/a, ShareMode: Read, Write, Delete, AllocationSize: n/a F:\Games\Battlefront\Combat Mission Black Sea\CM Black Sea.exe CRAPSTATION\stian
I've also removed any mods as well as the Reshade I use, and same thing.
-
6 hours ago, Ultradave said:
I know it's annoying but I'm not seeing how it makes the game unplayable or game-breaking.
Hi Dave, thanks for the reply. Yeah it's not making the game "unplayable" but when playing a turn I tend to save a *lot*, and this is really ingrained to how I play the game. So yeah, not game-breaking, just very annoying.
What annoys me the most is the complete lack of feedback from BF on this pretty obvious and serious bug, and any information on whether they're aware of it and when it will be fixed. I am of course expecting a fix in the "next patch" but no-one knows if that's weeks or months away, or even if it will actually contain a fix for this issue. We don't even know if they're working on a new fix for CMBS and CMCW.QuoteAnother question. I see in the pic of the OP that the Game Files folder is inside the installation. On a PC isn't that normally in your User directory? I understand I'm seeing the Steam installation there. Those of you with Matrix or BF installations - is your Game Files folder inside the application folder or in your User directory (somewhere like C:/Users/<username>/Battlefront/CM Black Sea/Game Files/ ) ?
It's a good point. I have the Matrix version of Cold War, and for some reason they've changed the save game location to the game directory, under "\Game Files\Saved Games". Which obviously is a *really stupid* place to save stuff, as there's no guarantee the user has write permissions there unless the game is run as Admin.
But like I said after patching Black Sea to 2.16 the same is happening there, and that game saves to the My Games directory like all other CM games (Documents\My Games\Battlefront\Combat Mission\Black Sea\Game Files\Saved Games).
So I don't think it's a permissions issue. Like I said in the Matrix forum post, it looks like the game messes up the save game path:
F:\Games\Battlefront\Combat Mission Cold War\F:\Games\Battlefront\Combat Mission Cold War\Game Files\Saved Games\Direction Found 003.bts
This above is from the Matrix build of Cold War. I've not done the same logging for Black Sea, but should be an easy task.
-
I posted about this bug back in November:
https://community.battlefront.com/topic/140450-the-combat-mission-cold-war-v103-patch-has-been-released/page/2/#comment-1892857Also on the Matrix CMCW forum since I bought it there:
https://www.matrixgames.com/forums/viewtopic.php?t=375985No official response from Matrix or BF on this... Matrix Games support sucks but I was expecting more from Battlefront. At least an official "yes we know about it and is working on it".
In fact, I thought I would get back into CMBS - played it a bit and saving worked fine. Then I saw, that "oh there's a new patch 2.16, better install that". After patching, the *same* bloody thing is happening in CMBS...
-
Does anyone know if a 1.04 patch is upcoming and if it will fix the overwriting save games issue?
-
I bought the version off Matrix, it's still on 1.02 and no patch on My Page on Matrix.
I encountered a nasty critical bug with the game failing to overwrite save games, instead creating TMP files in the install folder. Just wondering if this issue is limited to the Matrix version and/or maybe related to the new PBEM++ system (assuming it required a rewrite of save system)?
https://www.matrixgames.com/forums/tm.asp?m=5107582
Matrix support being notoriously slow and incompetent, I'm already starting to regret my decision. Just wanted to use my discount voucher...
-
One thing I don't understand is why you keep releasing patches in RAR format. Does it really compress better than the much more universally supported ZIP format, which is built-in to Windows these days? I mean, I have the tools to unpack them but not necessarily every does.
-
On 7/16/2020 at 7:06 PM, BFCElvis said:
FIXED: T32 infantry gun's projectile and tracer appearing from wrong location (not the barrel)
Thanks for that! Took a while, but hopefully it fixes this issue:
I wonder if the blinking contact icons will be fixed, just have to check and see I guess...
-
On 6/24/2020 at 12:27 AM, AtheistDane said:
Which mod is those explosions from?
It's Aris CMFI HD Explosion Mod:
https://cmmodsiii.greenasjade.net/?p=1458 -
16 hours ago, Field Oggy said:
Could the pack up time be refering to the gun being tied onto the back of a mule?
Yeah, I was actually thinking the same - the time is to "emulate" packing the gun onto a donkey back
Might as well be, makes as much sense as anything else!
11 hours ago, DougPhresh said:once the tube is hot and the baseplate is firmly in the ground
Yeah, that might be it as well. No idea unless we can get the information from the "donkey's mouth" i.e. Battlefront, on why they decided on this long pack-up time...
Thanks!
-
On 1/22/2020 at 1:37 AM, DougPhresh said:
Limbering a gun can take a while depending on how dug in the spades are. Usually we fire one round at full charge to get the spades dug in deep when setting up the gun but it can take a lot of shovel-work and manpower to roll the gun out of that hole. Also a pack gun probably takes a while to break down into loads.
Thanks for the information! But surely it would not apply to this thing? I mean if it takes 20 secs to assemble the loads then why would it take five minutes to pack it up again?
Then again, the main issue is not the packup time, but the gun's inability to fire at things it has LOS to. I suspect the terrain slope where the gun is deployed plays a role in this? The packup time is just a huge nuisance when it's unclear where the gun is able to fire from.
-
Brummbär explodes.
Really hope no civvies were still in that ville...
-
Good tip!
The default post-processing in the game is way too blurry. I use Reshade with the LumaSharpen filter to achieve a similar effect.
-
Yeah, might be something like that - I was thinking maybe the gun is on a slope, so it's unable to elevate the barrel to the target. I've seen that before for other weapons but then it says "elevating" not "turning". Also kind of pointless for a *Mountain Gun* if you ask me...
I'll try things I guess - problem is, with a 5 min pack up time... sheesh. No way do I believe something that takes 20 secs to deploy would take 5 minutes to pack...
-
On 12/3/2019 at 10:34 PM, CHEqTRO said:
While playing the Two Crowns scenario, my T32 Mountain gun refused to fire for some reason.
The gunner kept in a permanent state of "turning" the weapon, but never fired, despite having perfect line of vision/fire and being commanded to fire via the target command. It is true that one of the 4 soldiers that usually handle the weapon was killed before this, and maybe that was the reason it refuse to turn the weapon, as it needed the full crew to work, so maybe is working as intended?
Yeah, I'm having the same issue here with the T32 on the Two Crowns scenario. It can target, but is in a constant state of "turning". Makes the scenario even harder than it needs be...
-
On 12/3/2019 at 10:34 PM, CHEqTRO said:
While playing the Two Crowns scenario, my T32 Mountain gun refused to fire for some reason.
The gunner kept in a permanent state of "turning" the weapon, but never fired, despite having perfect line of vision/fire and being commanded to fire via the target command. It is true that one of the 4 soldiers that usually handle the weapon was killed before this, and maybe that was the reason it refuse to turn the weapon, as it needed the full crew to work, so maybe is working as intended?
Yeah, I'm having the same issue here with the T32 on the Two Crowns scenario. It can target, but is in a constant state of "turning". Makes the scenario even harder than it needs be...
-
Thanks for the confirmation, and that it's not mods at least. Maybe an issue with that specific range of gfx cards.
-
With this release I'm getting back into CMFI after a long absence. Seeing blinking icons for non-spotted contacts, not sure if this is something new or a bug.
I've tried disabling Reshade and mods but still it occurs.
Windows 10 Pro x64
NVidia GTX970, latest driversMods:
Aris Flames Mod SlowMo\
Aris HD Explosion Mod\
Aris Muzzle Fire\
Aris Smoke\
Aris Tracers\
Juju's TweakedUI for CMBN v5\
Juju's TweakedUI for CMFI v5\
Bils CMFB Gridded Ground.brzReshade 4.3.0 with only Vibrance and LumaSharpen enabled.
Anyone else seeing the same?
-
There are certain small things that bother me about the game in its current state, and all CM titles, and I'm not talking about if the German infantry have the right number of attachments on their belts or the M1 Abrams has the correct number of sprockets.
Stuff like minor UI improvements that could make a big difference for usability and "quality of life" for players.
- Having a modifier for plotting routes, for instance holding down Shift, to make several selected units follow the same waypoints (NOT follow formation). Would be a massive time-saver for plotting road routes for vehicles.
- More mouseover tooltips on UI elements, especially stuff that's important, like rank, comms status. Ideally tooltips should be on all elements related to gameplay.
Certainly there other more important things the devs should prioritize, like performance and graphics improvements, unit balance and so on, but I think small things matter just as much on how the game is received, especially for new players.
Feel free to add your own, but we're talking about UI and usability here.
-
@HerrTom I just use stock Vibrance to add a dash of color, and LumaSharpen to make textures a bit sharper. Never liked oversaturated and too high contrast, like the movie effects. But I guess a lot of people like it...
Only problem I have with CM + Reshade is the game keeps spinning when I am inside the Reshade config overlay. Anyone else seeing that? Tried changing the input settings with not really an improvement. I guess I'm not the only one either:
That last post might have given a solution though, will check...
-
According to the README, the demo is supposed to launch in desktop resolution, which for me is 2560*1440.
However it is clear it is not, as everything is very blocky, looks more like the ancient 1024x768.
So when changing to 1280x720 which is the highest from the menus, I get the following crash:
Also after editing display size.txt to read:
2560 1440 60
I get the same blocky graphics.After changing it to:
1920 1080 60
Which is what I run the other games at (since 1440 makes the UI too small), I get the crash again.Am I forced to play the demo in the ultra-blocky resolution?
-
To avoid this error, set DPI settings to Override + performed by Application.
Just another indication of the age of this engine, when it crashes using simple DPI scaling.
Combat Mission Cold War v1.06 is now available
in Combat Mission Cold War
Posted · Edited by Shadrach
Well, looks like you fixed the bug with overwriting save games, as reported here:
At least looks like it from a quick test
It is possible this bug was only present for the Matrix/Slitherine release, as they for some reason chose to save games in the game install folder not Documents like the Battlefront releases.