New Release Crew Dragon 2022

carlosriera

Member
Joined
Feb 4, 2020
Messages
53
Reaction score
9
Points
23
Sorry Brianj,
In any scenario, a black box appears that covers part of the DM2 2022 capsule.
 

carlosriera

Member
Joined
Feb 4, 2020
Messages
53
Reaction score
9
Points
23
I hope I have done well.
Sorry for my translator english.


**** Orbiter.log
000000.000: Build Aug 28 2016 [v.160828]
000000.000: Timer precision: 1e-007 sec
000000.000: Found 0 joystick(s)
000000.000: Module AtlantisConfig.dll .... [Build 160828, API 160828]
000000.000: Module AtmConfig.dll ......... [Build 160828, API 160828]
000000.000: Module DGConfigurator.dll .... [Build 160828, API 160828]
000000.000: Module ScnEditor.dll ......... [Build 160828, API 160828]
000000.000: Module OrbiterSound.dll ...... [Build 200811, API 160828]
000000.000: Module Rcontrol.dll .......... [Build 160828, API 160828]
000000.000: Module transx.dll ............ [Build 160216, API 160214]
000000.000: ---------------------------------------------------------------
BaseDir : C:\Orbiter 2016\
ConfigDir : C:\Orbiter 2016\Config\
MeshDir : C:\Orbiter 2016\Meshes\
TextureDir : C:\Orbiter 2016\Textures\
HightexDir : C:\Orbiter 2016\Textures2\
ScenarioDir: C:\Orbiter 2016\Scenarios\
000000.000: ---------------------------------------------------------------
D3D9 DLLs : C:\Windows\SYSTEM32\d3dx9_43.dll [v 9.29.952.3111]
: C:\Windows\SYSTEM32\d3d9.dll [v 10.0.19041.2788]
000000.000: ---------------------------------------------------------------
000000.000: Module D3D9Client.dll ........ [Build 211009, API 160828]
000000.000: Module InterMFD57.dll ........ [Build 161216, API 160910]
000000.000: ---------------------------------------------------------------
000000.000: >>> WARNING: Obsolete API function used: oapiRegisterMFDMode
000000.000: At least one active module is accessing an obsolete interface function.
000000.000: Addons which rely on obsolete functions may not be compatible with
000000.000: future versions of Orbiter.
000000.000: ---------------------------------------------------------------
000000.000: Module BurnTimeMFD.dll ....... [Build 180706, API 160828]
000000.000: Module BaseSyncMFD.dll ....... [Build 180408, API 160828]
000000.000: Module GenericCamera.dll ..... [Build 211009, API 160828]
000000.000: Module CrewDragonMFD.dll ..... [Build 230210, API 160828]
000000.000: Module PursuitMFD_2016.dll ... [Build 171119, API 160828]
000000.000:
000000.000: **** Creating simulation session
000000.000: D3D9: [DirectX 9 Initialized]
D3D9: 3D-Adapter.............. : AMD Radeon HD 5700 Series
D3D9: MaxTextureWidth......... : 16384
D3D9: MaxTextureHeight........ : 16384
D3D9: MaxTextureRepeat........ : 8192
D3D9: VolTexAddressCaps....... : 0x3F
D3D9: NumSimultaneousRTs...... : 4
D3D9: VertexDeclCaps.......... : 0x3FF
D3D9: MiscCaps................ : 0x3FCCF2
D3D9: XNA Math Support........ : Yes
D3D9: Vertex Texture.......... : Yes
D3D9: Separate AlphaBlend..... : Yes
D3D9: Shadow Mapping.......... : Yes
D3D9: D3DFMT_A16B16G16R16F.... : Yes
D3D9: D3DFMT_A32B32G32R32F.... : Yes
D3D9: D3DFMT_D32F_LOCKABLE.... : Yes
D3D9: D3DFMT_A2R10G10B10...... : Yes
D3D9: D3DFMT_L8............... : Yes
D3D9: D3DDTCAPS_DEC3N......... : Yes
D3D9: D3DDTCAPS_FLOAT16_2..... : Yes
D3D9: D3DDTCAPS_FLOAT16_4..... : Yes
D3D9: Runs under WINE......... : No
D3D9: D3D9Build Date.......... : 211009
D3D9: Available Texture Memory : 4082 MB
000000.000: D3D9: [3DDevice Initialized]
000000.000: D3D9: [Loading Constellations]
000000.000: D3D9: [D3D9Client Initialized]
000000.000: Module Sun.dll ............... [Build 160828, API 160828]
VSOP87(E) Sun: Precision 1e-006, Terms 554/6634
000000.000: Module Mercury.dll ........... [Build 160828, API 160828]
VSOP87(B) Mercury: Precision 1e-005, Terms 167/7123
000000.000: Module Venus.dll ............. [Build 160828, API 160828]
000000.000: Module VenusAtm2006.dll ...... [Build 160828, API 160828]
VSOP87(B) Venus: Precision 1e-005, Terms 79/1710
000000.000: Module Earth.dll ............. [Build 160828, API 160828]
000000.000: Module EarthAtmJ71G.dll ...... [Build 160828, API 160828]
VSOP87(B) Earth: Precision 1e-008, Terms 2564/2564
000000.000: Module Moon.dll .............. [Build 160828, API 160828]
ELP82: Precision 1e-005, Terms 116/829
000000.000: Module Mars.dll .............. [Build 160828, API 160828]
000000.000: Module MarsAtm2006.dll ....... [Build 160828, API 160828]
VSOP87(B) Mars: Precision 1e-005, Terms 405/6400
000000.000: Module Phobos.dll ............ [Build ******, API 060425]
000000.000: Module Deimos.dll ............ [Build ******, API 060425]
000000.000: Module Galsat.dll ............ [Build 160828, API 160828]
000000.000: Module Jupiter.dll ........... [Build 160828, API 160828]
VSOP87(B) Jupiter: Precision 1e-006, Terms 1624/3625
000000.000: Module Io.dll ................ [Build 160828, API 160828]
000000.000: Module Europa.dll ............ [Build 160828, API 160828]
000000.000: Module Ganymede.dll .......... [Build 160828, API 160828]
000000.000: Module Callisto.dll .......... [Build 160828, API 160828]
000000.000: Module Satsat.dll ............ [Build 160828, API 160828]
000000.000: Module Saturn.dll ............ [Build 160828, API 160828]
VSOP87(B) Saturn: Precision 1e-006, Terms 2904/6365
000000.000: Module Mimas.dll ............. [Build 160828, API 160828]
SATSAT Mimas: Terms 113
000000.000: Module Enceladus.dll ......... [Build 160828, API 160828]
SATSAT Enceladus: Terms 33
000000.000: Module Tethys.dll ............ [Build 160828, API 160828]
SATSAT Tethys: Terms 101
000000.000: Module Dione.dll ............. [Build 160828, API 160828]
SATSAT Dione: Terms 59
000000.000: Module Rhea.dll .............. [Build 160828, API 160828]
SATSAT Rhea: Terms 68
000000.000: Module Titan.dll ............. [Build 160828, API 160828]
SATSAT Titan: Terms 100
000000.000: Module Iapetus.dll ........... [Build 160828, API 160828]
SATSAT Iapetus: Terms 605
000000.000: Module Uranus.dll ............ [Build 160828, API 160828]
VSOP87(B) Uranus: Precision 1e-006, Terms 1827/5269
000000.000: Module Miranda.dll ........... [Build ******, API 060425]
000000.000: Module Ariel.dll ............. [Build ******, API 060425]
000000.000: Module Umbriel.dll ........... [Build ******, API 060425]
000000.000: Module Titania.dll ........... [Build ******, API 060425]
000000.000: Module Oberon.dll ............ [Build ******, API 060425]
000000.000: Module Neptune.dll ........... [Build 160828, API 160828]
VSOP87(B) Neptune: Precision 1e-006, Terms 391/2024
000000.000: Finished initialising world
000000.000: Module slc40abort.dll ........ [Build 221125, API 160828]
000000.000: Module dm2_capsule.dll ....... [Build 230210, API 160828]
000000.000: ---------------------------------------------------------------
000000.000: >>> WARNING: Obsolete API function used: VESSEL::CreateVariableDragElement
000000.000: At least one active module is accessing an obsolete interface function.
000000.000: Addons which rely on obsolete functions may not be compatible with
000000.000: future versions of Orbiter.
000000.000: ---------------------------------------------------------------
000000.000: Finished initialising status
000000.000: Finished initialising camera
000000.000: Finished setting up render state
000000.000: D3D9: [Scene Initialized]
000000.000: Finished initialising panels
000010.613: D3D9: [Session Closed. Scene deleted.]
000010.613: D3D9: [Destroy Render Window Called]
000010.613: **** Closing simulation session
 

BrianJ

Addon Developer
Addon Developer
Joined
Apr 19, 2008
Messages
1,676
Reaction score
900
Points
128
Location
Code 347
Hi,
I can't see anything wrong in your orbiter.log.
Does the same thing happen if you use Orbiter2016 default graphics (not D3D9 GC) ?
 

carlosriera

Member
Joined
Feb 4, 2020
Messages
53
Reaction score
9
Points
23
Orbiter_ng detects the graphics of the new PC but normal Orbiter doesn't seem to,the graphics of the original laptop remains and I can't test.
 
Last edited:

BrianJ

Addon Developer
Addon Developer
Joined
Apr 19, 2008
Messages
1,676
Reaction score
900
Points
128
Location
Code 347
Orbiter_ng detects the graphics of the new PC but normal Orbiter doesn't seem to,the graphics of the original laptop remains and I can't test.
Ah, OK. It sounds like a graphics card incompatibility problem of some kind - I don't have the knowledge to analyse or fix it. Sorry. Only thing I can suggest is maybe make sure the graphics card driver is updated (but probably won't fix the problem).
Cheers,
Brian
 

carlosriera

Member
Joined
Feb 4, 2020
Messages
53
Reaction score
9
Points
23
Thank you Brianj,
The drivers are recently downloaded. If so, I find it difficult to solve it.:unsure:
 

kuddel

Donator
Donator
Joined
Apr 1, 2008
Messages
2,064
Reaction score
507
Points
113
I once had a similar issue. The most recent driver did make things worse....I installed "version -1", "version-2", etc. pp. until it worked again.
I immediately saved and noted down that version for the next time I might ran into that.
After a couple of weeks yet another new version came out and that one did work again.
Fortunately my graphic card drivers are easy to up- and down-grade. That's not always the case :( I recommend using windows "system restore point" in that case.
 

carlosriera

Member
Joined
Feb 4, 2020
Messages
53
Reaction score
9
Points
23
When updating the graphics card driver with Windows 10,
I see a different graphics card than the AMD HD 5770 that comes with the PC, an AMD HD6770 using GPU-Z. I have verified that it is the same card with another heatsink.
The change of drivers I don't know if it could affect the performance of my PC.

 
Last edited:

carlosriera

Member
Joined
Feb 4, 2020
Messages
53
Reaction score
9
Points
23
I have another graphics card, a Gigabyte GTX 1050 Ti.
If I change the AMD for this one, would my problem with the DM2 capsule be fixed?
Do I have to remove the AMD drivers before turning off the computer and then install the NVIDIA drivers after turning on the computer?
 

MaxBuzz

Well-known member
Joined
Sep 19, 2016
Messages
1,392
Reaction score
2,126
Points
128
Location
Kursk
I have another graphics card, a Gigabyte GTX 1050 Ti.
If I change the AMD for this one, would my problem with the DM2 capsule be fixed?
Do I have to remove the AMD drivers before turning off the computer and then install the NVIDIA drivers after turning on the computer?
latest drivers came out in 2015 (I have a dual video card HD 7660G + 7670M)
 

EstebanDF

Active member
Joined
Apr 16, 2020
Messages
53
Reaction score
52
Points
33
@BrianJ I'm having a problem, If I save the scenario for later use, or if I try to reload from "Current State" I get a crash to desktop, orbiter log doesn't show any errors, if I want to resume, I have to open the .scn file and remove all vehicles except the crew dragon and the ISS, then it works. It doesn't make any sense to me, because the start launch scenario has all vehicles and it works just fine...
 

BrianJ

Addon Developer
Addon Developer
Joined
Apr 19, 2008
Messages
1,676
Reaction score
900
Points
128
Location
Code 347
@BrianJ I'm having a problem, If I save the scenario for later use, or if I try to reload from "Current State" I get a crash to desktop, orbiter log doesn't show any errors, if I want to resume, I have to open the .scn file and remove all vehicles except the crew dragon and the ISS, then it works. It doesn't make any sense to me, because the start launch scenario has all vehicles and it works just fine...
Hi,
can you post a scenario that causes the CTD? Also, it might be useful to post your orbiter.log after the CTD has happened.
I'll take a look.
Cheers,
Brian
 

EstebanDF

Active member
Joined
Apr 16, 2020
Messages
53
Reaction score
52
Points
33
Hello @BrianJ,
Here it is, This scenario comes from the original DM1\DM-1 Launch scenario.

Edit: I saved the scenario with the standard editor (Not TLE) in case you wonder, since I'm loading both.
 

Attachments

  • Orbiter.log
    6.6 KB · Views: 3
  • CrewDragon_Post_planeAlign.scn
    3.1 KB · Views: 4

BrianJ

Addon Developer
Addon Developer
Joined
Apr 19, 2008
Messages
1,676
Reaction score
900
Points
128
Location
Code 347
Hi,
thanks for posting the .scn and .log - unfortunately I can't reproduce the CTD - it works OK for me (using D3D9 GC r4.26, OrbiterSound4.0)

You could try some experiments....
I don't have ScenarioEditorTLE or FlyByWire - try disabling those in the Modules tab before starting scenario.
Try starting the scenario paused.
Try using default Orbiter2016 graphics rendering.

You did make me realise I haven't updated the CrewDragon2022 package with the latest modules that have the "Ctrl+ keypress fix"! Thanks.

Hope you find a fix, good luck.
BrianJ
 

francisdrake

Addon Developer
Addon Developer
Joined
Mar 23, 2008
Messages
1,060
Reaction score
864
Points
128
Website
francisdrakex.deviantart.com
I tried the posted scenario.
  • It runs, no crash.
  • Had to delete the THLEVEL line of the scenario file, as some thrusters never zeroed fully out and the vessel started rotating slowly,
when no Navmode was engaged.

On the maneuvering:
  • Orbital alignment was a little off, by 0,19°.
  • SyncOrbit was set to vessel Apoapsis. Better to be set to Intersect 1 or 2.

Approach and docking went well, without any hitch.
 

EstebanDF

Active member
Joined
Apr 16, 2020
Messages
53
Reaction score
52
Points
33
I tried the posted scenario.
  • It runs, no crash.
  • Had to delete the THLEVEL line of the scenario file, as some thrusters never zeroed fully out and the vessel started rotating slowly,
when no Navmode was engaged.

On the maneuvering:
  • Orbital alignment was a little off, by 0,19°.
  • SyncOrbit was set to vessel Apoapsis. Better to be set to Intersect 1 or 2.

Approach and docking went well, without any hitch.
Hello,

Thank you both for testing, yes, the plane alignment was a bit off, that's because I used the main engine to do the initial alignment, and it has very little RCS fuel, so needs to be set to normal / antinormal manually. I went from about 3.6º to 0.19º, and was going to correct later :D

I don't know if it's realistic to use the main engine for plane alignment, I guess that on a real life scenario the vessel would be much closer, IE the space shuttle could never correct 3º with the available fuel, and be able to complete all the maneuvering.

Also I think SyncOrbit can be anything you consider the best option in terms of fuel saving, there was no intersection at the time, the crew dragon orbit was lower than the ISS, so the setting at the time was not the last solution yet.

Edit: I checked again and I do have intersection, the plane alignment maneuver altered my orbit as well from 200 / 400 to 207 / 468 :D

thanks again,
Esteban.
 
Last edited:

EstebanDF

Active member
Joined
Apr 16, 2020
Messages
53
Reaction score
52
Points
33
Ran a couple more tests, and the scenario works by only removing this vessel:


Code:
Falcon9:Falcon9R_V12\f9_v12_drg2
  STATUS Orbiting Earth
  RPOS 4335927.321 4652915.050 -1775857.863
  RVEL 5572.4699 -5093.9494 750.5770
  AROT 71.723 83.594 3.955
  VROT 0.0003 0.0014 -38.0319
  PRPLEVEL 2:0.227524
  THLEVEL 17:0.017472 18:0.017472 21:0.000015 23:0.000015
  NAVFREQ 0 0
  FAIRS 1
  SOST 1 0 0 0 1 1 1
  SOPR 0.9014626 200000.0 400000.0 23000.0 125000.0 OCISLY 0.4402
  LOTM 0 0 0 0 0.0000
  NOZL 0.0000 0
END

My D3D9 version is also 4.26, but my OrbiterSound is 5.0
 
Top