[Generalgreen]

Not sure how to explain this, but whenever  my shot impacts a hull observing the damage effect (the one that looks like a flame or fire streak coming out of the hull on the point of impact) at a medium or shot range (0-1000m) I my FPS drops to zero, this problem seemed to have appeared after Installing and playing cardinal spear till the mission where you use the neutron flux cannon, then it carried over to the rest of the game, it the problem persists regardless of visual settings and does not cause any error messages at all, the reason i do not want to reinstall is that it may take a long time, and thank you for your time to help me.

[attachment deleted by a basterd]

[FreeSpaceFreak]

Psst, if you're having a problem with FSO, your fs2_open.log would be more helpful - fred2_open.log is for the case you're having problems with FRED.

In your FSO-debug runto generate the log, make sure that the problem does occur, so it's cause should be visible in the log.

[Generalgreen]

Well that was kind of embarrassing , thanks for clarifying that, here is the fs2 log.

[attachment deleted by a basterd]

[FreeSpaceFreak]

Hmm, interesting. Your install appears to be valid (though I haven't compared checksums), you have a reasonably capable graphics card, and you are not trying to overload it with MV_Advanced. In short, I can see no reason why you should have this issue - even though it is there, judging by the frame times in the end.

I would suggest that you try switching soft particles and postprocessing off, and see if the issue still occurs. If that doesn't solve it, try without the MediaVPs (select "No mod" in the launcher), and be sure to let us know what happens.

[Generalgreen]

I did a test run with post processing and soft particles turned off and another with no MediaVps enabled, the problem seemed to have persisted in both cases, I will attach the log with the newest run (the right one hopefully ) And we'll see what happens.

[attachment deleted by a basterd]

[FreeSpaceFreak]

Well, the log clearly shows the lag, but still no indication of the cause. Your VP checksums seem to match up, too, so data corruption is unlikely.

Hm. Try updating your video drivers; be sure to get them from the NVidia website itself, don't trust Microsoft or your computer OEM. Also, please save the file attached in your <FSO>/data directory (same as where fs2_open.log is); it will produce an extended version of the debug log, with additional information (which is usually superfluous, which is why it's not the default). And could you post your OS and system specs?

[attachment deleted by a basterd]

[Generalgreen]

System specs:
OS: Windows 7 Ultimate 64bit.
Processor: Intel core 2 duo P7350 @ 2.00Ghz (2 CPU).
Memory: 4096MB of Ram.
Graphics card: GeForce 9300M GS @2268MB of Visual ram
Running DirectX 11
Also, here is the extended log, I also updated my video card from the Nvidia website recently after the occurrence of this problem, Sadly that did not help

[FreeSpaceFreak]

I think you forgot to attach the log Your system should be able to handle FS just fine (and especially w/o MediaVPs), so that could hardly be the cause indeed...

EDIT: Oh, and since it started after Cardinal Spear - try deleting your <FSO>/data/cache folder, and are you still playing with the same pilot? If so, try creating a new one (not a clone, entirely new). TBH, I'd be surprised if that helps, but I ran out of better ideas :-/

[Generalgreen]

Apparently the attachment was too big (2.67mb), But the good news is, changing the pilot did solve the problem, even though deleting the cache folder didn't help with the first pilot, using another one did eliminate the problem completely, and did give me an FPS boost on higher graphical settings, Thank you for your help, I really do appreciate it a lot.

[FreeSpaceFreak]

No problem, glad to see it solved The pilot code has been a long-standing issue in FSO, and it's led to many obscure problems like yours. As a rule of thumb, you should use a separate pilot for each mod, and avoid cloning them. I know, it's a pain to set up your controls time and again... but hopefully not for very much longer: FSO 3.7 (currently scheduled after 3.6.16) will have the pilot code overhauled, which should make it much more robust.