Jump to content

F-15C model loading bug,


Recommended Posts

DCS 1.2.8.27203

 

Loaded up DCS F15-C and the cockpit model data didn't all load into the video card. See attached screen shots.

 

This has happened once after about ten flights. The computer is new and the operating system is up to date and was installed a few weeks ago. There is very little else installed on the system.

 

Hardware is GTX 780 Ti, driver version 335.23

Core-i5 4670K

16Mb RAM

Windows 7 Home Premium

Screen_140503_010505.thumb.jpg.f2cc3b89e4445ac3e4d16f3577cbec51.jpg

Screen_140503_010507.thumb.jpg.ef08f1253407c2ead6da61779e74fa3a.jpg

Screen_140503_010509.thumb.jpg.cda31aac83994084607a8a6e7003b203.jpg

Link to comment
Share on other sites

your processor has an Intel HD 4600 graphics chipset embedded in it. If windows decides to use this to render DCS, you will get exactly that sort of problem.

 

To manually set which GPU to use:

 

right click desktop -> nVidia control panel

3D settings -> Manage 3D settings

Preferred graphics processor -> select your GTX 780

Link to comment
Share on other sites

Hey guys, thanks for the posts. If the bug is linked to non-activation then there's likely a bug in the activation system because:

 

- the plane (specifically FC3) is activated;

- I've flown numerous times before this;

- I've flown subsequently;

- This issue has happened only once thus far.

 

Hope that's useful

Link to comment
Share on other sites

Have you also updated the fc3 module so that DCS world and the module are exactly the same ie 1.2.8.XXX.XXX? I've had that issue before when they were out if sync

MSI M5 z270 | Intel i5 7600k (OC) 4.8GHz | MSI GTX1080ti Gaming X 11Gb | 500gb Samsung 970 Evo NVME M.2 (DCS World) | 500gb Samsung 850 Evo SSD (OS and Apps) | 32Gb 2400MHz DDR4 - Crucial Ballistix | Be Quiet Silent Loop 240mm | NZXT H440 case |

 

Thrustmaster Warthog - 47608 with Virpil Mongoose joystick base | MFG Crosswinds - 1241 | Westland Lynx collective with Bodnar X board | Pilot's seat from ZH832 Merlin | JetSeat | Oculus Rift S | Windows 10 | VA |

Link to comment
Share on other sites

Same thing happened to me a few days ago after the release 1.2.8. 1.2.7 and the 1.2.8 beta were just fine, the release version had a hiccup. Went to the Module Manger, had it acknowledge the SN, and all was well on the next startup.

Link to comment
Share on other sites

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...