#CONVERT RFACTOR TRACKS TO RFACTOR 2 MOD#
#CONVERT RFACTOR TRACKS TO RFACTOR 2 SOFTWARE#

We have a running alpha version, and no testers who provide solid and helpful feedback. We have basic physics who need work especially on the tire model, which is its very own story with rFactor2. 15 helmets are left to do and no texture artist is motivated to work on it. While the community held its breath waiting, modding within CTDP appears to suffocate. Sometimes for the better, sometimes for the worst.

#CONVERT RFACTOR TRACKS TO RFACTOR 2 MOD#

This has not happened yet and every new build requires to update things on our current alpha of the IFM2009 mod and reexporting the models.

#CONVERT RFACTOR TRACKS TO RFACTOR 2 SOFTWARE#

Software is supposed to evolve and change, but especially interfaces to external components (ie exporters, shaders, physics, packaging) need to be frozen at one point to allow for third-party devs to get things done and build upon it. That’s alright, however what makes it frustrating is, that even after 10 months it feels like developing against a moving target. We discovered several bugs in export tools and shaders, we have been embracing the new platform and sometimes we had setbacks and wrong decisions. And we can understand this, as CTDP is also experiencing the disadvantages of being cutting edge: sometimes you cut yourself. Very few leagues switch and embrace the new platform, even fewer mod teams. For us it feels like the community has been holding it’s breath since the first release of rF2.

This is software, this is normal, however, this has consequences on the community and on the modders in particular. Beta means rFactor2 is not stable and in a constant change. rFactor 2 Beta was released in January and looking back on the past months, we realized, many of our hopes have yet to be fullfiled. We had to adjust and get results with less people, and a smaller mod such as IFM-2009 was just the way to go. To boost morale in the team, we pushed the developed of the IFM-2009 mod forward in favor of F1-1994.

As we wrote a couple of months ago, CTDP has had some hard years and we have awaited rFactor2 with high hopes. We feel in a stalemate situation at the moment. Alexander Curtis on IFM 2009: Before and after….(CTDP)Dahie on IFM 2009: Before and after….(CTDP)Dahie on rfDynHUD avaliable at github.This is the latest developments we want to share with you and so we suggest not to republish every bit in your blog or news. Most of this is not meant as public promotion material. We also like to share some of our experiences we made in the past years of modding. We show our latest work in progress and Making Ofs. This video is out of date, but if you import the FBX instead of from rFactor1, the process is very similar.In this blog we present the recent progress on our current projects. The only realistic option atm, is to use 3DSimed to import the FBX, and export the GMT files. His problem was, ISI and S397 kept changing the technology (Material's) Brendon was waiting for rFactor 2's development to mature before developing Race Track Builders support for rFactor 2 any further. Studio 397 have said to use either 3DS MAX or Blender to import the FBX file, but only the older version of Blender have rFactor 2 tools (made by a individual Traveller), and 3DS MAX has all the tools, but it's expensive.īrendon has said in the past, he was targeting direct output to rFactor2, the same as Bobs Track Builder had direct output to rFactor1. Soon after Studio 397 took over rFactor 2, they changed all the graphics technology, DirectX11, PBR Shaders, Shadow Shaders, which made GJed out dated. Hi, Race Track Builder was designed to be used with rFactor 2's GJed editor (Equivelant to Assetto Corsa's KS Editor) It was basically the same as this youtube tutorial about Maya to GJed, except the FBX file comes from Race Track Builder.

Convert rfactor tracks to rfactor 2