When I try to launch tf2 in lawena it fails and shows in the bottom left corner 'Failed to replace cfg files'
I was wondering if anybody else had this problem and knew how to fix it.
ty
When I try to launch tf2 in lawena it fails and shows in the bottom left corner 'Failed to replace cfg files'
I was wondering if anybody else had this problem and knew how to fix it.
ty
Common problem usually happens when theres stuff in your main cfg or custom folders. I believe the solution was to use lawenas specified custom and cfg folder which you can find somehere in the launcher
had this issue a while ago aswell, if u try closing every file explorer window before u launch thats what fixed it for me
doikuCommon problem usually happens when theres stuff in your main cfg or custom folders. I believe the solution was to use lawenas specified custom and cfg folder which you can find somehere in the launcher
So I can’t use my own hud and stuff? Or have I misinterpreted what you’re saying,
zhernhad this issue a while ago aswell, if u try closing every file explorer window before u launch thats what fixed it for me
Would this also include having CFGs tabs open in notepad++ even if that application isn’t open.
zhernhad this issue a while ago aswell, if u try closing every file explorer window before u launch thats what fixed it for me
Would this also include having CFGs tabs open in notepad++ even if that application isn’t open.
i think notepad++ files are fine, but i'd close them anyway just in case
EDOSo I can’t use my own hud and stuff? Or have I misinterpreted what you’re saying,
If you want custom stuff with lawena launched, have all your custom stuff in lawena's custom folder and keep the regular custom folder empty. Once you're down with recording and want to play normally, use regular custom. I forgot if this applies to cfg folder too so might want to expirement that as well.
I don't know if this will help but one time I changed the folder icons in windows explorer for cfg and custom and it fucked lawena. I imagine for that it had to do with not being able to move/del the hidden desktop.ini somehow.