Installer Steam
connexion
|
langue
简体中文 (chinois simplifié)
繁體中文 (chinois traditionnel)
日本語 (japonais)
한국어 (coréen)
ไทย (thaï)
Български (bulgare)
Čeština (tchèque)
Dansk (danois)
Deutsch (allemand)
English (anglais)
Español - España (espagnol castillan)
Español - Latinoamérica (espagnol d'Amérique latine)
Ελληνικά (grec)
Italiano (italien)
Bahasa Indonesia (indonésien)
Magyar (hongrois)
Nederlands (néerlandais)
Norsk (norvégien)
Polski (polonais)
Português (portugais du Portugal)
Português - Brasil (portugais du Brésil)
Română (roumain)
Русский (russe)
Suomi (finnois)
Svenska (suédois)
Türkçe (turc)
Tiếng Việt (vietnamien)
Українська (ukrainien)
Signaler un problème de traduction
From Readme file issue may be caused by soundcard driver, too. But there is no option to choose acceleration for sound in newer DXDIAG.
Working station: 1360x768 resolution, Nvidia onboard soundcard
Not working: 1280x1024 resolution, Realtek onboard soundcard
(maybe this helps)
EDIT: Contact with support - investigating problem..
the issue has been located with help from Square Enix support.
It's hardware-software problem.
The root case was that I was unable to start Just Cause from 2TB RAID level 0 (stripe) volume with following NTFS parameters reported by FSUTIL:
fsutil fsinfo ntfsinfo d:
NTFS Volume Serial Number : 0xSomething
NTFS Version : 3.1
LFS Version : 2.0
Number Sectors : 0x000000001d1a91ff
Total Clusters : 0x000000001d1a91ff
Free Clusters : 0x0000000014ec09ba
Total Reserved : 0x0000000000000000
Bytes Per Sector : 4096
Bytes Per Physical Sector : 4096
Bytes Per Cluster : 4096
Bytes Per FileRecord Segment : 4096
Clusters Per FileRecord Segment : 1
Mft Valid Data Length : 0x00000000e0a00000
Mft Start Lcn : 0x00000000000c0000
Mft2 Start Lcn : 0x0000000000000002
Mft Zone Start : 0x0000000014060cc0
Mft Zone End : 0x0000000014063200
Resource Manager Identifier : some-long-number
The symphtom was: Just Cause 2 main screen with two arrows rolling/spinning in right bottom corner.
The game never started.
Note that Steam integrity verify tool report status 100% ok in this case.
There are no bad sectors on disks, there are no NTFS errors in filesystem.
However, game loaded sucessfully from non-RAID volumes with following parameters:
SSD drive:
fsutil fsinfo ntfsinfo c:
NTFS Volume Serial Number : 0xSomething
NTFS Version : 3.1
LFS Version : 2.0
Number Sectors : 0x000000001dc42fff
Total Clusters : 0x0000000003b885ff
Free Clusters : 0x0000000002db83ee
Total Reserved : 0x0000000000000fe0
Bytes Per Sector : 512
Bytes Per Physical Sector : 512
Bytes Per Cluster : 4096
Bytes Per FileRecord Segment : 1024
Clusters Per FileRecord Segment : 0
Mft Valid Data Length : 0x000000000d480000
Mft Start Lcn : 0x00000000000c0000
Mft2 Start Lcn : 0x0000000000000002
Mft Zone Start : 0x0000000001dff620
Mft Zone End : 0x0000000001e06be0
Resource Manager Identifier : some-long-number
USB drive:
fsutil fsinfo ntfsinfo p:
NTFS Volume Serial Number : 0xSomething
NTFS Version : 3.1
LFS Version : 1.1
Number Sectors : 0x0000000071e16fff
Total Clusters : 0x000000000e3c2dff
Free Clusters : 0x000000000571de1d
Total Reserved : 0x0000000000000040
Bytes Per Sector : 512
Bytes Per Physical Sector : 512
Bytes Per Cluster : 4096
Bytes Per FileRecord Segment : 1024
Clusters Per FileRecord Segment : 0
Mft Valid Data Length : 0x000000001b780000
Mft Start Lcn : 0x00000000000c0000
Mft2 Start Lcn : 0x0000000000000002
Mft Zone Start : 0x0000000008c39880
Mft Zone End : 0x0000000008c460a0
Resource Manager Identifier : some-long-number
and single 2TB drive:
NTFS Volume Serial Number : 0xSomething
NTFS Version : 3.1
LFS Version : 2.0
Number Sectors : 0x00000000e8e077ff
Total Clusters : 0x000000001d1c0eff
Free Clusters : 0x00000000015121e6
Total Reserved : 0x0000000000064580
Bytes Per Sector : 512
Bytes Per Physical Sector : 4096
Bytes Per Cluster : 4096
Bytes Per FileRecord Segment : 1024
Clusters Per FileRecord Segment : 0
Mft Valid Data Length : 0x000000003c1c0000
Mft Start Lcn : 0x00000000000c0000
Mft2 Start Lcn : 0x0000000000000002
Mft Zone Start : 0x00000000113201e0
Mft Zone End : 0x000000001132bfc0
Resource Manager Identifier : some-long-number
Please note differences in:
Total Reserved
Bytes Per Sector
Bytes Per Physical Sector
Bytes Per FileRecord Segment
Clusters Per FileRecord Segment
These differences make this game unable to start..
Affected Steam version:
23 Apr 2014 13:50:57
Steam API: v014
Steam package versions: 1398287272 / 1398287272
and all earlier since around April 2013..
Other games may be also affected.
Hope Square Enix notifies Steam Support about this problem soon..
EDIT: More (possible) affected games:
Carrier Command: Gaea Mission
(game not starting)
Saints Row: The third
(game crashing after second movie)
Saints Row 2
(stucks at LOADING 5% on black screen)
WORKAROUND:
Both Saints Row versions are confirmed to work on volume with different sector size.
So they are affected, too.
1. Make a backup of the game
2. Remove it from Steam's library
3. Restore it to different drive
4. Wait until download of executable finishes
5. Play and have fun..
Carrier Command doesn't work either. But it loads settings from this volume all the time.
UPDATE: Carrier Command is confirmed and is also affected!
Most of games will work. Only few are affected.
WORKAROUND for Carrier Command: Gaea Mission
Go to thread http://steamcommunity.com/app/65740/discussions/0/864973981198247582/