S
sandbagger
Guest
Hi all,
I thought I'd relate this - it may be something unique to my PC set up - but then again??
Saturday evening I installed an update from Microsoft updates for .Net 3.5. It was on my workstation XP (SP 3) machine and apparently required to run other software I had installed (not OBD). The update went OK but on Sunday I found that BHaH would not go past the mission initialisation screen - it just hung there. Thinking it was a GPU glitch, I reduced the GPU to 800x600 resolution and all detail sliders to 1. Eventually it did work but I got only 4 FPS and some aircraft had no skin shown (white only). This all smacked of a GPU problem.
However, I decided to uninstall the .Net 3.5 update and after playing around with the GPU settings, got BHaH operating again as normal (45-55 FPS and all skins showing).
As I said at the start - this may have been just coincidence and on my PC only - but then again??
I thought I'd relate this - it may be something unique to my PC set up - but then again??
Saturday evening I installed an update from Microsoft updates for .Net 3.5. It was on my workstation XP (SP 3) machine and apparently required to run other software I had installed (not OBD). The update went OK but on Sunday I found that BHaH would not go past the mission initialisation screen - it just hung there. Thinking it was a GPU glitch, I reduced the GPU to 800x600 resolution and all detail sliders to 1. Eventually it did work but I got only 4 FPS and some aircraft had no skin shown (white only). This all smacked of a GPU problem.
However, I decided to uninstall the .Net 3.5 update and after playing around with the GPU settings, got BHaH operating again as normal (45-55 FPS and all skins showing).
As I said at the start - this may have been just coincidence and on my PC only - but then again??
No problems here with 3.5. I have had 3.5 on my machine for quite a while now, no issues that I know of.