Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Discussions Rules and Guidelines
4 
Report this post
What does this function really do for you and TSFix?
W7 is only 7 years old. WXP is 15 years old, I could see not supporting that. Since it's more than twice as old.
At work we still use an emulated DOS like system for inventory under W7 VMs. Though that's in the process of being replaced, it's going to take several years. Rolling out W10 to all company computers? That'd probably take even longer lol. Heck, the POS systems still use WXP IIRC, now that's bad lol. For professional and work systems, where there is no hardware or software compatibility issues. I fully support using W10. Mainly from a security standpoint.
Plus, my personal hardware has no official support for W10 with no official drivers. (Not that it seems to have stopped some people in using X58 systems on W10)
As well, I REALLY don't feel like having to reinstall and re set up my entire DAW set up with tons of VST software that can be a pain to re activate.
I would never do an in place upgrade to W10. I would dual boot it perhaps. In my uses of working with an installing W10 on 2 other PCs, I find a lot of aspects of it very counterintuitive in terms of basic functions that didn't need to be changed from past Windows GUIs (Excluding W8)
I've experienced problems with W10 personally. The lack of being able to an upgrade install outside of inside the older OS environment is retarded. (I had a sibling whoms older OS install suddenly wouldn't boot no matter what kind of repair I did. The whole boot just became corrupt. Multiple checks of the drive for failure turned up nothing. And the drive is still functioning fine as a 2nd drive in that PC, aside from some long spin up times when coming out of sleep mode because it's a mediocre performing drive anyway. W10 has no way to do an upgrade install to preserve installed programs and data without launching the install from the old OS. You'd think they'd figure this ♥♥♥♥ out by now)
I've had Windows 10 just magically delete a ton of important personal data out of nowhere when trying to just delete a couple individual files. It didn't even go to the Recycle bin, it bypassed it completely and just blamo gone. (Even dug around using file recovery tools, zip zilch)Luckily a system restore somehow managed to save most of the most important stuff.
All I did was select like 5 files on the desktop because sibling ;instead of making shortcuts to some program files just copy pasted them on the desktop, so I was gonna make shortcuts; hit delete. And blamo, half the desktop disppeared. Gone.
https://linux.slashdot.org/story/16/08/03/1614223/windows-10-anniversary-update-borks-dual-boot-partitions?utm_source=rss1.0mainlinkanon&utm_medium=feed
http://betanews.com/2016/08/03/windows-10-anniversary-update-delete-linux-partition/
That's not to say i'm sour on W10, there are some parts of it that I like.
But really, functionality wise, aside from DX12.(And maybe the lack of crashing in DX10 Capcom games that comes with the kb2670838 update in W7) It offers me litterally nothing significantly useful considering i'm already slightly CPU bottlenecked with my aging 4Ghz 1st gen i7 with only PCI-E 2.0 and Sata II.
And DX12 has been very underwhelming, .No way to turn Vsync off in Windowed mode for any game, DX12 or otherwise. W8 did this too though. Aero in W7 is beyond terrible however, so at least there is that improvement.. (Say I want to play a game windowed at 180FPS on a 60hz display for decreased input latency. To my knowledge this isn't possible).
I'm rooting more for Vulkan, not just for W7/8. But also for Linux.
Then there is Microsoft's Malware centric approach to trying to force people to upgrade without their consent and removing more and more control over the process as it went on. Downloading large files without consent,which on metered connections and devices with small storage space, is even more irritating. The anniversary update requires 16GB of space , and on devices like Tabtops(Tablet/laptop combos), this space is a premium.
Again though, like I said I wouldn't mind dual booting W10 for certain uses. But W7 will be my main OS for the forseeable future, especially for games that might not work well on W10 and will never be updated or re-released.
When she's soulless, her CC is supposed to be Gray [with her eyes being red].
In those scenes, her CC is showing up red like it'd be if she was normal.
[Happened to notice AFTER putting in the 4K fix, so...]
Oh I see, I completely misunderstood that!
Heh, it's amazing I never asked about this in any of my graphics classes. I always assumed textures were pushed to VRAM as they were needed and well if you didn't have enough you needed to invest in a better graphics card. :)
I guess it makes sense that just like when you run out of physical RAM, your data is stored in pages, so the same would apply to VRAM. I just never thought about it. Of course that's slower but still a feasible option for users.
I'm using Win7 too but I'll probably upgrade to 10 by the time I play this game..hopefully.
Still, it's surprising they would add that feature in Win8. I've never been good at multi-threaded programming beyond some simple consumer/producer stuff. Is this doing anything more than just being a handy simple function that abstracts lower-level stuff? Couldn't you do something similar with WaitForAllObjects()?
I've heard a few stories about people losing some data, but it did seem to do a good job of getting things back to the way they were if you just restore the old OS. Just about every version of Windows that came out with significant changes caused miscellaneous odd problems for a while after release due to the wide variety of system and software configurations. The worst situations seem to be on machines that have drives that are already dying and a big OS upgrade like that shifting files around shakes up issues that were laying in wait. Not every end user is really qualified to assess those risks, so it was very ballsy for Microsoft to make Windows 10 a recommended update.
A big advantage of DX12 is actually to help reduce the CPU usage, but most engines which have DX12 (and Vulkan) support aren't actually designed from the ground up for it. Wait until we see real DX12 games that aren't just using it for marketing purposes. I also initially thought that PCI-E 2.0 was a bottleneck for me, but the reality is different. You've probably never maxed out that bus. I had a lower end processor along with only 4GB of RAM at the time and performance improved across the board when I upgraded from Windows 7 to Windows 10. Faster boot, more available RAM, freed up space rather than taking up more and framerates went up. It breathed similar life into other older machines more-so than a normal reinstall would have. So even excluding DX12, there are gains. Some of those performance improvements are things which came with Windows 8.1.
I believe they already fixed the vsync issue. Plus they're also making it so that if a surface fills the full display, the compositor will assume it has nothing to composite and step out of the way. That will reduce input latency a bit, since you would only be 1 frame behind instead of 2.
I think it's easy to hate on proprietary APIs and assume every company that does something proprietary is just evil, but there's also a chance that line of thinking is ignorant. Basically every meaningful platform today has their own graphics API. Let's just go ahead and give countless veteran engineers the benefit of the doubt that they've thought it through and decided having their own API would be beneficial. Sony, Nintendo, Apple, Microsoft, you name it. What could their reasoning be?
Does having their own API allow them to integrate more with the rest of the system, reserving room for them to innovate in the future even if it doesn't manifest in the short-term? Does it allow them to make optimizations and other improvements without worrying about breaking some cross-platform standard? Can they make their own API designed in such a way that it's easier to tool against? Does it make it easier for them to fix emergency issues should they come up, whether it's a software or hardware partner that introduced them?
Of course companies that have lots of cross-platform investment would love to have some unified API. Neither side is really wrong. Web standards have a similar issue. There's already some level of agreement over the basic functionality that should be provided, but it's open to interpretation and everyone wants their own interpretation so you still have to test in other browsers and make changes as needed. Plus, people love to add their own experiments which in the end have resulted in contributions to the standard.
I haven't run into a single game or app that doesn't work on Windows 10 in quite some time and that includes both ancient legacy crap, modern things and brand new things. I know stuff exists that doesn't work on Windows 10 yet due to integrating more at the system level or had custom drivers, but I'm not aware of anything super popular worth ignoring the upgrade for. I've seen a number of cases where people said a game didn't work for them on Windows 10, but others on Windows 10 had no problems running it and that may point more to a configuration or driver issue rather than Windows 10 itself at times. Perhaps someone has compiled a list?
It synchronizes multiple threads and allows you to efficiently wait until all of them reach a certain point. It's very commonly used in compute shaders because they're ridiculously multi-threaded, it's not so commonly used for CPU stuff but it does have a legitimate use here and the fact that the Windows 7 kernel doesn't support it but I'm forced to support Windows 7 is annoying.
I think a lot of the room for performance improvement in D3D12 games will actually come from developers not having to cripple their software with slow stuff that works in Windows 7 :) The sooner we can eradicate Windows 7 the better.
The one thing I liked about developing for OS X (before Apple lost their mind and created the Metal API), was that users had no objection to upgrading to run new software. I never had to worry about my software using an OSX 10.x+ feature and the end-user stubbornly using OS X 10.y.
This version includes the performance optimizations from the 0.9.1 and 0.9.2 pre-releases plus stability improvements. Support for .zip files is gone and .7z loading is more versatile. Custom texture packs should be distributed in .7z form and should have "solid mode" turned off in the 7-zip compression settings for best performance. The texture cache OSD can be toggled and defaults to off now.
Grab it here.[github.com]
https://www.youtube.com/watch?v=4-ig6iU1kwg
Not supporting Windows 7 might make sense for such features if it wasn't a DX9 port of a decade+ old game. I could understand not supporting it in a brand new AAA game that absolutely needs stuff like this. But if you need something like that to make a port of a game like this to improve/make it work better. Then I think something else is wrong.
OF Course, this is you doing stuff from the outside in and not the other way around. So that's a different story.
I don't have the option of not supporting Windows 7. So what happens most of the time is something's bugged in Windows 7 and I have to fix it. Your argument about "if it ain't broken, don't fix it" kind of boils down to "it's broken, let the developer work around it."
http://i1-news.softpedia-static.com/images/news2/How-to-Change-the-Ugly-Windows-10-Icons-475062-6.jpg
I like when windows looks like this http://toastytech.com/guis/win7screenres.png
and the start menu on windows 7 doesnt look painful as on 10
If you go into it expecting to click a bunch of things to get to an application, it's annoying. Instead you just type the first two or three letters of the app you want and you've got all sorts of context menus (e.g. the application, web searches related to it, recent documents edited with it). It's actually more annoying to use the WIndows 7 or older start menu now by a lot.
http://steamcommunity.com/sharedfiles/filedetails/?id=737936094
Most of the Windows-related problems I run into during development are resolved in Windows 8 and by extension included in Windows 10. You just sort of get the best of both worlds with 10, a polished user experience plus the numerous enhancements under the hood that Windows 8 brought. Plus it's free :)