BAM 0 Posted March 21, 2002 Hi. Im new to these forums, but ive been playing the game for a long time. There are some bugs which I have noticed, and would like to see if: A - are others experiencing them? B - Are Codemasters / BIS aware of these bugs and planning on addressing them in future patches? My OFP and system details: Operation Flashpoint Gold Edition, patched to the official v1.46 version. Windows ME P3 800E 3DFx Voodoo3 3000 AGP with final official drivers 1.07.00 WHQL DirectX 8.1 512Mb SDRAM ABIT BE6 Motherboard with latest BIOS revision The first problem - smoke/cloudets come out of parachutes I never noticed this one in the original flashpoint 1985 campaign, but I did recently see it in Red Hammer, mission 4. I replayed the mission several times, restarted the game and even the computer and I still seen this occuring on several of my mission restarts. Here are some screenshots: The second problem - the ENGAGE command from the command menu does not work as its supposed to (as described in the instruction manual). Ok, im pretty sure that others are aware of this problem, as its present in the great "Commanders Guide v1.2" (thanks to Zovirl who wrote it) which you can find on the site of AvonLady (thanks Avonlady, great site and FAQ!!. Ok the problem, well, when you command any of your troops to ENGAGE the enemy, they do so, BUT if you have them under the HOLD FIRE command, they disregard this and fire anyway, as soon as they are in a position to shoot. This action seems to represent the ENGAGE AT WILL command, its just as if the ENGAGE command is the exact same as this... Here is the description of the command from the manual: ENGAGE "Provided the HOLD FIRE command has been issued, advance to bring enemy into firing range and await fire command. Otherwise, advance and open fire as soon as target is in range." As it says here, the troops who are engaging should continue to hold fire and await the FIRE command, rather than just firing immediately. Ok, so why am I making a fuss about this seeminly trivial problem? Well, this command, if it worked as intended, would be really useful. As it stands now, it does take away from the gameplay, and makes it more complex for the player to set up and execute ambushes etc.. in the game (especially for commanding any of your remote snipers). It would be great if this glitch was addressed, it sounds like it would be pretty simple to get the soldiers to maintain the HOLD FIRE state, but im not one of the programmers so I wouldnt really know The Third problem - random crashes to the desktop Ok, I know that this one cant really be proven to be 100% the fault of the game, but the facts are that I previously ran the game on version 1.10 for about 2 months solid and -NEVER- had a crash to the desktop. Since uninstalling this 1.10 version completely which I had borrowed from a friend, and cleanly installing my newly purchased Gold Edition pack (which starts at v1.30) then going straight to v1.46 via the patch, ive had very frequent crashes to the desktop, with no error messages to explain why. With no exaggeration whatsoever, I would say that about 75% of the games I play will end in a crash to the desktop. I know that there are a lot of possibilites of why a game could be crashing, but my previous 1.10 install was rock solid. Is anyone else experiencing a sudden drop in stability after upgrading to 1.46? Well, thats the lot, thanks for reading! Regards, BAM:) Share this post Link to post Share on other sites
SpaceAlex 0 Posted March 21, 2002 That parachute smoke is a bug. It's pretty funny. It's strange that BIS didn't fix this bug. Maybe in the next patch. Who knows? Share this post Link to post Share on other sites
theavonlady 2 Posted March 21, 2002 </span><table border="0" align="center" width="95%" cellpadding="3" cellspacing="1"><tr><td>Quote (BAM @ Mar. 21 2002,03:57)</td></tr><tr><td id="QUOTE">ENGAGE "Provided the HOLD FIRE command has been issued, advance to bring enemy into firing range and await fire command. Â Otherwise, advance and open fire as soon as target is in range." As it says here, the troops who are engaging should continue to hold fire and await the FIRE command, rather than just firing immediately.<span id='postcolor'> Search The FAQ for "commander guide" and see what it says about ENGAGE\HOLD FIRE. Share this post Link to post Share on other sites
deady 0 Posted March 21, 2002 </span><table border="0" align="center" width="95%" cellpadding="3" cellspacing="1"><tr><td>Quote (BAM @ Mar. 21 2002,02:57)</td></tr><tr><td id="QUOTE">Ok, im pretty sure that others are aware of this problem, as its present in the great "Commanders Guide v1.2" (thanks to Zovirl who wrote it) which you can find on the site of AvonLady (thanks Avonlady, great site and FAQ!!.<span id='postcolor'> I think he knows about it already :| Share this post Link to post Share on other sites
theavonlady 2 Posted March 21, 2002 </span><table border="0" align="center" width="95%" cellpadding="3" cellspacing="1"><tr><td>Quote (Deady @ Mar. 21 2002,12:52)</td></tr><tr><td id="QUOTE">I think he knows about it already :|<span id='postcolor'> Must read the fine print. Share this post Link to post Share on other sites
