Was FSXSE originally located in a Steam Library in "C:\Program Files"?

 

Nope

 

E:\Steam

Bjoern,

I am having same problem.

 

MY STEAM  locates in "C:\ Program Files (x86)

 

Not in "Program Files

 

Do I need to switch locations?

Thanks

Bjoern,

I am having same problem.

 

MY STEAM  locates in "C:\ Program Files (x86)

 

Not in "Program Files

 

Do I need to switch locations?

Thanks

I recommend moving to a different drive, if you have one, or into a folder, i/e. FSX-SE, on its own in the root directory, ie. C:\FSX-SE\etc\

My STEAM Location:

 

C:\Program Files(x86)>Steam>SteamAPPS>Common>FSX

 

You advise  to move:

 

C:\FSX-SE

 

Do I need uninstall STEAM  and reinstall to C:FSX-SE

You need to uninstall FSX-SE and Steam.

 

Then re-install Steam in C:\

 

Then re-install FSX-SE with will automatically go in your Steam folder and will look like this:

 

C:\Steam>SteamAPPS>Common>FSX

OK..

Thanks. I am going to do that.

You need to uninstall FSX-SE and Steam.

 

Then re-install Steam in C:\

 

Then re-install FSX-SE with will automatically go in your Steam folder and will look like this:

 

C:\Steam>SteamAPPS>Common>FSX

That's what I meant, but as I'm getting another 777-300ER long-range flight ready, missed that step.

I have concluded that there's an issue with stablity in FSX-SE whenever you fly for long durations.

 

Based on Dovetail's Steam Support forum, they are aware of the issue and is working on a fix. Please see source comment....

 

[uPDATE]

This information is based on a response from a user that received a response on the issue from Dovetail's support. I have not yet found a direct response from Dovetail that they're working on the issue. If anyone else has received a similar response, let us know for confirmation.

 

SOURCE:

http://steamcommunity.com/app/314160/discussions/1/612823460253102801/

Well, I also wrote them an email, and got a confimation - that they received my email - It said "We'll be in touch"

 

That was three days ago......

 

regards

I really don't see how they can "fix" it. The program is the same as FSX/Acceleration except they were allowed to modify it the installation so it would work on Steam. I think they threw in some tweaks and changed some of the settings like Texture_Max_Load from 1024 to 4096. They cannot touch the code. This is as stated in the FSX Forum by Dovetail representatives and on the AVSIM Front Page where we interviewed one of the developers. If it was happening to everyone I would be concerned but it is not happening to everyone who has FSX-SE installed.

 

Best regards,

I really don't see how they can "fix" it.....They cannot touch the code. This is as stated in the FSX Forum by Dovetail representatives and on the AVSIM Front Page where we interviewed one of the developers. 

 

except that's not what he said?  a quote here -> ". We can make (and have made) changes to the core software, but we are not at liberty to make significant functionality improvements that rightly would belong in a sequel."

 

i don't think fixing crashes would be considered something 'only for the sequel'... although that is what happened with the original fsx i suppose   it sounds to me like they can't really add features but that getting the existing ones to work correctly with their newly compiled versions would be legit. of course without seeing the actual legal agreement this is all speculation...

 

anyway, based on what the hifi guys have been saying, dovetail is actively addressing bugs so i'm optimistic that at least some of these issues will be solved. it's certainly better than we had before which was basically no dev involvement at all!

 

cheers!

-andy crosby

I really don't see how they can "fix" it. The program is the same as FSX/Acceleration except they were allowed to modify it the installation so it would work on Steam. I think they threw in some tweaks and changed some of the settings like Texture_Max_Load from 1024 to 4096. They cannot touch the code. This is as stated in the FSX Forum by Dovetail representatives and on the AVSIM Front Page where we interviewed one of the developers. If it was happening to everyone I would be concerned but it is not happening to everyone who has FSX-SE installed.

 

Best regards,

 

Well, dovetail has updated FSX:SE with bugfixes in the past - and they did more to the software then just add a few (already well known) tweaks in the standard config. 

 

They changed some core components - which they needed to change to get it working with Steam which is certainly covered by there license agreement.

 

How I understand their agreement is that:

 

They may not change the functionality in core FSX like big changes/improvement to the ATC System or introduce a better Ingame Map feature or rewrite the AI (un)logic....

 

But I'd think, and I'm pretty sure they are allowed to fix bugs - especially if they have introduced them like the terrain.dll bug - because I for instance never had this bug in FSX:ME - exept when I misconfigured something in the terrain.cfg.... 

 

but in a vanilla install - even with crancked up settings I can fly FSX:ME for hours over hours - not that it is a nice experiance with those standard planes etc. (praise to those gifted addon devs.) but it neither OOM'd nor did it crash with any .dll error.....

 

whereas FSX:SE crashes in a vanilla install after pretty much exactly 4 hours..... with a standard plane.....

 

regards

MY reinstallation completed  as  C\: Steam .

 

I made a test flight,  45minutes later  R6025 error appeared and CTD

 

I just gave up. There are no solution from STEAM. 

What is this R6025 error that causes the CTD? I have yet to see it.

Rick,

 

R6025 CTD possible causing by  wrong coding of  STEAM  FSX software. No one knows how to solve this problem, including the STEAM. There are many members are suffering  from this problem.

 

http://imageshack.com/a/img538/6899/dXOL0r.jpg