gossamersolid 155 Posted July 5, 2010 They don't appear in the expansions menu anymore, I tried to move them to the beta folder's root as well and they still won't appear Share this post Link to post Share on other sites
Zipper5 74 Posted July 5, 2010 It's a bug with the beta patches, must be looking for them in the wrong directory. In the mean time, the good ol' -mod= parameter in your shortcut's target line still works. ;) Share this post Link to post Share on other sites
gossamersolid 155 Posted July 6, 2010 It's a bug with the beta patches, must be looking for them in the wrong directory. In the mean time, the good ol' -mod= parameter in your shortcut's target line still works. ;) I know :) I just got pampered by the damn expansions menu... now I'm getting noobified again :) Share this post Link to post Share on other sites
cole 0 Posted July 6, 2010 Maybe it's not even a bug? Bohemia probably wants people to test patches mainly on the vanilla game? Share this post Link to post Share on other sites
CarlGustaffa 4 Posted July 6, 2010 Think I read somewhere that if you use the -mod switch (like the beta do), then you loose all addons from the expansion list. It's logical though. You either use the -mod switch to set it up, or you use the expansions menu to set it up. What happens if you remove the beta mod switch, won't you get it as part of expansions? If not, then there is a problem (at least for me, future sound mods etc). Share this post Link to post Share on other sites
Cyborg11 10 Posted July 6, 2010 (edited) It's not a bug. If you use the -mod parameter in the target line you can't select mods from the expansions menu. Do this: - If you have the beta folder already (from ArmA 2 beta patches) then delete it - Take your beta folder from Expansions\beta and copy it in your ArmA 2 root folder - Go in beta\Expansions then and take the dta folder and put it in your beta folder - Now remove the -mod= parameter from your beta shortcut, change the path of your target to the right folder ...\ArmA 2\beta instead of ...\ArmA 2\Expansions\beta, start the game and choose the beta patch from your Expansions menu.The target line should now look like this: "C:\Program Files\Bohemia Interactive\ArmA 2\beta\arma2oa.exe" -nosplash And the beta folder should contain the following: Did it and it's working Edited July 6, 2010 by Cyborg11 Share this post Link to post Share on other sites
gossamersolid 155 Posted July 6, 2010 It's not a bug. If you use the -mod parameter in the target line you can't select mods from the expansions menu.Do this: - Take your beta folder from Expansions\beta and copy it in your ArmA 2 root folder - Go in beta\Expansions then and take the dta folder and put it in your beta folder - Now remove the -mod= parameter from your beta shortcut, start the game and select the beta patch under Expansions Did it and it's working :yay: too many bananas dancing, don't know if I should trust :D Share this post Link to post Share on other sites
evilfury 0 Posted July 6, 2010 Not working for me. Error at game launch. Share this post Link to post Share on other sites
Cyborg11 10 Posted July 6, 2010 Which error? How do you start the beta? Share this post Link to post Share on other sites
evilfury 0 Posted July 6, 2010 Its working now. I had to do clean install. These method works perfectly. Gj Cyborg Share this post Link to post Share on other sites
Cyborg11 10 Posted July 6, 2010 I forgot: You have to delete your old beta folder! If you don't do that you will get errors :D Share this post Link to post Share on other sites
ahmedjbh 0 Posted July 6, 2010 I get error on start up: no entry ".profilepathstartup" then gives shades error mismatch, then crashes to desktop. Share this post Link to post Share on other sites
Cyborg11 10 Posted July 6, 2010 (edited) SRY GUYS! Forgot to mention that you have to change the path in the target line of your shortcut. :o I'll edit my post on page 1 now. The target line of your shortcut should look like this: "C:\Program Files\Bohemia Interactive\ArmA 2\beta\arma2oa.exe" -nosplash And your beta folder should look like this: Edited July 6, 2010 by Cyborg11 Share this post Link to post Share on other sites
ahmedjbh 0 Posted July 6, 2010 hmm, i still cant get it to work. Share this post Link to post Share on other sites
Cyborg11 10 Posted July 7, 2010 You are sure that you start your beta patch with the created shortcut? Only remove the -mod= parameter from your target line and it should work. This is my shortcut: Share this post Link to post Share on other sites
ahmedjbh 0 Posted July 7, 2010 its working now, i did a clean install and followed the instructions. The new recoil+super smooth play+ace = very late night! Thanks Cyborg, may God reward you! Share this post Link to post Share on other sites
Zipper5 74 Posted July 8, 2010 As far as I know, ACE2 will be overriding the new beta recoil if you're using them in conjunction with each other, so the new recoil you speak of in your post, ahmedjbh, is just ACE2's same old recoil... Share this post Link to post Share on other sites
ahmedjbh 0 Posted July 8, 2010 nope, its very different. When you fire, then gun doesnt go back down. ACE never had that, at least not for me. I had it working without ace, as I said above, adding the ace made no obvious difference to the recoil. Share this post Link to post Share on other sites
langgis08 10 Posted July 8, 2010 ... I get an error with the new beta 71952 when I try your method step by step, cyborg, as follows "no entry 'bin\config.bin/CfgVehicles/All.artilleryTarget'." what am I doing wrong , any clues ? :-) Share this post Link to post Share on other sites
Cyborg11 10 Posted July 8, 2010 Everyone has the same error if you use the beta that way. Solution for now: Run the beta shortcut in your arma 2 folder and set your mods with the -mod= parameter. Trying to find a fix for this. ;) Share this post Link to post Share on other sites
langgis08 10 Posted July 8, 2010 Sethos had same error, but without your method ... perhaps here's a junction/hint ? http://forums.bistudio.com/showpost.php?p=1675933&postcount=11 Share this post Link to post Share on other sites
Cyborg11 10 Posted July 8, 2010 I found out something interesting: If you are using the -mod=beta it works with my method but the modlauncher is unusable again :p It seems like that the modlauncher can't launch the beta bin.pbo file. This is the reason why we get the errors :( Or maybe it's overwritten by OA? Don't know. :j: Can't find a solution to get both working :( Share this post Link to post Share on other sites