(closed) DeltaGliderIV+addons beta 20120320

[asmi]

DGIV BUG

Short description:

Altitude callouts are heard after vessel is crashed


Severity

minor


Complete description

Altitude callouts are played after vessel is crashed if impact impulse is large enough to propel wreck up in the air


Reproduce bug

Take off the ground on Earth, climb to 2-3 km, pick up good speed (1M+) and then direct vessel to the ground with high AoA (-50 or more). Impact enegry should be enough to propel crashed piece up into the air to the altitude of more than 100 feet. As wreck starts to fall down, you'll hear altitude callouts ("100", "50", "40" and so forth)


Miscallenous

Those callouts are usually propounced by co-pilot (or second pilot), but impact energy is likely to vaporize whoever was aboard, so...



Post Edited ( 03-23-12 01:52 )

[asmi]

DGIV BUG

Short description:

"80 knots" callout is heard at 80 m/s


Severity

minor


Complete description

80 m/s is actually ~155.5 knots, which is roughly twice the indicated value. 80 knots is ~41.2 m/s.


Reproduce bug

Start jet-like take off on Earth. At 80 m/s you'll hear "80 knots" which is wrong.

Miscallenous

Just FYI, usual take-off speed for commercial jets is around 140-160 knots or 72-82 m/s.



Post Edited ( 03-23-12 02:06 )

[Cras]

asmi wrote:
Looks cool - let's not fix that
On a serious note - can you please create a brand new installation of Orbiter P2 + D3D11Client + DGIV and give it a try.

Yup, will do.  I think something may be amiss here in this installation.  Makes sense to clean it out and start over and see what happens.

[DanSteph]

SolarLiner a écrit:
Complete description
Orbiter CTD when DGIV crashes
Reproduce bug
Load a DGIV scenario, and crashes it on the ground, or on a reentry.
Miscallenous
I'm on "40 debirs" crash mode, may be it is the problem ... I've not tested with other settings

So I mark this one as solved. (DX11)

Dan



Message modifié ( 23-03-2012 08:00 )

[DanSteph]

asmi a écrit:
DGIV BUG

Short description:
Altitude callouts are heard after vessel is crashed

Funny, I obviously didn't set the "no GPWS" in the main debris's OrbiterSound parameters given it's rare someone crash
so hard (congrat asmi )

I'll keep "Antenna" & "parts goes wild" open until they are fixed in respective clients.

For "80" I'll probably remove the "knots".

Thanks to all,

Dan



Message modifié ( 23-03-2012 08:41 )

[asmi]

DanSteph wrote:

Funny, I obviously didn't set the "no GPWS" in the main debris's OrbiterSound parameters given it's rare someone crash
so hard (congrat asmi )

Well, I figured - if I need to crash this baby, this would better be a good one - so I directed vessel towards ground while keeping engines at full thrust It is funny, it's it?



Post Edited ( 03-23-12 11:27 )

[Ripley]

ORBITERSOUND BUG

Short description:
 
ORBITERSOUND not recognized nor detected.
Module activated in Launchpad.


Severity

Serious


Complete description
This happens on my 2nd pc (at work).
Specs are: XP Pro SP3, Dual Core E5700, 4Gb RAM, integrated Intel graphics chipset, integrated Realtek audio

I made a new fresh Orbiter2010P1 install.

I've put in that folder all Dansteph's goodies (OrbiterSound 3.5, DGIV-2, UCGO, UMMU) from the good old download page, plus the D3D9 RC44 client, plus Dansteph's latest beta package.

I keep on getting the error message at start: "DGIV NEEDS AT LEAST ORBITERSOUND 3.5! YOUR VERSION IS OUTDATED OR NOT INSTALLED".

If I reinstall the original OrbiterSound 3.5 it says that the detected OrbiterSound is older!
Anyway, after installation, sound works (both Inline and D3D9).

If I put again Dansteph's latest beta package, this message comes back: "DGIV NEEDS AT LEAST ORBITERSOUND 3.5! YOUR VERSION IS OUTDATED OR NOT INSTALLED".


File OrbiterSound_Log.txt says:

OrbiterSound 3.5 ver. May 13 2007  Log Started
***********************************************

--------------------------------------
ERR01= Vessel->ConnectToOrbiterSoundDLL3: Unable to connect to OrbiterSound 3.5 - not installed or activated


File Orbiter.log says:
Error loading module Modules\Plugin\OrbiterSound.dll (code 14001)


Reproduce bug

Just putting the new Beta pack into my Orbiter folder gives me this bug


Miscallenous

What is strange is that on my "home" pc, the new beta OrbiterSound worked well...I'll try to replicate this one when I'm home later today.



Post Edited ( 03-23-12 17:37 )

[Ripley]

ORBITER.LOG ANOMALIES

Short description:

File Orbiter.log has a few "error" lines.


Severity

Seems minor to me.
But I don't know what this could mean "inside".


Complete description

Test is made by launching the "Landed KCS departure to ISS.scn" scenario, waiting to sit in the cockpit, and pressing F4 to exit simulation, then open Orbiter.log.


When I launch ORBITER.EXE:

Code: [Select]

[i][b]UNTIL HERE IT HAS CORRECTLY LOADED ALL THE MODULES[/b][/i]
Finished initialising world
Module DeltaGliderIV.dll ..... [Build 120318, API 100830]
Finished initialising status
Finished initialising camera
Finished initialising panels
Finished setting up render state
ERROR: DDraw object is still referenced: 6
---------------------------------------------------------------
>>> ERROR: Destroy framework objects failed
>>> [OrbiterGraphics::Exit3DEnvironment | .\OGraphics.cpp | 1034]
---------------------------------------------------------------
**** Closing simulation session
When I launch ORBITER_NG.EXE:

Code: [Select]

[i][b]UNTIL HERE IT HAS CORRECTLY LOADED ALL THE MODULES[/b][/i]
Finished initialising world
Module DeltaGliderIV.dll ..... [Build 120318, API 100830]
Finished initialising status
Finished initialising camera
Finished initialising panels
Finished setting up render state
D3D9Client: [Scene Initialized]
D3D9Client: [Session Closed. Scene deleted.]
UnDeleted Surface(s) Detected
Surface 0x1B18468 (DGIV\skin\Mining\DGIII_4.dds) (1024,1024) Type=2, Creation=1
Surface 0x1B18540 (DGIV\skin\Mining\DGIII_3.dds) (1024,1024) Type=2, Creation=1
Surface 0x1B18618 (DGIV\skin\Mining\DGIII_5.dds) (1024,1024) Type=2, Creation=1
**** Closing simulation session

Reproduce bug

Every time I make this test it ends this way.


Miscallenous

I'll try to replicate these situations (from this one and from the previous post) on my "home" pc in a few hours.



Post Edited ( 03-23-12 17:42 )

[Ripley]

DGIV MAIN PANEL BUG

Short description:

Still about white pixels, sorry, not THAT important, but I just noticed this.


Severity

Minor


Complete description

I am on my 2nd pc (at work) now, the one that had those white pixels on the overhead panel (Dansteph said it probably was an antialiasing issue). I even updated the graphics drivers, but the "white pixels" problem is not solved yet.

There is this white line also on the top edge of the main panel, but it is kind of "broken" where the mini panel is (that is, the drawing of the panel is ok in that portion of screen, both with mini panel ON or OFF).





- If I toggle the mini panel off, there are no white pixels there.
- If I switch to other panels, and then back to the main panel to force a redraw, still no white pixels...


The "Advanced" properties of the Launchpad Video tab give me this poor view: Antialiasing is "none", nothing else can be selected.




Reproduce bug

Buy a very cheapo graphics card... ;-)


Miscallenous



Post Edited ( 03-23-12 17:54 )

[DanSteph]

Ripley a écrit:
File OrbiterSound_Log.txt says:

OrbiterSound 3.5 ver. May 13 2007  Log Started
***********************************************

What's your Orbiter's path and is it a user acount with limited right ?

(PS: filling bugs report that I can tag would be more clear : http://www.dansteph.com/publie/beta_form.txt )

Dan



Message modifié ( 23-03-2012 17:20 )

[DanSteph]

Ripley a écrit:
Still about white pixels, sorry, not THAT important, but I just noticed this:

The stock image have no white pixel here, must be an AA problem. (client)

Dan

[Ripley]

DanSteph wrote:

What's your Orbiter's path and is it a user acount with limited right ?

(PS: filling bugs report that I can tag would be more clear : http://www.dansteph.com/publie/beta_form.txt )

Dan

Path is "C:\Downloads\orbiter100830 - BETA DG D3D9RC"
NO restricted account, I'm the administrator.

...Could it be that "minus" sign?

Sorry for the format of my "bugs", I'll edit them.

EDIT:
NO! It was not!! I renamed the folder without blanks or "-", but I still have the same problem...



Post Edited ( 03-23-12 17:29 )

[DanSteph]

Ripley a écrit:
NO! It was not!! I renamed the folder without blanks or "-", but I still have the same problem...

Okay, I'll have a look.

Dan

[DanSteph]

Ripley a écrit:
File Orbiter.log says:
Error loading module Modules\Plugin\OrbiterSound.dll (code 14001)

Mhhhh... thinking about it I smell something about library, VC+ redistributable (most probably).
I compiled with a newest DirectXSound library and the dll need MSVCR80 despit my static linking. (!??)

Don't install VC redistributable so we have a test system. I'll try to solve that.

EDIT: Solved imho, see new dll (pm)

Dan



Message modifié ( 23-03-2012 20:19 )

[Ripley]

DanSteph wrote:
...Don't install VC redistributable so we have a test system. I'll try to solve that.

You mean we have to uninstall it, if we have installed it previously??

[DanSteph]

Ripley a écrit:
You mean we have to uninstall it, if we have installed it previously??

No, just replace the old dll with the new one in the zip. (OrbiterSound_20120323_nocrt.zip see your PM for link)



Message modifié ( 23-03-2012 20:21 )

[Ripley]

Ok, so I'm home now with my more powerful pc.

The "ORBITER.LOG ANOMALIES" bug report I wrote earlier is still present, even on this pc, exactly the same as described in previous post.


The new "OrbiterSound_20120323_nocrt" works well here, Inline and D3D9.

Here's the OrbiterSound_Log.txt from Inline...

Code: [Select]

OrbiterSound 3.5.1 ver. Mar 23 2012  Log Started
***********************************************

Vessel GL-01 requested an ID, returned= 0 OK
attempting focus change...
Focus not ready bypassing focus change - Ok
Attempting RenderViewport initialisation...
Attempting GetStartValue initialisation...
Passed GetStartValue - Ok
Initialising directsound...
directsound initialised - OK
Passed RenderViewport - Ok
Attempting Mp3 initialisation...
MP3 found in directory =  5
Mp3 initialised - Ok
Focus changed attempting to load vessel wave
Focus changed load vessel wave - OK
Attempting to close viewport...
Attempting to kill DirectSound...
DirectSound killed - OK
Passed CloseRenderViewport - Ok
Exited to Orbiter Launchpad - OK

...And here's the OrbiterSound_Log.txt from D3D9:

Code: [Select]

OrbiterSound 3.5.1 ver. Mar 23 2012  Log Started
***********************************************

Vessel GL-01 requested an ID, returned= 0 OK
attempting focus change...
Focus not ready bypassing focus change - Ok
Attempting RenderViewport initialisation...
Attempting GetStartValue initialisation...
Passed GetStartValue - Ok
Initialising directsound...
directsound initialised - OK
Passed RenderViewport - Ok
Attempting Mp3 initialisation...
MP3 found in directory =  5
Mp3 initialised - Ok
Focus changed attempting to load vessel wave
Focus changed load vessel wave - OK
Attempting to close viewport...
Attempting to kill DirectSound...
DirectSound killed - OK
Passed CloseRenderViewport - Ok
Exited to Orbiter Launchpad - OK

...Problem is that I won't be able to test that "bug" (ORBITERSOUND BUG - ORBITERSOUND not recognized nor detected) until monday morning, when I'll be back to my work pc.
That's why we have an office, isn't it? To betatest Orbiter!



Post Edited ( 03-26-12 11:45 )

[DanSteph]

Ripley a écrit:
That's why we have an office, isn't it? To betatest Orbiter!

Sure

I'm 99.9% confident that this was the problem, Redist is one major cause of malfunction on one computer while working on all other.
Work computer are typically not updated with redistributable.

I have another new tester which had this problem, I wait his feedback.

EDIT: feedback received, it's okay now.

Dan



Message modifié ( 24-03-2012 00:46 )

[ProAuroraX]

after checking that everything works with D3D9, i ran the DGIV in the default client and got this animation bug, the same one as Cras http://dl.dropbox.com/u/57029031/DGIVwierdbug.png  .

[jarmonik]

Ripley wrote:
Still about white pixels, sorry, not THAT important, but I just noticed this.

What graphics card you have ?

Are the white pixels visible in a fullscreen mode ?

Is the desktop color resolution 16-bit by any chance ?

[luki1997a]

ProAuroraX wrote:
after checking that everything works with D3D9, i ran the DGIV in the default client and got this animation bug, the same one as Cras http://dl.dropbox.com/u/57029031/DGIVwierdbug.png  .

I've got similiar bug while rolling on phobos in previous release.

[Ripley]

jarmonik wrote:
What graphics card you have ?

Are the white pixels visible in a fullscreen mode ?

Is the desktop color resolution 16-bit by any chance ?

On that pc there's a cheap integrated Intel Q43 Express graphics chipset. Drivers updated.
I was surely running in a window, not full screen.

To test this in full screen (and for the 16-bit question as well), I can answer not before next Monday.



Post Edited ( 03-25-12 11:39 )

[luki1997a]

Hey, try walking UMMU on the moon from scenario "Fly me around the moon". UMMU sometimes rotates instead of walking:trucdeouf:

EDIT: when i faced the ground I've been ejected with speed about 200 km/s



Post Edited ( 03-24-12 21:41 )

[Ripley]

Good morning from my office, gents!
Here's the results from "work" pc (the one that had problems with OrbiterSound not detected).

The new OrbiterSound_20120323_nocrt WORKS!


Here's the new OrbiterSound_Log.txt from D3D9:

Code: [Select]

OrbiterSound 3.5.1 ver. Mar 23 2012  Log Started
***********************************************

Vessel GL-01 requested an ID, returned= 0 OK
attempting focus change...
Focus not ready bypassing focus change - Ok
Attempting RenderViewport initialisation...
Attempting GetStartValue initialisation...
Passed GetStartValue - Ok
Initialising directsound...
directsound initialised - OK
Passed RenderViewport - Ok
Attempting Mp3 initialisation...
MP3 found in playlist =  1
Mp3 initialised - Ok
Focus changed attempting to load vessel wave
Focus changed load vessel wave - OK
Attempting to close viewport...
Attempting to kill DirectSound...
DirectSound killed - OK
Passed CloseRenderViewport - Ok
Exited to Orbiter Launchpad - OK

Passed ExitModule - Ok

...And the new OrbiterSound_Log.txt from INLINE:

Code: [Select]

OrbiterSound 3.5.1 ver. Mar 23 2012  Log Started
***********************************************

Vessel GL-01 requested an ID, returned= 0 OK
attempting focus change...
Focus not ready bypassing focus change - Ok
Attempting RenderViewport initialisation...
Attempting GetStartValue initialisation...
Passed GetStartValue - Ok
Initialising directsound...
directsound initialised - OK
Passed RenderViewport - Ok
Attempting Mp3 initialisation...
MP3 found in playlist =  1
Mp3 initialised - Ok
Focus changed attempting to load vessel wave
Focus changed load vessel wave - OK
Attempting to close viewport...
Attempting to kill DirectSound...
DirectSound killed - OK
Passed CloseRenderViewport - Ok
Exited to Orbiter Launchpad - OK

Passed ExitModule - Ok


Post Edited ( 03-26-12 12:02 )

[Ripley]

jarmonik wrote:
What graphics card you have ?

Are the white pixels visible in a fullscreen mode ?

Is the desktop color resolution 16-bit by any chance ?

1) Here's the graphics "card"



2) Yes, white pixels are visible both in a window and in full screen (also checking/unchecking "Full Screen Window" and "Disable Vsync" fields)

3) No, it's set at 32 bit.

I've tried changing every slider and parameter of the graphics control panel, but it never changed a single bit.



Post Edited ( 03-26-12 11:56 )