Newcomer. Some feedback and a problem.

[PabloSanchezGrobet]

I tried Walterar's suggestion, to see if it made a difference and it crashed both ways. But there was a difference: when I selected Altair A as hyperspace jump target, it crashed almost immediately after the jump; then I selected Altair f as target and then tried to navigate to Mruk town and it let me travel some distance before crashing, I was about 2 AU from target when it crashed, I don't know if that means anything. 

[PabloSanchezGrobet]

I just found out something. It only crashes when I'm at normal view (F1). I jumped to Atair A, after the jump, I selected autopilot to vicinity of Mruk town, about 120 AU distance, and then quickly went to maps view (F2) and kept it the whole journey and it didn't crash. Then I had to go back to internal view again to tell the autopilot to dock with Mruk Town, again quickly went back to orbital view and everything was allright. But after the docking, it crashed immediately after I pressed F1 to go to normal view again.

[fluffyfreak]

Ah now that is more interesting, ok then my advice is to start the game, go to the Options, and reduce the planet detail settings to lowest then give it another go.Maybe create a save game somewhere close to where the game crashes so that it's quicker for you to repeat in the future? Also how much RAM do you have and how much is the GPU allowed to use?

[impaktor]

On a side note, if you're 120 AU out, then you've targeted the wrong star. Which leads to quite tedious game play.

[PabloSanchezGrobet]

I tried that, nothing worked. I even reduced all other graphics options to the lowest and deactivated other options like speed lines, compact scanner, star field density, tried different resolutions, and it still crashed. I have 4 GB RAM, and NVIDIA GeForce 630M graphics card.

[PabloSanchezGrobet]

I have a save file from when I got to Mruk town in orbital view, orbiting the planet. I loaded that game without problem. When the game opens I'm in internal view looking towards space. I could even travel to Kuo Outpost, the space station near the planet. But then it crashed when, near to the station, the autopilot turned around. I think the problem is with the planet. Even if I stay over the planet but looking outwards, it doesn't crash, and I can move the camera a little bit, but it crashes if I try to put the planet in the screen.In another try I jumped from Earth to Altair f and then started traveling to Hsiung Rock. Normally it would crash about 1.5 AU from target. But I changed course when it was about 6 AU away and headed to Artair f f, which was nearby, in autopilot. It aproached the planet until, again, it crashed when the autopilot started making adjustments, before I could ever see the planet on the screen.

[walterar]

Something strange is happening there. :(It seems that the video card that is active is Intel HD Graphics 4000, instead of the Nvidia 630.

[PabloSanchezGrobet]

Hmm, it seems that it is set up to use the Intel Graphics by default instead of the Nvidia. But if I try to set up Nvidia for this specific aplication, I can't even open the program, it crashes immediately.

[walterar]

@PabloSanchezGrobet There is a 99% chance that it is a problem of Nvidia-Win10 I googled a bit and see that it is a common problem. Maybe you should download the updated Nvidia drivers and install them manually. @fluffyfreak has a laptop similar to yours; perhaps know how to solve this problem. :prankster:

[fluffyfreak]

It's fine on my laptop with the built-in Intel 4000 and the nVidia 650m on my laptop. You can either install the "Geforce Experience" (http://www.geforce.co.uk/geforce-experience[/url] software and have it download the correct drivers for you or get them directly from nVidia's site ([url]http://www.nvidia.co.uk/Download/Find.aspx?lang=en-uk).[/url] Pioneer doesn't need a profile creating for it as we export the `NvOptimusEnablement=1[/url] symbol that the nVidia drivers use to determine availability so it should just work if you have the newest drivers. It might be best to download the drivers yourself, and do a clean installation (optional during install) to make sure that there's no junk left over from earlier installations.

[PabloSanchezGrobet]

It worked!! Finaly!! Thank you very much to all of you who helped. Yes, I updated the driver from version 563.something to 573. I ended up being lazy and did it with the help of the GeForce Experience software but it works fine. The only thing was that at first the video was jumpy, but I deactivated the multisampling and it solved the problem. I still think its weird that it consistently crashed on some apparently random systems, right?Anyway, thanks again. I know it may have been rather obvious, but I am not really a frequent gamer, and it did not occur to me that an out-of-date driver could cause such problems.Now to enjoy the game!