themediocrity

Well I haven't seen this exact kind of incident but I've had a lot of trouble with the RPG-29. At least since patch 1.08, I've noticed it seems to be extremely underpowered as well (For example, T-72s surving multiple hits to their rear armor). So I'm not sure if the PG-7VR is actually any worse than the PG-29V, it's possible both have been seriously nerfed.

I've got it too but I don't think Battlefront intends on fixing it or even doing something as simple as posting a saved game in the campaign after this mission so we can get around it.

No the error just says "out of memory" currently the page file is around 1.5 GB and the physical memory is around 1 GB but, oddly, when I monitored the whole process with the task manager I found only a very small increase in page file and memory usage leading up to the crash. When it crashed only around 677 MB of the page file (as opposed to the usual 550MB) was in use while no more the 300MB of physical memory was in use by the game. So there was still 800-900 MB of free page file space and around 400 MB of free physical memory when I got the message "out of memory".

Because I get an error message saying as much when it crashes

Was It fixed for anyone? I still can't get past this mission (though now with 1.08 the game runs out of memory eventually and crashes so I don't have to reboot), I guess my next step will be to open the missions in the editor the save them into battles and just play them one at a time. Can anyone send me a save from the next mission? if possible please let me know. EDIT: Okay you can't access the campaign missions from the editor so I guess I'm stuck. [ May 03, 2008, 11:13 AM: Message edited by: themediocrity ]

I understand that some or all of these ideas may be unfeasible but I think these would be cool to have. 1. Withdraw ability and objective. The idea is that through the unit could set you could set a group to withdraw and a place for them to withdraw at. When a unit gets to the selected location it is removed from the map. These units would count as having survived the battle. A withdraw objective could also be added so that the player is given points for each unit from a specific group which withdraws. 2. Updatable Objectives. Have objectives which can be given to the player with a timer and/or trigger delay, Additionally allow objectives to be removed due to timeout or triggers. 3. Messages sent to player. Allow for messages to be transmitted to the player on a timer/trigger delay. This would go well paired with #2. I don't think any of these things are critical they would just open up more possibilities. Feel free to add your own or criticize those above.

I have a similar problem and I have patch 1.03 installed (Battlefront). The only difference is that in my case I get a "this program has encountered a problem and needs to close" message if I surrender and try to go to the next mission like that in addition to a CTD (with no message) if I win. So I can't advance in any direction. I had this problem before and after patching. from 1.02 to 1.03. [ September 16, 2007, 03:09 PM: Message edited by: themediocrity ]

I don't think that minimum range was really a problem since I was often engaging targets over a kilometer away and still was unable to get a kill. I have the 1.02 patch so if the height problem is fixed I shouldn't be suffering from it. I was also experiencing a lot of inaccuracy. The missile almost always missed, overshooting by maybe 50-100m.

Something similar happened to me on "The Screen" mission. I tried to use javelins against T-62MVs at ranges of 400-1700m all of the tanks were completely exposed and some were stationary but almost all of the missiles missed (usually by large margins) and the ones that did hit did nothing. In multiple tries of the scenario I got one kill in maybe 20 attempts and that was only after multiple direct hits.