zacklaws

Its a mystery then, found evidence that I was running V 1.5.3 back in April 2016, same graphics card with DX11 installed in a posting by myself with a report on 050416 titled "Game crashes on starting a mission" and it was a problem which resolved itself eventually. As I was running on the minimum then, perhaps Win 10 is now using a bit more memory than win 7 was and has caused the problem, but not to worry, new card and memory when I get chance.

Was 1.5 Open beta running on DX 9, because if it was not, then I can assure you that it was working on my system because as we have seen, my graphics card does not support DX11 but I have had OPEN Beta 1.5 working on that card since it came out and it was up to upgrading to WIN 10 and DX 12 when it stopped working.

If that is the case then, I cannot recall when 1.5 came out, but if it was before July 29th when I switched to Win 10, then I must have been running 1.5 on DX9. Anyway, time to go fishing fro rest of week, I'll sort it out next week if I get chance.

Tried it numerous occasions along with pressing virtually every other key settings for views etc. I also knew I was not the first to have this problem but no matter how much I searched I could not find the thread till today until I was looking at DX 11 issues and then found the thread I was looking for which would have helped me. The other poster had spelt cockpit as "cokpit" so no matter how much I searched for "cockpit" problems I could not find it. At moment planning on going back to 1.2 till I can get a new graphics card or revert back to an earlier 1.5 that worked with DX 9, if there is one and it is possible to go back to such.

So it must be a coincidence that at the same time as I updated to Win 10, DCS World must have updated to DirectX 11.0 as DCS ran perfect with high frame rates etc on DirectX 10 before I installed Win 10

That is probably the problem then, Win 10 has updated me to DX 12. I shall have to see if I can go back to DX 10 when I get time.

Its not made any difference, no cockpit or any external views of the aircraft even though only 78% of the RAM is in use. Next step to find two more chips to get me to 8GB

I will give that ago of a clean install, for 1.5, I was on the open beta. I refrained from doing this but was held back by my monthly download limit, but I have just had fibre optic fitted so things are buzzing now with a bigger monthly limit.

Hi Since updating to Windows 10 at the end of July, When I got around to using DCS World a short while later, I found non of my aircraft cockpits would display, A10-C, F-86 and the Hawk. In the A10-C, I get the HUD and the two MFD's, the F-86 and hawk, nothing. I also noted that when I fly towards a built up area as I get close, the buildings dissapear, terrain features ie tree's etc remain. In Windows 7, DCS world worked perfect and flawlessly. I have lowered resolution settings in the sim to minimum etc, reverted back to an older graphics card driver that worked, tried repairs but nothing works. As I can no longer revert back to Win 7, I am now stuck. Something tells me its a memory issue and Win 10 uses more than Win 7 on which I was running on the minimum needed, 4GB RAM and 2GB graphics card and I may need a new system now. Anyone any ideas what else could be amiss? DxDiag.txt

Question from me, I also have all my kneeboard functions mapped to my joystick and after some hectic CAS I can end up with a load of marks on the map,is it possible to clear these marks when you end up with loads of unwanted one?

I have just had this problem yesterday with my Logitech Extreme 3D Pro which I use for quick games instead of setting up my Thrustmaster Warthog, HOTAS and pedals. I updated to the latest version of 1.5.3, checked the settings that nothing had changed for the joystick and nothing had, but soon as I went to play a mission with the F-86F, I went into an inverted loop and had no control at all with the stick to pull out of it and eventually crashed. After the first time, I disconnected the stick from the PC and reconnected it, opened up DCS world again, the same happened again. In total it happened three times. After the third time I opened up control panel in Windows and checked to see if my stick was working and it was working perfectly, opened up DCS world again and the problem was solved.

Since the last update to the latest version, 1.5.3 52478, I now have a problem of the game crashing occasionally. Aircraft in use F-86F. Start the mission When it loads, press "Fly" and then I get DCS world has stopped working After a few attempts it will work. report.zip

Just discovered this old thread whilst browsing through old posts etc. The "Hide the Stick" toggle does work on the F-86F on the most recent update which I have done today, 1.5.3 52478

The level of detail fails though when you get killed in such a mishap and can post on a forum asking questions as to what went wrong. I think that after one unsurvivable mishap, your DCS World should become locked along with access to forums.

Nothing complicated about it at all, its a very simple process which takes seconds, plus I also have the real manual as well.