Screenshot Issue & CO2 Issues

Gryffon300 · 07-04-13, 04:23 AM

This may or not be a mod issue per se, but may require an adjustment in a config file, so I hope I'm in the right place.

This is a reprint of a comment in the 'Stories' thread, but it probably needs some high-tech input. I'm using Windows 7.

Quote:

I've been revisiting the screen-shot issue. Its going to take me a little longer as, although Ctrl+F11 seems to do something, the .bmp file it creates is dumped into the SH4 folder, which is not good, as it means mucking around in that folder. Cutting and pasting in that folder is not great process - so I'll have to explore a way to control the destination folder, if possible.

Of more concern, however, is that the file (that is named like this - SH4Img@2013-07-03_16.16.14_529.bmp) is not openable, with an error message that comes up reading, "Windows Photo Viewer can't open this picture because the file appears to be damaged, corrupted, or is too large." (All the files are 3 MB).

More homework. (Sigh.) Can anyone point me to fix-up instructions?

In addition, the game just 'killed' me after successfully sinking on over 60,000 of merchants in Truck Lagoon on 17th August '42, evading and escaping on the surface at night, only being unable to clear the 'CO2' warning. The game terminated my sub, declaring we had run out of Oxygen. I had run serveral dive cycles, trying to clear the fault, to no avail. Any thoughts?

Thanks

Gryff

CapnScurvy · 07-04-13, 08:12 AM

Taking an in-game image with the Ctl+F11 key combo is normal, so is the name the game gives the .bmp image, and the placement in the game's "main" Silent Hunter Wolves of the Pacific folder. All stock game functions. The 3Mb size is about right too. Don't worry about cut/paste in the folder, if you use the JSGME "Compare Snapshot" you'll have those image files as "New" found files if you don't remove them.

Why the image isn't openable is an issue more likely due to your computer. When you right click the .bmp, do you have a choice of "Preview, Edit, Print" at the top of the menu popup? Can you take the image to any of these functions? I don't have Windows 7, but I'm suspecting there's something fishy about your "Windows Picture & Fax Viewer" (least that's what its called on older OS systems).

As far as the "Co2 bug" (yep, we have a name for it).....
its a stock game problem many of us have encountered. Here's a recent thread...."Co2 Bug"....that has a lot of opinions on the subject. Nothing we can really do about it, just have to work around it.

Gryffon300 · 07-04-13, 09:48 PM

Quote:

Originally Posted by CapnScurvy

Taking an in-game image with the Ctl+F11 key combo is normal, so is the name the game gives the .bmp image, and the placement in the game's "main" Silent Hunter Wolves of the Pacific folder. All stock game functions. The 3Mb size is about right too.

Why the image isn't openable is an issue more likely due to your computer. When you right click the .bmp, do you have a choice of "Preview, Edit, Print" at the top of the menu popup? Can you take the image to any of these functions? I don't have Windows 7, but I'm suspecting there's something fishy about your "Windows Picture & Fax Viewer" (least that's what its called on older OS systems).

Thanks, CS - it's good to know the game program is functioning as designed - it looks like all this is a Windows system issue. I can go to Preview etc, but I get that same error message. I'll try opening the bmp with some other photo processing program etc.

Quote:

As far as the "Co2 bug" (yep, we have a name for it).....
its a stock game problem many of us have encountered. Here's a recent thread...."Co2 Bug"....that has a lot of opinions on the subject. Nothing we can really do about it, just have to work around it.

OK. I can live with that. (I put a reply in the CO2 Bug thread that you let me know about - that was useful. Cheers.

) My problem was in not knowing that the consequence would be the game 'screen-of-death', and being in high-compression mode to get on my way, I was about ready to save, in case I got sunk or something after all my good work, but it all happened too fast and regrets were being expressed. Live and learn.

Thanks

Gryff

CapnScurvy · 07-05-13, 06:49 AM

That Co2 bug is a stinker!

I mentioned I had it once, and like you, I couldn't/didn't do anything about it. The game ended with the death screen and I was helpless to do anything else. Seems if it happens again, the correct response is to "Save" your game, exit, restart, then reload the save game point. Gamer's say that will correct the bug. I don't know, its not happened to me since the last time.

Why it happens.....what triggers it? Is still unclear.

Gryffon300 · 07-05-13, 07:37 PM

Quote:

Originally Posted by CapnScurvy

That Co2 bug is a stinker!

I mentioned I had it once, and like you, I couldn't/didn't do anything about it. The game ended with the death screen and I was helpless to do anything else. Seems if it happens again, the correct response is to "Save" your game, exit, restart, then reload the save game point. Gamer's say that will correct the bug. I don't know, its not happened to me since the last time.

Why it happens.....what triggers it? Is still unclear.

Thanks, CS. Yep, I'm relaxed about it now that I know that there is an on-the-fly work-around that can be used if it ever pops up again. I would be fairly confident that there is a game bug that doesn't 'accept' the 'switch' to being surfaced, so it fails to switch off the CO2 clock of death.

Any vehicle worth it's salt has it's endearing idiosyncrasies.

Cheers

Gryff

TheDarkWraith · 07-07-13, 08:48 PM

Quote:

Originally Posted by Gryffon300

Thanks, CS. Yep, I'm relaxed about it now that I know that there is an on-the-fly work-around that can be used if it ever pops up again. I would be fairly confident that there is a game bug that doesn't 'accept' the 'switch' to being surfaced, so it fails to switch off the CO2 clock of death.

SH5 code was built on top of SH4 code and this bug was present in SH5. The problem is a bit is not being reset. I patched it out in SH5. So yes, your assumption is correct

Gryffon300 · 07-12-13, 01:43 AM

Quote:

Originally Posted by Gryffon300

Thanks, CS - it's good to know the game program is functioning as designed - it looks like all this is a Windows system issue. I can go to Preview etc, but I get that same error message. I'll try opening the bmp with some other photo processing program etc.

Very weird stuff. As both myself and Vomitus developed an inability to open bmp files simultaneously, it was mooted that there may have been a Microsoft upgrade that had 'killed the function. I have tried multiple solutions, but to no avail. However, last night, after yet another series of standard Windows auto upgrades (131 MB's worth!), I took a bunch of screen shots on the off chance I could do something with them (I wanted proof that the game was not giving me credit for 3 out of the 6 Capitals (2 x Heavy and 1 x Light Cruisers).

I did not have much hope, but after the mission, I went to the saved files, and immediately noticed a significant difference. As previously noted, the un-openable files are 3MB files, whereas all of last night's shots were 5MB. Ah,ha! Something is going on. Sure enough, I can open and view them all.

Don't ask me what happened, I'm just glad something, somewhere was changed (but not by me).

Gryff

CapnScurvy · 07-12-13, 05:52 PM

As I mentioned, I don't have Windows7 (or 8 for that matter) so I'm not one to know for sure what's up with an "update" for these newer OS's. I do know that there have been times when a Windows update has caused problems with other programs that I've got running in the background of my XP or Vista OS. One such program has been my Google Spell Check program attached to the Google TaskBar.....It has recently stopped functioning, after one of the latest Windows updates......on both of my Operating Systems?!

Why, I don't know? But, I can't spell kat without it!

Gryffon300 · 07-12-13, 09:08 PM

Quote:

Originally Posted by CapnScurvy

As I mentioned, I don't have Windows7 (or 8 for that matter) so I'm not one to know for sure what's up with an "update" for these newer OS's. I do know that there have been times when a Windows update has caused problems with other programs that I've got running in the background of my XP or Vista OS. One such program has been my Google Spell Check program attached to the Google TaskBar.....It has recently stopped functioning, after one of the latest Windows updates......on both of my Operating Systems?!

Why, I don't know? But, I can't spell kat without it!

Well, Fearless Leader, I have concluded that the dreaded Microsoft are a perfidious and nefarious multi-tentacled critter, so our mutual annoyances can well be imagined to be their doing. Sometimes Moriarty has nothing on these dudes.

I have only recently acquired this new notebook, but I had a bit of a struggle finding it, as I did NOT want to be a guinea-pig and be lumbered with that new touchy-feely W8. Finding one loaded with W7 was not easy. Unless you have a computer built, it seems no longer possible to get the excellent, stable and reliable XP. ave atque vale.

Anyway, Cap'n. I been meanin' ta ask ye, with all that spinach you consume, how is it you got knighted as 'Scurvy'. Now, it was only 2 years ago in Sydney, while I was lodging in a nice sea-side hostel for a spell, that I came across two very sick and sorry young American lads in their early twenties. They had been touring around Aus for about 9 months and were getting progressively worse. We finally persuaded them to see a doc (yes, we actually have such things!). They were pretty bloody sheepish when they came back, I can tell you! Yep, you guessed it, scurvy! from a steady, almost exclusive diet of 2-minute Noodles. First and only time I'd ever heard of anyone actually having it. So. What's your story?

Gryff

PS don't feel too bad about not being able to spell without your checker. When typing fast, I too may misspell 'kak' - I thought your use of the term for parrot-droppings as a description was quite apt, though unusual and not employed nearly frequently enough. (That IS what you were trying to type, wasn't it?)