This strengthens my belief that the bug is somewhere in a line of code related to aircraft explosion or module damage and fire in certain views. Crashing a plane into the water allowed the game to continue running with no issues, every time. All of the above still applies, as long as the plane was destroyed in the air, however, if a crash was not already triggered, and the plane fell into the water, the game continued to run smoothly for everyone without crashing. We tested this further by shooting down planes over water, or deliberately crashing into water, which doesn't trigger an explosion or fire on the plane. So there are some differences there, which leads me to believe that the crash is being triggered by some type of module damage on the plane, or perhaps from the fire/explosion animation itself. For example, if you made the kill in third person mode, or if you shot off a wing/tail or knocked the pilot unconscious without causing serious module damage or explosion.
When a damaged plane hits the ground, it usually triggered a crash for each of us, even if it didn't before. When you shoot down a plane in zoom mode with the gunner's view, it always triggered a crash for whoever made the kill.
Especially when the aircraft is far away, or if you immediately remove your radar lock from the plane after the kill. When you successfully destroy an aircraft in third person view while in an SPAA, sometimes the game continues running without issue. Shooting down aircraft didn't always trigger a crash for everyone. We took turns in aircraft and on the ground in SPAA, and learned a couple of new things. I did some custom battle testing with other friends in game who play on Mac. We win (I suspect we played an entire team using Mac's)ĭev's are trying to find why the crashes. Restart Again - mash battle in the closest vehicle - my AH-1 - and it loads Restart Again - but now my Sheridan is dead I am now on top of a destroyed building - but instead of Freeze error - I get Reflection: invalid object 0x0x7f8f52203000 This is because if you were to do this, your discrete GPU would actually stay powered on, even though you've switched to the. It last around 1 Min - I am beside a building near the B cap on that map As stated on the developers webpage: 'gfxCardStatus v2.3 and above actively prevents you from switching to Integrated Only mode when any apps are in the Dependencies list ( or if you have an external display plugged in ). Not sure what caused that Freeze - nothing was going on I near me - a plane was shot down across the map - but not in my view There is a utility called gfxCardStatus which can tell which graphics card is being used by the system atm.Kill a BMP with my Sheridan - and start to Cap B plugging in an external monitor forces the usage of the discrete card). It works much better using the integrated card as long as the system is allowed to use it (eg.
#GFXCARDSTATUS FORUM UPDATE#
We also released a small update to the testing branch on steam which makes the game prefer the integrated graphics (intel) card to the discrete one (radeon).
#GFXCARDSTATUS FORUM DRIVER#
Sometimes it is not enough just to change the settings but you need to exit the game and start it again as it seems the driver gets in a bad state. If that does not help try turning every setting to low and turning off all other effects. To help with the performance (making map movements more fluid) try turning off vsync (under general settings) and set frame rate limit to 30, this works without having to sacrifice to much quality (eg.
The artifacts are cause by these 2 (effects) settings under video: As Tomislav pointed out, there are still some issues with Radeon Cards and we are still debugging the issue.
0 kommentar(er)
