@manticored said:
Again you don't know how to use "you're" and "your", and yet again you're using the wrong one in a sentence that's being pushed as an insult... The irony...
Apparently you missed my relaxed grammar policy as it doesnt matter. And my single quote key works 50% of the time. Again I've established at being ok with grammar issues. You are still trying to push a dumb idea. I'm owning up to the grammar mistake but I'm not going to bother correcting it. Its of such little importance. Plus you know someone realizes they are wrong once they resort to attacking inconsequential things like grammar... like who the **** cares?
Yes, prior to online updates if there was an issue large enough to warrant it a publisher or development team would make a revision to the game and re-release it, is that hard to understand? That is what is generally referred to as a public revision, it's the modern day equivalent of an update patch.
Actually no, patches are new versions, thats why in patch notes there is a new version number.
FOR INSTANCE
Dark souls there has both the regulation version and app version listed on the main page.
WoW you can just search patch notes to see all the different versions.
steam/origin you can get the versions going to the about page.
You can get the version of windows 10 your running in the system information
To your bullet points, yes, any modification to game code is a revision of the code, any modification to anything is a revision, but there is a big difference between internal revised code before a release, and public revised code after a release. Why you're incapable of understanding this is beyond me, it's very simple to grasp.
New versions are just new versions... Your making this concept harder trying to make a distinction to updated games with new versions (1.0 -> 1.1) as explicitly being public revisions. Your objectively wrong.
Revision is not a term used very often. Versions get release. Revisions generally mean a specific build of a application. For instance in the examples above, none of them use the term revision. All the patches and updates are new Versions. So again, your idea is fundamentally flawed. As there is no standardization on versioning software. So my usage of the term revision is completely fine. And I explained it to you so I don't know what the problem is. So you should have figured out that my argument is that there may be different... builds of the game that are undocumented.
There is no public revision to the NTSC release of The Need for Speed on the Saturn, I don't know how many more ways this can be reiterated for that to sink in.
You can't prove that though, and its not out of the question that some manufacturer got in updated version. Or a greatest hits casing sometimes included an updated build without adding a new public version. Like I mentioned previously there is a huge problem with the pre internet age that many things could go undocumented or lost on some guys PC. It was not uncommon that some specific person's PC was responsible for creating a released build for manufacturing. That guy quits you might end up with a different revision without even knowing it because it wasn't documented. Or if you change who's printing your game, your might accidentally release a different revision.
The fact remains this type of information is unreliable because of the types of software practices that were used in the 90's.
Just because they are binary compatible doesn't mean that they are free from compatibility errors due to variations in their software design and operation. You're treating compatibility as if it's a black and white plane of code operation free of anomalies and errors, compatibility ensures functionality, not a set level or scope of functionality. I don't need it to be true, it is true, what you're saying is so feeble in argument stance that you're actually hamstringing this to a scratched disc which is absurd or a mysterious game revision that doesn't even exist instead of the obvious, the game running into compatibility problems because it's being operated on a foreign Saturn and certain coded elements are incompatible.
Binary compatibly means exactly that. The way the game communicates with the OS would be identical. And these games more often communicated directly with hardware or really thin abstracted layers. If there was a bug in the API for the os then it would be a bug that persists with all software that use the API.
Now lets get back to my disc scratch assertion... thats more likely the cause than a incompatibly issue. Where you can load the music in some circumstances like on the title screen but not others ? If you have a problem with loading/playing music you likely will have a problem with ALL music.
Whats that... the same refute you used for a disc scratch?
Also this is the second time you've stated that you're leaving, please do so.
Those statements are more out of bewilderment over your stupidity.
And lets not forget the most likely cause is they made a mistake and it will likely end up corrected. Your attack on their credibility is dumb to begin with. Ockham's razor blah blah
Log in to comment