![]() ![]() bat, selected "Dawn", then enabled "AI Traffic." This resulted in the following (excerpted from the very large log) and a freezing of the cursor. bat to include setting the log level to "bulk". However, I really like the new startup screens - nice screen captures! Including the auto-coordination option selection is also a big plus.īeing a relative noob, I read about log levels and edited the minimal startup. The new version does not fix the problem I've reported. Uninstalled 2017.1.3 and installed the 2017.2.0 nightly on. Should this be reported as a possible bug? Are there other things I should try first? Buy more memory? pb321 Posts: 411 Joined: Sun 5:08 pm Version: 2020.4.0 OS: Windows 10 Pro I noted that someone reported a similar problem under Linux ( viewtopic.php?f=17&t=31939) and am now wondering if my issue is related. However, I have not been able to get any AI to work under version 2017.1.3. It was also working with the airport for which I've been building and testing traffic. However, it may also have been when I tried using AI, although I had AI enabled and I know it worked at KATL, KORD, KMSP and some other airports. It may have been when I went to version 2017.1.1 that the crashes started. Clicking in the FG window a second time causes the dialog box to appear with the choice of waiting or closing the application. Whenever "AI Enabled" is selected the "FightGear (Not Responding" message appears in the white bar at the top. Things work fine with any airport and graphics options I've tried, but NOT with "AI Enabled". I've tried booting with the "minimal install" for Windows described here. I thought going to 2017.1.3 might help and I was interested in getting real weather to work again, so I uninstalled 2017.1.2 and installed 2017.1.3. FG was working yesterday with AI enabled under version 2017.1.2 as long as I waited until things settled down before using the mouse but then, when re-booted, the "not responding" re-appeared and it did not matter how long I waited for things to settle down, the message "not responding" returned (crash). ![]() This time I just wait a minute or two without doing anything (even the cursor is not in the FG window), the screen freezes, then "Not Responding" pops up. Any ideas of what could be wrong? pb321 Posts: 411 Joined: Sun 5:08 pm Version: 2020.4.0 OS: Windows 10 ProĢ017.1.1.3, Windows 10, 4 GB RAM, GTX 750 TI w latest driver 381.65 No other programs on the computer result in this behavior. I also tried Microsoft diagnostics and did the sfc scannow check - no problems. I've checked for viruses and malware with a couple programs and they found nothing. I've never seen anything like this over a long career working with Windows computers. But sometimes even starting at a different airport results in the same behavior. I can often load FG using a different airport and things will work until I make more changes. I thought maybe it has something to do with putting scenery or groundnet files in Terrasync, but I'm not sure. I don't know what is causing this and am running out of ideas. I then updated two flight files and the groundnet to fix a couple traffic problems. Magically, it worked fine and I was able to see some of the AI traffic I've been working on in the last few days. After the computer was off for the night, I tried FG again. I then replaced the flight files, one at a time, then the groundnet, but the problem recurred. ![]() ![]() One time I had narrowed it down to the scenery file generated with the Airport Web Generator, but it later turned out that wasn't it, as a couple startups later the problem recurred. At first I thought it was a corrupt file, so I replaced files, one by one. I use the task manager to close the program and try again. It seems I could wait forever for something to happen, but it never does. Windows then reports "Not Responding" with the blue swirling circle (of death) as the new cursor within the window. Placement of AI flight schedules, and local scenery files within the FG directory structure seems to cause my Windows 10 computer to load and, within seconds, freeze and lose the cursor within the FG window. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |