UI v1.0e not found or damaged.

Hi guys,

The game won't start here
I get into the launcher, click to play offline and I get the message that the UI v1.0e is damaged, missing or something else and it is unable to continue.

Now......that might be my own fault; I may have played around with it in the past but I can't remember........
Anyway; would someone please send me the stock file, the rfcmp from the UI, version 1.0e so I can test?

Might be a bit of a "bug" I think; guys with other UI versions, can get this same problem?

 

Have you installed the beta on top of the old rF2 install?

 

Are you not supposed to do this? Because that's what I did.

 

Ehhhh......yes I did........have no HD room to spare........

It's my own fault; if it doesn't work out, I just have to find a new hobby

 

Well I`ve not played around with anything like that but I don`t have any problems with the sim starting...

I`ve tried all the UI`s... the original and the minimalist and everything works fine.

Maybe youv`e altered something whilst "playing" Nav?

 

I might have, yes.
But I also have other UI's in there.......so it should "pick just one" right?

 

Don't do that!!!

 

Thanks, I know that now. Doesn't really help anymore.......

Forget I asked; I'll figure it out myself or find a new hobby indeed.

 

I think this happens when you point the new core to a datapath that haven't been updated yet. To fix this you should be able to rerun the installer and when it prompts for the core just select some temporary folder that you can delete later and then when it prompts for the datapath just select the one that is giving you a problem.

Before trying that, in the launcher select the advanced tab and then check the box that tells it to reset to the default UI.

 

I installed the new unstable on top of the last unstable, both core and data. The only thing I share with the stable version is the packages directory.
All the configurations were converted and maintained, no issues here. Everything working fine so far using the 64 bits version.

 

For me this happened as well in internal testing. It turned out I somehow had got an extra Core folder inside my datapath rF2 folder, which contained outdated UI information. Solution was simply to delete the extra Core folder. I have no idea how it got there, but this happened once last year as well so don't think it's build related.