Page 1 of 1

Profiles issues

Posted: 2016-07-07 06:58
by PLODDITHANLEY
I try to help out guys with problems as no one else regularly does, (blind leading the blind) I've noticed many many guys with an issue that seems to be creating the profiles.

The first sign is in specs - no details are shown about monitor or GPU after getting insta crashes on launch.

A lot of the time it's W10 guys but also a few holding on the W7, I wonder if it is some permissions issue, my profiles folders are rather oddly marked read only when they clearly aren't. At one point windows onedrive seemed in some way responsible but now I don't think so.

If anyone has any clue what might be causing this frequent issue and needs more info don't hesitate to ask

This other error pops up too but seems to be DX install problem, but sometimes seems to be solved by importing virgin profiles.

Image
FIXED IT! okay after all that.... When you extracted into other folder. Even if it errors on install. Let it keep installing. After game installs. Go to your extracted files location. now go to the DEPENDENCIES folder. Open Directx folder and scroll down till you find the Setup. Run it.. Now run your game. Do the updates and hit play. Game should run now. Worked for me.
Where/what is the dependency folders

Re: Profiles issues

Posted: 2016-07-07 12:42
by Mats391
PLODDITHANLEY wrote:I try to help out guys with problems as no one else regularly does, (blind leading the blind) I've noticed many many guys with an issue that seems to be creating the profiles.

The first sign is in specs - no details are shown about monitor or GPU after getting insta crashes on launch.

A lot of the time it's W10 guys but also a few holding on the W7, I wonder if it is some permissions issue, my profiles folders are rather oddly marked read only when they clearly aren't. At one point windows onedrive seemed in some way responsible but now I don't think so.

If anyone has any clue what might be causing this frequent issue and needs more info don't hesitate to ask
The profile files are meant to be readonly. It does not really matter either way as the Launcher is meant to run as admin and can read them always.
The GPU not being detected is weird and likely the cause of the crash as it might set wrong resolution+refresh rate.

PLODDITHANLEY wrote: This other error pops up too but seems to be DX install problem, but sometimes seems to be solved by importing virgin profiles.

Image
I know this error from errors in python when python is unable to load the proper gamemode file. I doubt this is the case tho as no one should have modified those. It also is only an issue if you create local games.
PLODDITHANLEY wrote: Where/what is the dependency folders
Unzip or open the prbf2_1.3.5.0_full.iso and in there is the depedencies folder. It is just plain old directX 9 and you can download it from anywhere you like (i suggest MS website ;) ). It should also install automatically when installing PR, but might be buggy on Win10 etc.

Re: Profiles issues

Posted: 2016-08-18 23:23
by PLODDITHANLEY
This is a good example of the most frequent installation problem, I'm not sure what the solution is.

Sometimes erasing profiles and recreating, using other profiles, changing to read only permission. Some people have got round it by using BF2 profiles.

Its around once a week someone turns up with it.

I even wondered about using a offline DX9 installer as it is so old maybe the online doesn't bother about it sonetimes??
DX 11.2 indicates the DX 'Feature level' your graphics card is capable of running.

- It's a common misconception that Win7/8/8.1 has only DX 11, and Win10 has only DX12.
Win7/8/8.1/10 all have of DX - 9,10 and 11.

- The following is a list of the Direct X .dll's you will have when the files are up to date.
Go to the Windows / System 32 folder, (and SysWOW64 if you have 64bit).
They are in alphabetical order and will start with d3dx9 - 24 > 43 . Then d3dx10 - 33 > 43 & finally d3dx11 - 42 > 43.
There should also be - d3d9, d3d10 and d3d11 (among others).

These come before the D3Dcompilers-33>43+47.
- Win10 currently has only two d3d 12 files. One in System 32,and SysWOW64 .
- There are more DX files, but these are most of the graphics related Direct X .dll's

- When using a 'clean' Windows install it's advisable to run the DirectX Web Installer to 'update' DX.
Note that the Web Installer only installs 'missing' files and does not overwrite corrupt files as does

the full DX Redist installer.



Download DirectX End-User Runtime Web Installer from Official Microsoft Download Center

- Another common misconception is that you need to install DX 9.0c to run older DX9 games. Not so.
This version has been superseded by the DX Redist (June 2010) which has all of the DX9.0c files and more.

This installer is the best option if DirectX files are corrupted.


Download Details - Microsoft Download Center - DirectX Redist (June 2010)



Note - This is a two step process. The installer download unpacks files to a location of your choice.

You then open the folder and find the DXSETP.exe and run that to reinstall DirectX.
Once the reinstall is complete you can delete the folder the files were unpacked to.

- Another reason for DirectX errors is if your graphics accelerator (either Integrated graphics or graphics card)

does not meet the specifications of the game.
- Outdated audio drivers can also cause DirectX errors in some cases.



However.... (If you are using a disk based version of FIFA 07)

FIFA '07 may be a victim of a malware that MS has built into Win10. This game uses SafeDisk copy protection,

which uses a driver titled secdrv.sys which is being blocked by MS.

I'm not sure, but this game may use a version of SafeDisk that does not rely on the secdrv.sys driver.

You can read more details in my post at --this thread--

http://answers.microsoft.com/en-us/wind ... 89aae764c1

http://answers.microsoft.com/en-us/wind ... 258?auth=1