Build 660 Released

Status
Not open for further replies.
In my configuration changing resolution, AA or HDR settings in game turn the screen black during a certain time: between 2 to 5 seconds, and then I'm back in main rF2 menu (not the video settings) and all is fine. we don' have tons of games/sims/applications allowing us to change such settings "on-the-fly" and usually it's made in a separate launcher or configuration tools. I agree if they appear in game it's better if it work ;) If it's too much a pain, I'll will not cry during weeks if those ingame settings disappear.
 
When I try to change resolution or AA settings from within the game I get a crash to desktop - "rFactor 2 has stopped working", this has happened to me for a few recent builds. Not a big problem because I just use the "configure sim" thing from the launcher.
 
I often get "rFactor 2 has stopped working" after I minimize or close the main game (with the launcher still going). I actually got that twice last night without booting the game, just with the launcher on and looking around the account tabs and Manage Mods.
 
Guimengo said:
I often get "rFactor 2 has stopped working" after I minimize or close the main game (with the launcher still going). I actually got that twice last night without booting the game, just with the launcher on and looking around the account tabs and Manage Mods.
Click to expand...
When reporting something like this, please mention if you have any plugins? Thanks :)
 
Those of you getting black flashes or crashes, do any of you have system logs from error reporting? For example to say if a video driver is crashing, etc?
 
Still fighting the "no Launcher" problem..........can't play the game!!!!! Every other program on the computer works fine except rf2....????


Log Name: Application
Source: Application Error
Date: 4/29/2014 1:37:17 PM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: Paul-PC
Description:
Faulting application name: Launch rFactor.exe, version: 0.0.0.0, time stamp: 0x533ef889
Faulting module name: MSVCR110.dll, version: 11.0.51106.1, time stamp: 0x5098858e
Exception code: 0x40000015
Fault offset: 0x000a327c
Faulting process id: 0xed0
Faulting application start time: 0x01cf63eace3a6890
Faulting application path: C:\Program Files (x86)\rFactor2\Launch rFactor.exe
Faulting module path: C:\Windows\system32\MSVCR110.dll
Report Id: 0d616e3b-cfde-11e3-90be-00248c85b33d
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2014-04-29T20:37:17.000000000Z" />
<EventRecordID>32380</EventRecordID>
<Channel>Application</Channel>
<Computer>Paul-PC</Computer>
<Security />
</System>
<EventData>
<Data>Launch rFactor.exe</Data>
<Data>0.0.0.0</Data>
<Data>533ef889</Data>
<Data>MSVCR110.dll</Data>
<Data>11.0.51106.1</Data>
<Data>5098858e</Data>
<Data>40000015</Data>
<Data>000a327c</Data>
<Data>ed0</Data>
<Data>01cf63eace3a6890</Data>
<Data>C:\Program Files (x86)\rFactor2\Launch rFactor.exe</Data>
<Data>C:\Windows\system32\MSVCR110.dll</Data>
<Data>0d616e3b-cfde-11e3-90be-00248c85b33d</Data>
</EventData>
</Event>

I've done all the fooling around with the dll's previously and decided to copy these from a working copy of Windows/rF2 but now I get this again....it's either this or the 0xc000007b error which supposedly is connected.......my mind is a blur over this!

Help
 
pn6 said:
Still fighting the "no Launcher" problem..........can't play the game!!!!! Every other program on the computer works fine except rf2....????
Click to expand...

Found my fix for this and just posted it in the Bug Reports section

http://isiforums.net/f/showthread.php/19643-Launcher-broken-APPCRASH-MSVCR110-dll

Fix is simply to remove your Credentials file from the folder: Appdata -> Roaming -> rfactor

If the launcher works again after you remove it, just Login again and the file will be recreated, see if that fixes it for you.
 
Great find Hectari, FWIW I've just tried corrupting my credentials file and now I too can get the launcher to crash on start up and it throws the same faulting module.

Weird thing is that DLL is the 64bit version or at least the path is the where the 64bit version should be. The launcher appears to only use the 32bit version (SysWOW64) both when working normally and when I made it crash.
 
Hi Folks,

Did a quick search of this thread and didn't see anything relevant to my issue, maybe it is posted elsewhere?

Wanted to host a race with inclimate weather - brought Dedi as follows:

View attachment 12551

Race was set for 10 laps as a test... Since the are 5 segments in the WETs file... You would think that 2 laps represented each segment.

Results: Rain started 30 secs into the first lap and stopped after 2.2 laps ..... NOT what I expected !!!

This happening to anyone else???

Any ideas???

THANKS in advice for any help !!!
 
Last edited by a moderator:
Not sure if I mentioned it here, but the random daytime session start time for practices is now stuck on 9:30 am. Only one track (the impressive new Hockenheim) that I have used still functions as random (the way all did prior to 660). It seems as if I turn off HDR and turn it back on, the randomness comes back until I restart rF2. Haven't tried it without HDR after a restart because I am an HDR fan.
 
Tim Wheatley said:
Those of you getting black flashes or crashes, do any of you have system logs from error reporting? For example to say if a video driver is crashing, etc?
Click to expand...

This is the error logged after I try to change resolution in game triggering a crash to desktop:
Faulting application name: rFactor2.exe, version: 1.6.6.0, time stamp: 0x534c454d
Faulting module name: d3d9.dll, version: 0.94.0.0, time stamp: 0x51738d87
Exception code: 0xc0000005
Fault offset: 0x00038623
Faulting process ID: 0x166c
Faulting application start time: 0x01cf644dcb2cc04e
Faulting application path: C:\Program Files (x86)\rFactor2\Core\rFactor2.exe
Faulting module path: C:\Program Files (x86)\rFactor2\Core\d3d9.dll
Report ID: 18eef68f-d041-11e3-bf3e-bc5ff497f41e
Faulting package full name:
Faulting package-relative application ID:
Click to expand...

I have the pedal overlay plugin
 
The faulting d3d9.dll file in your Core folder is not a default rF2 file. You have some plugin installed (might be the pedal overlay, I don't have it so can't comment) that uses that file or you might have downloaded the 'clamp fix' DLL that was posted over at the GeForce forums.
 
What exactly means: Report some inner tire temperatures to plugins

All temperatures in TelemWheelV01.mTemperature array are always 0
 
Status
Not open for further replies.
Back
Top