thanks for the information muchly appreciated
thanks for the information muchly appreciated
pay no attention to brandter, their head is so far in the sand they can greet satan.
It sounds like you have a Memory issue, try going into the bios and raising the command rate from 1n/1t to 2n/2t or just disabling XMP/DOCP.
Software issues don't tend to go from working one moment to not working another, they are consistently reproducible across multiple systems when the same set of drivers and hardware are in use, the only component which could result in such variable behavior is Memory corrupting.
i've gamed (and programmed on) Commodore 128, early x86 up thru to these multicore high density monsters, and learned first hand just how weird software can get when hardware issues are present.
Last edited by Puss_Kat; 01-15-2022 at 01:52 AM.
well the game launched just fine no error message ty
Last edited by Corpzey; 01-15-2022 at 09:43 AM.
Again, your background is completely irrelevant unless you work with the FF code. 99% of what have written has nothing to do with the issues people are having, and nothing you have written has helped anyone. You have shown that you have zero ideas of how software development works, you're stuck on blaming hardware issues because in your small world hardware is the only thing that can cause software issues, which is so impressively dumb that not a single software developer ever would listen to anything that you write. Sofware can cause, will cause, and have ALWAYS caused hardware to bug out and crash games and applications, it has nothing to do with the hardware being broken, and anyone who states something like playing games on older systems like a C64 knows this! It's because the software was not written for that particular hardware in mind, which is why software development is very, VERY complicated because it's impossible for you to have all different combinations of hardware that are on the market. This is why they need bug/crash reports so that they can see all hardware, what the player did when the game crashed, how long the game was running before the crash and so much more. You programming basic on a C64 is not applicable to anything to what people here are having issues with.pay no attention to brandter, their head is so far in the sand they can greet satan.
It sounds like you have a Memory issue, try going into the bios and raising the command rate from 1n/1t to 2n/2t or just disabling XMP/DOCP.
Software issues don't tend to go from working one moment to not working another, they are consistently reproducible across multiple systems when the same set of drivers and hardware are in use, the only component which could result in such variable behavior is Memory corrupting.
i've gamed (and programmed on) Commodore 128, early x86 up thru to these multicore high density monsters, and learned first hand just how weird software can get when hardware issues are present.
|
|
![]() |
![]() |
![]() |
|
|
Cookie Policy
This website uses cookies. If you do not wish us to set cookies on your device, please do not use the website. Please read the Square Enix cookies policy for more information. Your use of the website is also subject to the terms in the Square Enix website terms of use and privacy policy and by using the website you are accepting those terms. The Square Enix terms of use, privacy policy and cookies policy can also be found through links at the bottom of the page.

Reply With Quote




