Taking High res screenies via Alt-F10 doesn't work for me anymore
- Thread starter Iskariot
- Start date
Really?
I did not know that at all.
I have been playing open again lately.
So that is it then.
Is there some technical reason why hires screenies don't work in Open?
This will likely force me back into solo again eventually.
Something to do with a possible exploit, I believe.
I'm not sure about Group, might be wrong there, sorry.
The reason they're blocked in Open is due an exploit. Someone set the save location for the screenshots to be a slow USB stick or something like that, and then taking a high resolution screenshot to this slow location effectively froze the game for a few seconds. I'm not sure what exactly the benefit was - probably combat logging.
The reason they're blocked in Open is due an exploit. Someone set the save location for the screenshots to be a slow USB stick or something like that, and then taking a high resolution screenshot to this slow location effectively froze the game for a few seconds. I'm not sure what exactly the benefit was - probably combat logging.
Somebody came up with a theory that you could macro-spam it to clip around in multiplayer. Frontier bought it without any actual testing and disregarding the obvious fact that you'd need to devote terabytes of your hard drive to the task. Now we have to log out and log back in to solo to take hi-res screenshots.
Frontier's superb knowledge of multiplayer games shines through once again.
It would take ten minutes to write a script to monitor the screenshot folder and delete the files as they're created.
Simple. Squeeze trigger on an alpha strike, take screenie, hold trigger. All the damage stacks at once. Another game I used to play had a similar issue. They eventually disabled screenshots entirely on that one, both to stop that and because Steam has its own screenie tool.
It's not a theory, and it doesn't take a lot of storage to do it, as the poster below you said, a script to clear the images is rather easy to create, allowing this exploit to be rather real, hence the reason FD did what they did.
You ARE correct on one fact, FD's lack of multiplayer experience, but they did take the exploit seriously because it's extremely easy to actually do, so they are obviously learning on the multiplayer aspect, will you do the same?
Less time. The issue is how big of a screenshot does it take to actually accomplish anything?
My PC at the time had 32gb of fast DDR3, I couldn't take a screenshot big enough to cause anything weird to happen without hard crashing, which just caused me to freeze in one spot for a few seconds before flying straight for a while and disconnecting. As far as I could tell the only way to do anything with it was to spam them to an SSD, and even then it wasn't as bad as the P2P servers are any given day.
It wasn't a real exploit though, most of the time it just made you an easy target while you had no idea what was happening to your ship. So yeah, I guess if having your ship fly in it's current trajectory for X seconds while your screen is frozen is an exploit it did it pretty well.
Writing to a USB was the most useless iteration of this "exploit". For it to be anything approaching an exploit the best you could do is force stutter while having high latency to the server, which would pop you around all over the place. I almost cooked an SSD finding out if this was possible because 500mb/s read/write wasn't fast enough to write and clear the screenshots off of a 512gb SSD. Since you were completely out of control of your ship you either needed an aimbot or you hoped that the turrets worked at least half the time, and you didn't have a chance in hell of chasing anyone down if they started to run.
So yeah, it was a great test to find out if you had epilepsy. Not much else.