(closed) DeltaGliderIV+addons beta 20120320

[Ripley]

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

I've tried (at work) but UMMUs behave as expected.
Cannot replicate this.

[jarmonik]

Ripley wrote:
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.

Thanks for the information. After giving some thought to this problem, I have desided to close this issue since it's more like a hardware/driver failure. Debugging and finding a reason for the failure would take too much efforts and it's most likely unfixable.

Jarmo

[DanSteph]

ProAuroraX a écrit:
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  .

Can you reproduce it and if yes describe how ?

jarmonik a écrit:
Thanks for the information. After giving some thought to this problem, I have desided to close this issue since it's more like a hardware/driver failure.

I tagged it "green" for closed.

Dan

[RevoluPowered]

DGIV BUG

Short description:

Lines appear on model thanks to the engine effects.



Severity

Detail


Complete description

Lines and texture cutting on model, caused by the engines
( This happens on DX9 and stock, haven't been able to test it in DX11 yet. )

http://dl.dropbox.com/u/33495256/Artifacts.png


Reproduce bug

Engines On, Press F1, Look at same angle.



Post Edited ( 03-27-12 14:26 )

[RevoluPowered]

DGIV BUG

Short description:

Engine effect failure.


Severity

minor


Complete description

"Engine's exhaust lights stay on but the smoke turns off if you use the countdown instead of holding + on numpad"

When holding * it does this.

(Tested in DX9 and STOCK)

Reproduce bug


any second countdown start, after countdown burn engages press * the engine effect will still be on but the engines wont be thrusting and also the smoke stops.


Miscallenous

Thought it was important.



Post Edited ( 03-27-12 14:22 )

[RevoluPowered]

DGIV BUG

Short description:

Hydraulic Lock up.


Severity

minor


Complete description

Hydraulic lock up occurs when holding 8 or 2 then pressing an * to switch from ATM AUTO to rotation and or to translation.


Reproduce bug

press and hold 8 or 2 then press *.
Then you will see if you release your keys the hydraulics "jam"/bug in there position.

[RevoluPowered]

DGIV Request

Short description:

MFD Button Sound not present.


Severity

detail


Complete description

The 2D cockpit's MFD buttons don't make any noise.


Miscallenous

All the others do, perhaps it should.



Post Edited ( 03-27-12 14:29 )

[Ripley]

For tests involving fps and performance, I came to think that it could be important to report also the personal MFD refresh rate - set in Launchpad -> Parameters -> MFD refresh (sec).

Anyway, mine is (and was) always at 0.01.



Post Edited ( 03-27-12 15:54 )

[DanSteph]

RevoluPowered a écrit:
DGIV RequestShort description:

MFD Button Sound not present.

Done

Dan

[DanSteph]

RevoluPowered a écrit:
Short description:

Lines appear on model thanks to the engine effects.

3d glitch, impossible to solve. (unless its' really anormal , any picture ?)

Dan

[DanSteph]

RevoluPowered a écrit:
Complete description

"Engine's exhaust lights stay on but the smoke turns off if you use the countdown instead of holding + on numpad"

When holding * it does this.

Now numpad * abort countdown

Dan

[Ripley]

DanSteph wrote:

RevoluPowered a écrit:
Short description:
Lines appear on model thanks to the engine effects.

3d glitch, impossible to solve. (unless its' really anormal , any picture ?)
Dan

As far as I remember, this glitch has always been there, at least from the start of my Orbiter experience (from the release of O2010).

[RevoluPowered]

http://dl.dropbox.com/u/33495256/Artifacts.png

[RevoluPowered]

I'm wondering if you could add some enhancements in the configuration options for DGIV?

Conversation I just had with the guy who develops OMP:


Me:
I'm on the DGIV beta ( Its for updated graphics compatibility ). Do you have any ideas on how to make DGIV compatible with OMP, I shall ask dan if he can perhaps make omp specific configuration options.


Friedrich Kastner-Masilko wrote at 7:14 p.m. on 27 March 2012

DGIV in OMP: as soon as a vessel is ScnEditor spawnable, it is OMP compatible. Of course it could still cause troubles if it reacts violently to SetState() commands. I'm not sure, but I think DGIV deletes itself - spawning a burned wrack - if the gees are to high. And the later is detected by displacement over time, something that could get quite high due to the constant SetState() displacement made by OMP.

[Face]

Conversation I just had with the guy who develops OMP:

That would be me. I had no idea that you are a beta tester here...

As for the configuration options, I would advice against it. OMP is not finished, and as such I'd hate to see Dan being distracted with problems originating from it. It is quite possible that later releases of OMP behave all but different in terms of position displacement and/or vessel creation, so whatever is the problem now could be gone later.

regards,
Face

[SolarLiner]

RevoluPowered wrote:
http://dl.dropbox.com/u/33495256/Artifacts.png

Caused because the engine exhaust and it's flare is a texture, a plane always facing the camera's direction. So when a part of the mesh is nearest the "flare", the texture is perforated, and draw something like this. So it's an Orbiter bug, and not a DGIV or D3D9 bug.

[RevoluPowered]

Can someone check if it happens in the D3D11 client, apparently D3D11 uses a different method?

[asmi]

SolarLiner wrote:
Caused because the engine exhaust and it's flare is a texture, a plane always facing the camera's direction. So when a part of the mesh is nearest the "flare", the texture is perforated, and draw something like this. So it's an Orbiter bug, and not a DGIV or D3D9 bug.

Well, technically it is a bug, since GC is not required to exactly follow interface (remember these effects are still an echo from late 1990's era of DirectX 7 ) Infact these flares should be drawn during post-processing, because in the real life they ARE a result of image "post-processing" done by human eye and brain.

RevoluPowered wrote:
Can someone check if it happens in the D3D11 client, apparently D3D11 uses a different method?

No, currently it uses the same method as DX9, but there are plans to move that to post-processing step where it belongs.

[RevoluPowered]

asmi wrote:

RevoluPowered wrote:
Can someone check if it happens in the D3D11 client, apparently D3D11 uses a different method?

No, currently it uses the same method as DX9, but there are plans to move that to post-processing step where it belongs.

Thank goodness for that.

[luki1997a]

UCGO BUG

Short description:

UMMU unpack/auto unpack probe is not compatible [no ui]


Severity
minor

Complete description
No ui and infos about probe. In inline client it shows data on screen but not in d3d9


Reproduce bug
Release ummu/auto unpack probe


Miscallenous
Will you add this requested light to ummu like this one:

?



Post Edited ( 03-28-12 22:15 )

[DanSteph]

luki1997a a écrit:
Short description:

UMMU unpack/auto unpack probe is not compatible [no ui]


Severity
minor

Complete description
No ui and infos about probe. In inline client it shows data on screen but not in d3d9

I just tested it work perfectly, are you sure to have the latest dll ? "Orbiter_20120320.zip" (see pm)

luki1997a a écrit:
Will you add this requested light to ummu like this one:
?

Sorry no, to much work. I deal already with 10-12 DLL, 4 complete addon and two minors now splitted in two version (2006&2010)
I would be happy if by any chance I don't f.. mess something with such big work and thousand files. (>1552 X 2)

Dan

[DanSteph]

I'm updating yet all the scenarios and the documentation. I'll need some help in english.

Can someone translate this below in good english ?

DGIV-3 April 2012 update

 -Fully compatible with graphic clients. Tested on DX11 and DX9 clients (amsi & jarmonik)
 -Atmospheric flight controls now much more reactive for a better flight experience.
 -Airlock local light. (open nosecone)
 -4 MFD's availables on the main panel (ONLY if you run orbiter with at least a 1920 width screen)
 -All scenarios corrected to take in account Orbiter 2010.
 -The DGIV-3 due to new Orbiter2010 features does not run anymore on Orbiter 2006.

Thanks

Dan

[Ripley]

DanSteph wrote:
I'm updating yet all the scenarios and the documentation. I'll need some help in english.

Can someone translate this below in good english ?

DGIV-3 April 2012 update

 -Fully compatible with graphic clients. Tested on DX11 and DX9 clients (amsi & jarmonik)
 -Atmospheric flight controls now much more reactive for a better flight experience.
 -Airlock local light. (open nosecone)
 -4 MFD's availables on the main panel (ONLY if you run orbiter with at least a 1920 width screen)
 -All scenarios corrected to take in account Orbiter 2010.
 -The DGIV-3 due to new Orbiter2010 features does not run anymore on Orbiter 2006.

Thanks

Dan

Are we close to release??

Even if I'm Italian, I'll give a shot to translate it, even if it's already nearly perfect:

DGIV-3 April 2012 update

 - Fully compatible with graphics clients. Tested on DX11 and DX9 clients (amsi & jarmonik).
 - Atmospheric flight controls now much more reactive for a better flight experience.
 - Airlock local light (open nosecone).
 - 4 MFDs available on the main panel (ONLY if you run Orbiter with at least a 1920 wide screen)
 - All scenarios corrected to take in account Orbiter2010.
 - The DGIV-3, due to new Orbiter2010 features, does not run anymore on Orbiter2006.



Post Edited ( 03-29-12 18:47 )

[asmi]

DanSteph wrote:

 -Fully compatible with graphic clients. Tested on DX11 and DX9 clients (amsi & jarmonik)

Dan, my nickname is asmi, not amsi

[Ripley]

Ripley wrote:
...(amsi & jarmonik)...

Ops!