In general, it would make sense for you to create a flight plan that reliably reproduces the issue, and then change visibility/LOD to exclude scenery/terrain from being part of this, and then switch to another aircraft (i.e. Having a reproducible test case (settings, flight plan, pre-recordeded flight, fgtape) should help tremendously. If you think you have found a bug, you are encouraged to report it at the tracker: Jabberwocky Retired Posts: 1316 Joined: Sat 8:36 pm Callsign: JWOCKY Version: 3.0.0 OS: Ubuntu 14.04 so I really lack a little bit the time for this kind of crash programming. but right now, I am quite unhappy with 3.4 and in three weeks, there is the USA Tour again, I want three bombers ready for that. Maybe it's me, maybe it's just not my day. well, and TerraSync fails like usual and gave me already know only the infamous white clouds instead of terrain in two arrivals. in compensation, the number of segment faults seems to be a lot higher (like 3 in the first hour). the fps seem to be with the same planes and airports about 10% lower than in 3.2 but that needs more testing So you can't crash in them from the rear, but t-boning them because they are invisible to you is possible. I find it also a bit sidturbing that other planes are virtuallly invisible if ther angle of view is not right. I made it in a 747 from Phoenis till about the middle of Utah till my 8 Gb were full. as soon as I fly by Route Manager, it starts to suck memory as if there is no tomorrow. I got force fed with FG 3.4, it came, together with a bunch of other updates while I was drinkinf coffee.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |