Recent content by mati140

It appears that the autopilot reads airspeed instead of ground speed, because when set to maintain 0 horizontal speed it starts moving trying to zero-out TAS. Orbiter 2016 introduced wind, which means it should read ground speed here instead of airspeed.

Unfortunately GS 2.4 doesn't seem to work in Orbiter 2016, it causes a crash on loading.

I've got a little update on this one: The issue with Item 27 is not limited to ops switch, if you load burn data with item 22, do item 27 and than change the data, reload them and do item 27 again, the computer won't maneuver into the new orientation - it's as if item 27 could only be executed...

Urwumpe, why do you have an Old Germanic healing spell (one of the Merseburg Incantations to be more precise) written in elder futhark in your signature? Is there some backstory about it?

Sorry for necro, but does this MFD work with D3D9 client? Because for me it doesn't even show up on the list after pressing SELECT though I've activated it in modules tab. Am I doing something wrong or it doesn't work with graphics client?

You watched wrong episode. Watch S2E3 - that one still didn't convince me to the show, but it did convince me that Season 2 did hit it's demographic. And it wasn't little girls it was aimed on.

Sorry for necro but is it gonna be compatible with graphic clients? I'm asking bc all those explosions would blow up my computer if I didn't use D3D9 Client - it hardly works at all at stock D3D7, I'm using Windows 7 and it doesn't have actual D3D7 support.

I have exactly the same problem, also with nVidia 200 series card (GT 240 in my case - my thread is still floating arround). The last drivers wich worked with Orbiter for me were 280 or 285 IIRC. The problem is that installing old drivers gives errors in newer programs. Let me give an example -...

There is an addon on OrbitHangar which allows to control mass of the ship, which is pretty much what zero element core makes - I don't know if it allows setting negative mass, which is needed for interstellar travel - you can still use WarpMFD then though.

Kamikaze Sake - lol

Yes, I did, read first post. It's still absolutely stock. Now, THIS is strange: I checked again adn it seems that this BSOD has nothing to do with on the ground or in orbit - I succesfully started scenario with DG on pad in Habana Spaceport, and "Lunch into sunrise" (LC on KSC) Atlantis...

I checked, hardware is fine. According to complaints all over the internet nVidia must have messed something up. The most strange thing is that when I start mission on orbit, and then switch to a vessel on the ground, the game runs fine - the problem happens only when I START on the ground...

I found some information (on BF3 Battlelog forums BTW) that 296.01 drivers cause such BSODs (the exactly same error) and going back to 295.73 does help, so I decided to start over from scratch. I removed all NVIDIA drivers, then i removed them again (bc it showed that my previous 290.xx drivers...

Actually I have no problems with as high-end game as Battlefield 3 - there's no way it can be a hardware problem.

U asked for it: *** STOP: 0x00000116 (0xC4547008, 0xD556AACE, 0x00000000, 0x00000002) *** nvlddmkm.sys - Address D556AACE base at D5420000, DateStamp 4f4e6797 I may upload memory dump if it does help. Gonna try reinstalling drivers later