![]() What am I doing wrong? Any suggestions? Is there a trick to fix the tremdendous loading time?Ĭheers Jaques jaques.flightgear Posts: 90 Joined: Fri 8:38 pm Location: Germany, between EDTY and EDRY Callsign: D-EVIL Version: 2020.4. While the base package only comes with scenery for the San Francisco Bay. GPS:defineWaypoint: creating waypoint:BLANESESWPTTWNĪ million waypoints appeared and after 1/2 hour the sim started. GPS:defineWaypoint: creating waypoint:BILBAOESWPTTWN GPS:defineWaypoint: creating waypoint:BENIDORMESWPTTWN GPS:defineWaypoint: non-unique waypoint identifier, ho-hum I changed DEBUG-Level to "info" and got output in the console window like ![]() they should start small and grow larger on approach instead of popping in and popping out when departing the scene.Not quite sure wether this is the right place to post my challenge concerning fgrun.ĭownloaded WIN 32 nightly-build fgfs_win32_vs2010_nightly_2.9.0.exe #813. all i'm wanting to do is have the view be more realistic than buildings popping into view when others closer and further away are already visible. I've found one-world-trade-center.xml and its files (w080n40/w075n40) but i don't see anything related to LOD in it so apparently this one is not carrying its own LOD settings? i don't know. in other words it should be visible since it is within my Bare LOD setting (of 370000 meters) shouldn't it? then when it gets within my Rough setting of 20000 meters, it should get some details and when it is 3000 meters away, it should have its highest detail. since that's outside of my Rough LOD setting of 20000 meters, i can see a slight delay in seeing it clearly as i cover that 7km at which point it should appear with more detail than it had been drawn with. the WTC is 27.3 km from my starting point as the crow flies (aka straight line). my Detailed is set to 3000 meters (3km) and my Rough is set to 20000 meters (20km). If they are supposed to be visible between my Detailed and Rough LOD settings, they are not. if i 'b'ack up, they pop out at the same distance where they popped in. they should all be loaded and visible already, IMHO. as i get closer to those buildings that just popped in, more start popping in. as i start to move forward, i see some tall buildings pop into view. that's almost directly at the new WTC building. Go back to your starting point over the runway at 1000 feet (i use the 'b' key to back up) and turn to true heading 295. i should be able to see it like i see the road on the water and watch the bridge get larger as i approach. i can see the road crossing over the water (drawn on the surface of the water) but i have to get close before the actual bridge pops into view. but after loading the scenery, there seems to be some kind of graphics issue- the screen flickers every 2-3 seconds. ![]() now fly toward the Verrazano-Narrows Bridge. load up at KJFK in the UFO on runway 31L. I don't know that what i see is the same thing, then. It takes a while to load (dependent on various factors, possibly minutes). When you request 50 km visibility of dense mesh terrain covered with objects (via a reposition for instance), that's a lot of data. Thorsten wrote in Wed 6:44 am:I think the overall problem is fairly clear: It would only be unloaded by OSG if OSG was struggling for resources and had determined that it was out of view previously. time would go goofy when scenery was being loaded. Otherwise I'd expect the building to already be loaded by OSG. Various restructures in the scenery loading code in preparation for more flexible runway lighting support. ![]() ![]() When you change to walker view, do you see the splashscreen for a moment? That would suggest the scenery is getting re-initialized, which shouldn't be nessecary. The example use case you give is also interesting. Every time mavproxy console loads, I got a message link 1 down. Are there particular objects that caused a very long freeze? If so, it would be worth checking whether they are too detailed or have too large textures. terrain is visible and the ground elevation reads correctly within FlightGear. OSG should be loading those static objects in the background so the "only" freeze would be while the mesh and textures are loaded into your graphics card and some final transformations are done. Pommesschranke - what you describe as your experience with the 10 second freeze is quite odd. There's a description of the changed here that might be useful for this discussion: I made some changes prior to the Barcelona release to rationalize the LOD ranges. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |