0 Members and 1 Guest are viewing this topic.
; === Subdirectory locationsConfigDir = .\Config\MeshDir = .\Meshes\TextureDir = .\Textures\HightexDir = .\Textures2\ScenarioDir = .\Scenarios\
Complete description When DGIV goes into a hover landing, wheel animations do not stop even though DGIV appears to be completely stopped
sunshine135 a écrit:Rookie Mistake (maybe).
sunshine135 wrote:Rendering appears to be a problem with the higher level Cape Canaveral Texture ONLY. When I kick the autopilot into gear, sometimes the base renders and other times it doesn't.
asmi wrote:This is happening sometimes when you exit the simulation and then restart it without restarting launchpad. It is known issue, though it's kinda random so it's hard to find/fix. If you restart launchpad it should work, or you can go to the "Extra" tab in NG's launchpad, pick Debugging options->Orbiter shutdown options, click "Edit" button and set it to "Respawn Orbiter process". It is likely caused by some memory leaks during shutdown, but as I said for now I wasn't able to catch and fix it.
sunshine135 wrote:Nice work btw. This is one of the few graphics clients I have been able to run that works well on my PC. I like the mountains on Mercury and look forward to exploring more. Just FYI, on your install instructions, you might want to recommend some textures to add that work well with your package.
sunshine135 a écrit:Short description: Arrow Freighter main panel bars are transparent to the outside surroundings
DanSteph wrote:No idea what happen here, I never saw that and I don't remember this being reported.Does anyone see this also ?Dan
asmi a écrit:And as a bonus - spoiler into terrain
sunshine135 wrote:Dan and Asmi,I have also discovered that pressing the F11 key in Orbiter now has a function that brings up what I guess to be a "mesh box" or an area of defined influence for an object. This isn't a bug within itself, but it conflicts with the MKTSAT deployment which ends on all commands with F11. See the picture below:With that being said, F11 command at the end of the sequence should probably be replaced with a different key as to not cause interference, or I am not sure if this key is exclusive to the new version of Orbiter or DX11, but maybe you guys and the good Doctor could compromise
Cras wrote:back to the animation bug and autopilot ascent crashes I saw under D3D11 (about one DGIV beta build or so ago), after a fresh install of Orbiter 2010P2 beta, and the latest and greatest D3D11 client from source forge, I no longer see any of these issues. I did have some repeating CTDs at random times that I feel are no way related to the DGIV, so I am not being able to test out the DGIV as well as I would have hopped, I need to get back in touch with asmi to sort out why once again my computer just does not want to co-operate with D3D11 client.
and asmi, that pic of you in the virtual cockpit of the arrow on the moon looks fantastic. Looks so good with that terrain.
Page created in 0.125 seconds with 25 queries.