Cromewell

You do realize that you could implement every single other padlock idea we have mentioned in this thread all together, and it wouldn't approach the programming complexity of LoS calculation? -SK The radar and eos already does a LoS calculation, wouldn't it be a realitively simple matter of adjusting the code to work with the padlock function?

I put this in the other thread because I hadn't read this one yet..but I might as well put it here I would like to have it so that you can't padlock a plane in visual range that you can't actually see because they are behind a mountain. I understand this is probably hard to implement but it would be nice

if you can actually see them, padlock is all well and good but when you padlock someone you shouldn't be able to see, I agree it's a cheat. I don't own a trackIR but at least the people who do have to be able to see you to make use of it. would it be possible to remove padlocks ability to lock onto targets you cant see? ie. they are behind a mountain, or maybe even a cloud

Oh ok you get it upon exit, no loss then :P Some clean up operations run before lock on exits (when you click 'exit') and I dont think that they perform the same on any 2 systems and so some people get this error where lock on is reading outside its heap/stack range instead freeing its allocated pointer arrays and such which reside in the heap. Theres not alot you can do about it, I used to get it all the time on my old system but my new one doesn't have a problem

I like the Su25 better than the a10 simply because its got a better weapon variety, and it flies faster

Usually this error is caused when a program reads outside its allocated resources, most often from exceeding array bounds. It's weird that it started when you upgraded your RAM