Released March 2021 rFactor 2 Build Release

@Paul Jeffrey A freind found this post by marrs:
MarrsToday at 3:15 PM
Given that we are getting a few reports on some aspects (and a substantial amount of our testers and people at Studio also use it) I would say it's likely we will look at doing some fixes/upgrades in Q1. He is talking about VR.
Will we see this in the near future as the 1st quarter has just about come and gone ?
 
OMG it's a new game for me, now it's so beauty, so crisp.I'm coming from the old UI, and now it's very beauty, there is so much changement !
I have just an issue, it's like the gsync for replay is desactivated or I don't know, but for the replay it's not smooth, but with the old IUi, it's smooth....It's annoys me, ithere is stutter for the replay.
I can't stop hotlaping now, I will post more feelings later.
(Don't want to be like that but I can uninstall AMS2, rF2 is my game the most played and it won't change with all the next improvements, finally it's in a state where nothing can challenge it about FFB/Physics/graphics/content/mod)

edit : after switching to old UI to verify, the new UI has stuttering in the replay in fullscreen, like if the Gsync was off....
 
Last edited:
Andy Bonar said:
One slight issue for me with the new RC.
My dedicated servers are run as a full RF2 install on a machine with no gfx as such. So I have to roll back to the old UI in order to get the steam workshop updates.
I then update to the latest RC after the updates are done.
With the latest RC, I have to have steam running in the background or the servers shut down without getting to the first screen.
Workaround I have found is to run steam in the background but in offline mode, or they will shut down again as soon as I start rf2 on my main machine.
Click to expand...
We have same problem on our servers.
 
I tried the latest release and again can not load any of my tracks in DevMode due to "Could not find TDF definition for material: Armco" and 100+ notifications of every texture in the game.

So I rolled back to the previous stable version.

Is this going to be fixed?
 
I find the cockpit auto-exposure is not enough bright, I don't want it too bright but like the nose cam, with the same value.
20210325005105_1.jpg

20210325005109_1.jpg
 
Mike Cantwell said:
I tried the latest release and again can not load any of my tracks in DevMode due to "Could not find TDF definition for material: Armco" and 100+ notifications of every texture in the game.

So I rolled back to the previous stable version.

Is this going to be fixed?
Click to expand...
No sorry , you need to fix your content. You can press ok and load the track. You have content errors and HAT tags on either in appropriate surfaces or you need to add those materials to the tdf file.
 
Alex Sawczuk said:
No sorry , you need to fix your content. You can press ok and load the track. You have content errors and HAT tags on either in appropriate surfaces or you need to add those materials to the tdf file.
Click to expand...

Alex, can you please give a little more detail in what I must do? I am not sure I understand.
 
OK...so that is in the SCN file, for example where a race surface is true, armco would be false etc?

I still have no idea where to look to fix it. I just tried removing the HAT target from the exporter in Max under the instance drop down and unchecked HAT and exported all the Armco, changed the armco to false in the SCN and the error is still there.

Instance=Armco_001
{
MeshFile=Armco_001.gmt CollTarget=True HATTarget=False ShadowCaster=(Static, Solid)
}
 
Mike Cantwell said:
OK...so that is in the SCN file, for example where a race surface is true, armco would be false etc?

I still have no idea where to look to fix it. I just tried removing the HAT target from the exporter in Max under the instance drop down and unchecked HAT and exported all the Armco, changed the armco to false in the SCN and the error is still there.

Instance=Armco_001
{
MeshFile=Armco_001.gmt CollTarget=True HATTarget=False ShadowCaster=(Static, Solid)
}
Click to expand...

That means that material is still referenced in a mesh which has HATTarget=True then.
This is important because if you drive on such a surface you will get undefined behaviour.
 
Paul Jeffrey said:
A Release Candidate hotfix update has been deployed to the simulation just now, details below:

Latest Release Candidate 3 (Hotfix)
Client 6438124
Dedicated 6438127- Fixed an issue where Steam had to be open to start a Dedicated Server

Cheers
Click to expand...

Thanks for this, wasnt expecting this to be sorted so quickly :-)
 
You must log in or register to reply here.
Back
Top