theavonlady 2 Posted July 20, 2004 I will try and find the conflicting .pbo and I will post it here then at least other people will be able to avoid it. It's most probably file BAS_MH47E_185.pbo - their Chinooks. edit: what file date do you have for file BAS_MH47E_185.pbo? Share this post Link to post Share on other sites
The_Oakster 0 Posted July 20, 2004 22 April 2003 for BAS_MH47E_185.pbo and 21 April 2003 for BAS_MH47E.pbo Share this post Link to post Share on other sites
theavonlady 2 Posted July 20, 2004 22 April 2003 for BAS_MH47E_185.pbo and 21 April 2003 for BAS_MH47E.pbo OK. Those are the latest. So those are likely the troublemakers. Share this post Link to post Share on other sites
The_Oakster 0 Posted July 20, 2004 Is it something that can be changed in the fire.sqs, (dont know that much about scripting) or is it just one of those things? Share this post Link to post Share on other sites
theavonlady 2 Posted July 20, 2004 Is it something that can be changed in the fire.sqs, (dont know that much about scripting) or is it just one of those things? Â There is no reference in fire.sqs to BAS specifically. The fact is I can run the mission without any BAS addons in my mod folders and I get no error. Maybe just the mention of TJ's name in the comments therein causes BAS addons to shout hello. Share this post Link to post Share on other sites
The_Oakster 0 Posted July 20, 2004 Just to confirm it... I removed the bas mod folder and no error message! Cheers for taking time to help me out Share this post Link to post Share on other sites