0 Members and 3 Guests are viewing this topic.
MattNW wrote:Only bug I keep coming up with is the CTD at the airlocks and I'm pretty sure that's caused by other ships in the scenario.Especially Spacecraft3 ships.
Voyager wrote:Quotekillingsnake wrote:I have another problem here. For some reason, my new keyboard doesn't have any seperate Ins and Del keys.They are combined with the numpad 0 and ( . ). So I can't control the camara's anymore. I'm probally the only one with thisproblem, so anyone knows how I can solve this problem?To use the insert and del keys of the numpad you need deactivate the numlock (press the numlock key so the light will gooff). Dont forget to turn it back on or you cant control the ship anymore! (if you're not using a joystick to fly)
killingsnake wrote:I have another problem here. For some reason, my new keyboard doesn't have any seperate Ins and Del keys.They are combined with the numpad 0 and ( . ). So I can't control the camara's anymore. I'm probally the only one with thisproblem, so anyone knows how I can solve this problem?
sunshine135 wrote:My thoughts are that if the incompatability cannot be overcome, we probably need to think aboutadding that to the DGIV FAQ. Some of these "nit-picks" we have been pointing out are sure to be ones that newbs will have,and this way we can politely tell them to read the manual/ sticky thread.
sunshine135 wrote:In your case Matt, you found the solution was to place the Spacecraft3 ship at the end of the scenario right? If thatconsistantly works for you, then we need to consider that as a solution unless, as Dan recently pointed out, we are allpiloting DGIV from a wheelchair wearing coke-bottle glasses.
n122vu wrote:DGIV docked to ISS, undock, EVA, grapple left or right turbopack on back. Fly the UMmu around a bit. When not near any object, press G to grapple with hand. HUD now reports TU-00 as hand-attached object. Press B to grapple with Back, HUD reports TU-00 as back-attached object. Now, return to DGIV near open turbopack door. detach turbopack from back. Switch to DGIV and attempt to grapple the turbopack. The DGIV reports "no free turbopack in range," even when the turbopack is clearly floating in the "turbopack bay" totally detached from the UMmu. n122vu
Pagir a écrit:I don't remember if it was summited before, but the temp reading of the DGIV in space (about -150C) is not the same than the uMMu (-273, almost 0 K). Well... maybe it should be corrected.
Pagir a écrit:Another thing: during the descent to the Earth, the uMMUtemp change from -273 to -50 in a fraction of a second, then go down til abour -100C...
streb2001 a écrit:Not sure if this is a bug but I can't get the ascent AP to work in the following:
DocHoliday a écrit:Well, I've just downloaded it, and I can't get the Prelude scenario to work.... Orbiter CTDs and I can't find out what toproblem is.. orbiter.log lists everything OK, OrbiterSound_Log.txt is also OK.
scinrd a écrit: I think I found a couple bugs: 1.) I have noticed that the RCS fuel gauge in the bottom panel does not show the little blue number in the middle that indicates fuel level in Kgs, but only when you use the Vespucci_D (Mabye a shared variable?).2.) I have also noticed that the BTC ver1.3 MFD causes a CTD when activated in same scenario (SEL->Burn Time Calculator).3.) Kulch's Mir 2 space station modules load fine in any DG IV scenario, but when I exit to the Launchpad and load current state.scn, I get a CTD. This is really annoying because I am trying to use it as a Jupiter orbital spaceport!!
Pagir a écrit:But I can't anymore!I think you prohibited the use of hovers when the P104SXX is in function, even if the doors are wide open.
willy88 a écrit:Is the next beta today?