See site in english Voir le site en francais
Website skin:
home  download  forum  link  contact

Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length

Author Topic: [Closed] BETA 2 Of deltaGliderIV (second beta release)  (Read 21627 times)

0 Members and 1 Guest are viewing this topic.

Offline DanSteph

  • Administrator
  • Legend
  • *****
  • Posts: 15407
  • Karma: 256
  • Hein, quoi !?
    • FsPassengers
29 December 2006, 18:07:01
EDIT: This thread is now closed, for current beta thread see:
http://orbiter.dansteph.com/forum/index.php?topic=11938.msg183499#msg183499











BETA 2 of DeltaGliderIV

For a list of DGIV feature and important notice see 1st beta thread here: (closed thread)
http://orbiter.dansteph.com/forum/index.php?topic=11922.msg183132#msg183132

Here's the file:
http://www.dansteph.com/publie/DeltaGliderIVBeta20061229.zip

Warning !

-it is a GOOD idea to install the pack after a fresh reboot of your computer
otherwise some files may not be copied properly due to XP or Orbiter holding them.
For beta testing it's important to ensure to not have false bug report.

-Simply unzip the archive in your Orbiter directory.



List of correction since BETA 1:


DGIV:

-Color of checklist and sys message increased, for people that have trouble with low contrast.
-Solved HUD bug with creation by scenery editor
-Solved visual bug when created by scenery editor
-Removed bug with mini HUD animation
-Removed all misc object from scenery editor
-Solved bug with text in normal Hud with door status.
-Solved bug with texture of door when ejection.
-Corrected bug with name list in dg4config.exe
-Corrected bug with capt name in dg4config.exe
-DGIV use private rotation and translation sound in case other dll handle the stock one and cause CTD
-Changed Thruster door button logic: Auto is now middle and open is on the right.
-Solved bug with seat belt button not working with power failure preventing ejection.
-Corrected inner door button behaviour.

Ummu:

-UMmu can't grapple DGIV or others vessel anymore.
-External Temperature show now in all hud mod.
-Changed text in attachment hud.
-Turbopack now keep their fuel level, can be refuel only in DGIV or in base.
-Corrected a bug with transfert beetween docked ship, added a scenario in DgIV "tuto" folder to explain transfert.


FOR THOSE THAT USED ALPHA VERSION OF UMMU SDK IN THEIR VESSEL:

This new version of Ummu is NOT compatible with the alpha release
and the new SDK is NOT released currently. It will be done in the meaning
time but UMmu SDK evolve to often yet for a release.

I recall also that releasing an addon with an alpha or beta of a SDK is not a good
things as it may confuse anyone.




Message modifié ( 09-01-2007 01:28 )


Offline wolfast

  • Newbie
  • *
  • Posts: 10
  • Karma: 0
Reply #1 - 29 December 2006, 18:08:18
weeee!!!!  Downloading
:turning:


Director manned
Space flight
SimNASA
simnasa.org

Offline reverend

  • Newbie
  • *
  • Posts: 7
  • Karma: 0
Reply #2 - 29 December 2006, 19:54:06
I still have an issue with Gear / Hover Failure when loading an On-Orbit Scenario.

Here's what I did so you can replicate this:

1) Start eh DGIV on Mars Scenario
2) Take off and fly to orbit
3) Obtain a nearly circular orbit
4) Press CTRL+Q  (this saves (Current State).scn)
5) Reload (Current State).scn


Right at the start of the simulation you'll get gear failure, hover failure, gear collapse.  

This happens with (current State).scn, QuickSaving, AutoSaves, or Saving with the Scenario Editor.

I have checked the saved scenario and the failgear and failhover settings are 0's, so something is causing them to fail
right when it starts up.

Hope this helps.



Offline Artlav

  • Jr. Member
  • **
  • Posts: 81
  • Karma: 0
Reply #3 - 29 December 2006, 20:18:28
Well, it works, and it looks good.:applause:

A quick-noted bug report and suggestions:

Noticible bugs:
-When you delete the ummu's reference object (scenary editor or other) -  CTD.
-Time warp is not working with ascent autopilot. It worked fine in DGIII.
-If you order the nose cone or airlock doors to open/close, then turn off the airlock power, they keep moving (unlike
radiator, turbo doors and antenna).

Minor bugs:
-When i landed the DGIV upside-down, the gears and hover engines was damaged... Wierd.
-The "Due to high temperature..." string appears when any DGIV is burned, whatever vessel you are in now.


Suggestions:
-Space suits reserve oxygen is not saved in the scenario.
-Turbo pack fuel is not saved in the scenario. Thus, no way to retry the failed stunts.
-Pitch indicator in the mmu. It's hard to do the TurboPack-powered moonhopping without it.
-When ejecting in space, the velocityes of the pilot and objects should be a little less. It's hard to compensate the
4m/s with mmu rcs in a tight situation.

-----
The Turbo-Landing scenario (Medium hardness):
DGIV is going candle-up, SS1 style, when APA hits 120Km, the power failing.
Assuming that mechanical control failed too.
The pilot (only he is aboard) should leave the vessel (low-powered eject? I just opened the airlocks before failure),
grab one turbo pack, and make it safely to the ground.
-----

Thta's it, hope this helps.


Offline DFP NEVERDIE

  • Jr. Member
  • **
  • Posts: 24
  • Karma: 0
Reply #4 - 29 December 2006, 21:11:34
Thats the DG oh ah.
Thats the Ummu oh ah!
:badsmile:


Offline Krytom

  • Legend
  • ******
  • Posts: 1058
  • Karma: 0
Reply #5 - 29 December 2006, 21:18:25
Quote
-Time warp is not working with ascent autopilot. It worked fine in DGIII.

That's not a bug, it's's a feature. It comes up with a message somewhere saying "Time warp is forbidden during autopilot" I
think.



Offline DanSteph

  • Administrator
  • Legend
  • *****
  • Posts: 15407
  • Karma: 256
  • Hein, quoi !?
    • FsPassengers
Reply #6 - 29 December 2006, 21:30:29
Quote
reverend a écrit:
I still have an issue with Gear / Hover Failure when loading an On-Orbit Scenario.
Right at the start of the simulation you'll get gear failure, hover failure, gear collapse.  


Sorry just tried it work fine... I don't see any reason why private variable would sundenly
pass from 0 to 1 without reasons... !??

Seem for whatewer reason Orbiter's vessel value for altitude,vertical speed and ground
touch at one moment during saving are false giving impression that the vessel touched
hard ground... I doubt such bug come from DGIV, something is happening in your
installation as no-one else reported such issue.

Did you tried to disable all others modules before your try ? intermod ? multiplayer ?

Dan



Message modifié ( 29-12-2006 22:47 )


Offline darkvoid

  • Jr. Member
  • **
  • Posts: 47
  • Karma: 0
Reply #7 - 29 December 2006, 21:34:58
I found that flying at 21.000m at mach 3.0 the nose cone temperature is near 750ºc.

From the literature that I've read "Mach 3 generates a nose temperature nearly... of 300°C". This applied to SR-71
and Mig 25.

Is the 750ºc normal?!


Offline DanSteph

  • Administrator
  • Legend
  • *****
  • Posts: 15407
  • Karma: 256
  • Hein, quoi !?
    • FsPassengers
Reply #8 - 29 December 2006, 21:38:54
Quote
Artlav a écrit:
When you delete the ummu's reference object (scenary editor or other) -  CTD.


Ah the reference... ok Will have a look...

Dan


>Is the 750ºc normal?!

Giving the shape of the nose yes...

Dan



Message modifié ( 29-12-2006 21:42 )


Offline Quick_Nick

  • Sr. Member
  • ****
  • Posts: 446
  • Karma: 0
Reply #9 - 29 December 2006, 22:05:12
Shape of nose, altitude, F vs C.(probably both the same though)
Anyways... thanks for the update Dan!!!


-Nick

Offline Travis Reed

  • Sr. Member
  • ****
  • Posts: 354
  • Karma: 0
Reply #10 - 29 December 2006, 22:24:31
Quote
DanSteph wrote:
Quote
Artlav a écrit:
When you delete the ummu's reference object (scenary editor or other) -  CTD.

Ah the reference... ok Will have a look...

Dan


&gtIs the 750ºc normal?!

Giving the shape of the nose yes...

Dan

I've noted that anytime I delete things using the Scenario Editor, I have to have it paused, then save the scenario.
Otherwise I'll lose my work when Orbiter CTDs after unpausing. As a result, I'm not sure this CTD is a result of the DGIV or
UMmu. Although I might just need a clean install of Orbiter to solve that (assuming it's not an inherent bug...)


Offline DanSteph

  • Administrator
  • Legend
  • *****
  • Posts: 15407
  • Karma: 256
  • Hein, quoi !?
    • FsPassengers
Reply #11 - 29 December 2006, 22:41:05
Quote
Artlav a écrit:
When you delete the ummu's reference object (scenary editor or other) -  CTD.

Solved, version not yet available. Was UMmu of course...

Dan


Offline Twilight

  • Jr. Member
  • **
  • Posts: 43
  • Karma: 0
Reply #12 - 29 December 2006, 23:10:11
Here's a bug, happened in DGIII aswell.

Startup "Docked to ISS", open all airlocks, make sure APU/generators are on, and the seatbelt light. Keep Engine and
RCS on. Undock! You should explosivly decompress, because the seatbelt light is on, you should still be alive, but now
go back and dock with the station.

Your cabin pressure/temp/everything should return to normal, but look up at your airlocks! Inner door is open, and
there's no pressure in the airlock still!



Also, PRO500S0 is still missing from Checklist MFD.


Offline DanSteph

  • Administrator
  • Legend
  • *****
  • Posts: 15407
  • Karma: 256
  • Hein, quoi !?
    • FsPassengers
Reply #13 - 29 December 2006, 23:59:10
Will have a look, check list need to be completely rechecked I think I'll do it last.

Whohoo next version UMmu will play sound if airlock closed or ship already full...
I think for a SDK that allow anyone to have mmu for their ship Ummu will be a
good addon.

Dan


Offline buznee

  • Newbie
  • *
  • Posts: 4
  • Karma: 0
Reply #14 - 30 December 2006, 02:30:55
where is the dg4config.exe, I cant seem to find it.


~Danny

Offline DanSteph

  • Administrator
  • Legend
  • *****
  • Posts: 15407
  • Karma: 256
  • Hein, quoi !?
    • FsPassengers
Reply #15 - 30 December 2006, 02:51:53
sound/DeltagliderIV

Dan


Offline Travis Reed

  • Sr. Member
  • ****
  • Posts: 354
  • Karma: 0
Reply #16 - 30 December 2006, 03:42:28
I've set up a new and relatively clean Orbiter install. I'm now getting the gear/hover engine failure upon loading a secnario with a DGIV in orbit. I'll list the addons I've installed, paste some orbiter logs, and generally post the results of some tests.

Addons Installed:
-Stock planetary textures upgrades (available from the Orbiter mirror sites)
-IMFD 4.6 (jarmonik's site)
-BaseSyncMFD latest version (jarmonik's site)
-AeroBrakeMFD 0.95 (OH)
-FuelSystem2 (on OH somewhere)
-Extended Map MFD 1.0b (can't remember where, might have been mentioned on the M6 forums)
-DeltaGliderEX v061015 (OH)
-SubOrbMFD 2.0 (OH?)
-Cam Shake 1.1 (OH)
-Cam Control 0.3 (OH)
-Rendezvous MFD v050621 (OH?)
-CameraMFD 0.12 Beta (OH)
-WarpDriveMFD latest version as of 061229 (OH)
-EquationMFD 11D (OH)
-SHUTTLE PB replacement v1.2 (OH)
-ISS12A.1 (OH)
-Hires Runway Texture (OH)
-newexhtex 1.2 (don't remember where, might have been mentioned on Dan's forum, the M6 forum, or possibly BigJim's forum)
-fuelmfd-031129 (I think this one came from avsim...I keep it around incase the other fuel system mfd fails)
-converted Space Skin (base skin available here I think, if not, it should be on OH)
-convrted NASA Skin (base skin available here I think, if not, it should be on OH)

Problem still occurs even with no modules loaded, even with a freshly started Orbiter. Will reboot machine and try again.
Nothing odd in the log files I've found.



Post Edited ( 12-30-06 03:43 )


Offline DanSteph

  • Administrator
  • Legend
  • *****
  • Posts: 15407
  • Karma: 256
  • Hein, quoi !?
    • FsPassengers
Reply #17 - 30 December 2006, 03:52:37
Odd... let me know if you find anythings that give an idea of what's happening.
My 1st suspect as said is at loading time during init the main loop start to run
but the values are not what they should be... *something might disturb those values*

Dan



Message modifié ( 30-12-2006 03:54 )


Offline Travis Reed

  • Sr. Member
  • ****
  • Posts: 354
  • Karma: 0
Reply #18 - 30 December 2006, 05:00:50
Alright, fresh reboot, fresh run of Orbiter and still have the problem. No modules loaded.

System Specs:
-CPU: AMD Athlon XP 2200+ running at 1.8 Ghz
-RAM: 1.5 GB PC2100 running at 266 Mhz
-OS: Windows XP Home with SP2
-Orbiter Version: 060929

Created a truly clean Orbiter install with nothing but the DGIV beta installed and I'm not having the problem anymore...of
course...this makes it less desirable to play...:(

Odd. I'm noting that even with my slightly less than clean install (see my previous post) I am only getting this on a
scenario I originally created for the 2003 version of the DG3 (and have since attempted to upgrade to work with 2006P1 and
the DGIV). Starting this scenario on the ground is fine, however, launching to orbit and then reloading a quicksave or
(Current State).scn comes up with this issue. The stock DGIV scenarios with the DGIV docked to a station don't seem to have
this problem, even with all the modules that I want to use loaded...

I'll paste the quicksave to see if anyone can spot anything amiss.

Quote
BEGIN_DESC
Orbiter saved state at T = 21567
END_DESC

BEGIN_ENVIRONMENT
  System Sol
  Date MJD 73819.2496177488
END_ENVIRONMENT

BEGIN_FOCUS
  Ship USS Terpathia
END_FOCUS

BEGIN_CAMERA
  TARGET USS Terpathia
  MODE Cockpit
  FOV 50.00
END_CAMERA

BEGIN_MFD Left
  TYPE User
  MODE Interplanetary
  MapMFD V5
  Reference Auto
  Target none
  Center GravityRef
  Data 0 1 1e-006 1 0 0 0 0 1 0 0 0
  MassLimit 1e+020
  CMode 0
  Config 1 1 1 1 0 0
  ExtMode 0
  Periapis none
  END
  CorMFD V4
  Reference Sun
  Target Mars
  Source Earth
  ActiveProg 1 1
  DataA 0 3 0 0 0 0
  DataB 1 1 73819.2587467014 0 0 3.299215962072631 0 73909.00280141203
  DVProg 0 0 0 0 0
  END
  EjectMFD V5
  Reference Auto
  Data 0 1 3 0 0 73819.30161055845 13401.1
  END
  BaseAprMFD V2
  Reference Auto
  Target none
  Source USS_Terpathia
  DataA 0 0 120000 0.0523599 0.0872665 1 1 73819.0017341088 73819.0035554051 0
  DataB 0 3 0 1 0 1
  END
  SlingMFD V4
  Reference Auto
  Source USS Terpathia
  Data 0 1 1 3 0 1 73819.0017341088 0
  END
  LaunchMFD V4
  Target None
  Data 0 1 1 3 0 1 73819.24683956597
  END
  mfdShare 1
  mfdProgram 2
END_MFD

BEGIN_MFD Right
  TYPE User
  MODE Interplanetary
  MapMFD V5
  Reference Auto
  Target none
  Center GravityRef
  Data 0 1 1e-006 1 0 0 0 0 1 0 0 0
  MassLimit 1e+020
  CMode 0
  Config 1 1 1 1 0 0
  ExtMode 0
  Periapis none
  END
  CorMFD V4
  Reference Sun
  Target Mars
  Source Earth
  ActiveProg 1 1
  DataA 0 3 0 0 0 0
  DataB 1 1 73819.2587467014 0 0 3.299215962072631 0 73909.00280141203
  DVProg 0 0 0 0 0
  END
  EjectMFD V5
  Reference Auto
  Data 0 1 3 0 0 73819.30161055845 13401.1
  END
  BaseAprMFD V2
  Reference Auto
  Target none
  Source USS_Terpathia
  DataA 0 0 120000 0.0523599 0.0872665 1 1 73819.0017341088 73819.0035554051 0
  DataB 0 3 0 1 0 1
  END
  SlingMFD V4
  Reference Auto
  Source USS Terpathia
  Data 0 1 1 3 0 1 73819.0017341088 0
  END
  LaunchMFD V4
  Target None
  Data 0 1 1 3 0 1 73819.24683956597
  END
  mfdShare -1
  mfdProgram 3
END_MFD

BEGIN_PANEL
END_PANEL


BEGIN_SHIPS
SS Callista:DeltaGliderIV
  STATUS Landed Earth
  BASE Cape Canaveral:4
  POS -80.6745290 28.5202595
  HEADING 135.09
  RCSMODE 0
  PRPLEVEL 0:1.000 1:1.000 2:0.983
  IDS 0:45 100
  NAVFREQ 94 524
  XPDR 0
  MeshSkin NASA
  NOSECONE 1 1.0000
  GEAR 1 1.0000
  AIRLOCK 1 1.0000
  INNERDOOR 0 0.0000
  COCKPIT 0 0.0000
  PRADIATOR_PROC 0 0.0000
  ANTENNA_PROC 0
  TURBODOORL 0 0.0000
  TURBODOORR 0 0.0000
  RightTurboPack 1
  LeftTurboPack 1
  StartPower_ext 2
  StartPower_batt 0
  StartPower_cell 0
  Apu_start 0
  Gen1 0
  Gen2 0
  GenSelector 0
  PowerHud 0
  PowerMfd 0
  PowerRadio 0
  PowerAirlock 0
  PowerEngine 0
  PowerLifepack 2
  PowerAp 0
  PowerMainBus 0
  PassengerSeat 1
  Strobe 0
  HydGearPress 0
  LevelBatt 100.0022
  Emergency_power 10000.0000
  Force_Canopy 0
  VoltageStartBus 48.0000
  VoltageGen1 0.0000
  VoltageGen2 0.0000
  VoltageGenBus 96.0000
  ExtFuelHatch 0
  ExtFuelValve 0
  DockFuelValve 0
  FuelInputSelector 0
  XFeedFuel 0
  DumpMainFuel 0
  DumpRcsFuel 0
  HoverValve 0
  MainValveL 0
  MainValveR 0
  RcsValve 0
  AirIntake 0
  TurboPump 0
  ComputerDisplay 0
  HudMode 0
  O2tankALevel 100.0000
  N2tankALevel 100.0000
  O2tankBLevel 100.0000
  N2tankBLevel 100.0000
  DockInputValve 0
  ExtInputValve 1
  InputSelector 1
  ButtonTankAO2 2
  ButtonTankAN2 1
  ButtonTankBO2 2
  ButtonTankBN2 1
  ButtonAFan 2
  ButtonAFilter 2
  ButtonACooling 2
  ButtonAMoist 2
  ButtonBFan 0
  ButtonBFilter 0
  ButtonBCooling 0
  ButtonBMoist 0
  Radiator 0
  ShipControl 5
  LifeDisplay 3
  CabinO2Level 21.4000
  CabinCO2Level 600.0000
  CabinTempLevel 21.2000
  CabinPressure 14.7000
  CabinMoistLevel 36.0000
  CabinDustLevel 0.0002
  CabinO2Setting 21.4000
  CabinTempSetting 21.2000
  CabinPressSetting 14.7000
  O2ConsumptionSetting 1
  AntennaTarget no_target
  NoOneOnBoard 0
  NoPilotOnBoard 0
  PassengerNumber 0
  PilotName Capt_Josh_Freedman
  PilotAge 23
  BasePilotPulse 50.0000
  FailGearFailure 0
  FailGearCollapse 0
  FailLeftMainEngine 0
  FailRightMainEngine 0
  FailHoverEngine 0
  FailRcs 0
  FailSurfaceControl 0
  FailComputer 0
  FailComputerBlueScreen 0
  FailAutopilot 0
  FailExtRadiator 0
  FailAirbrake 0
  FailNoseCone 0
  FailCanopy 0
  FailAntenna 0
  FailLeftTurbo 0
  FailRightTurbo 0
  EmergencyDoor 0
  SpacesuitTimer 0
  EmergencySequenceStep 0
  SecureEject 1
  RetroDoor 1
  HoverDoor 1
END
USS Terpathia:DeltaGliderIV
  STATUS Orbiting Earth
  RPOS -4748260.35 908130.97 4515828.03
  RVEL -5325.818 192.669 -5646.230
  AROT 177.99 43.58 170.72
  VROT -0.00 0.07 -0.00
  PRPLEVEL 0:0.897 1:0.986 2:1.000
  IDS 0:45 100
  NAVFREQ 94 524
  XPDR 0
  MeshSkin space
  NOSECONE 0 0.0000
  GEAR 0 0.0000
  AIRLOCK 0 0.0000
  INNERDOOR 0 0.0000
  COCKPIT 0 0.0000
  PRADIATOR_PROC 0 0.0000
  ANTENNA_PROC 0
  TURBODOORL 0 0.0000
  TURBODOORR 0 0.0000
  RightTurboPack 1
  LeftTurboPack 1
  StartPower_ext 0
  StartPower_batt 2
  StartPower_cell 0
  Apu_start 2
  Gen1 2
  Gen2 2
  GenSelector 0
  PowerHud 2
  PowerMfd 2
  PowerRadio 2
  PowerAirlock 0
  PowerEngine 2
  PowerLifepack 2
  PowerAp 2
  PowerMainBus 2
  PassengerSeat 1
  Strobe 0
  HydGearPress 0
  LevelBatt 100.0005
  Emergency_power 10000.0000
  Force_Canopy 0
  VoltageStartBus 48.0010
  VoltageGen1 97.5509
  VoltageGen2 96.0121
  VoltageGenBus 96.0000
  ExtFuelHatch 0
  ExtFuelValve 0
  DockFuelValve 0
  FuelInputSelector 0
  XFeedFuel 0
  DumpMainFuel 0
  DumpRcsFuel 0
  HoverValve 0
  MainValveL 2
  MainValveR 2
  RcsValve 2
  AirIntake 0
  TurboPump 0
  ComputerDisplay 1
  HudMode 0
  O2tankALevel 100.0183
  N2tankALevel 100.0000
  O2tankBLevel 100.0000
  N2tankBLevel 100.0000
  DockInputValve 0
  ExtInputValve 0
  InputSelector 0
  ButtonTankAO2 2
  ButtonTankAN2 1
  ButtonTankBO2 2
  ButtonTankBN2 1
  ButtonAFan 2
  ButtonAFilter 2
  ButtonACooling 2
  ButtonAMoist 2
  ButtonBFan 0
  ButtonBFilter 0
  ButtonBCooling 0
  ButtonBMoist 0
  Radiator 0
  ShipControl 4
  LifeDisplay 3
  CabinO2Level 21.3916
  CabinCO2Level 362.8263
  CabinTempLevel 21.1001
  CabinPressure 14.7000
  CabinMoistLevel 36.0000
  CabinDustLevel -0.0001
  CabinO2Setting 21.4000
  CabinTempSetting 21.2000
  CabinPressSetting 14.7000
  O2ConsumptionSetting 6
  AntennaTarget no_target
  NoOneOnBoard 0
  NoPilotOnBoard 0
  PassengerNumber 2
  PilotName Capt_Ben_Trefon
  PilotAge 18
  BasePilotPulse 74.0000
  Passenger1Name Tom_Barron
  Passenger1Age 19
  Passenger1BasePulse 80.0000
  Passenger2Name Joyce_Barron
  Passenger2Age 18
  Passenger2BasePulse 89.0000
  FailGearFailure 0
  FailGearCollapse 0
  FailLeftMainEngine 0
  FailRightMainEngine 0
  FailHoverEngine 0
  FailRcs 0
  FailSurfaceControl 0
  FailComputer 0
  FailComputerBlueScreen 0
  FailAutopilot 0
  FailExtRadiator 0
  FailAirbrake 0
  FailNoseCone 0
  FailCanopy 0
  FailAntenna 0
  FailLeftTurbo 0
  FailRightTurbo 0
  EmergencyDoor 0
  SpacesuitTimer 0
  EmergencySequenceStep 0
  SecureEject 1
  RetroDoor 1
  HoverDoor 1
END
END_SHIPS


Offline DanSteph

  • Administrator
  • Legend
  • *****
  • Posts: 15407
  • Karma: 256
  • Hein, quoi !?
    • FsPassengers
Reply #19 - 30 December 2006, 05:16:30
A stupid idea maybe but who know ? try a shorter name without space...
Not "USS Terpathia:DeltaGliderIV" but  "S1:DeltaGliderIV" for example.
I know that at least for attachment Orbiter don't like space or long name.

It *may* be the longer loading delay also, due to textures for example,
for odd reason the main loop start but loading is not fully finished  and
the data are not fully ready.

Can you try an empty install and just install textures add-ons for example ?
After it's just a matter to launch the scenery above beetween addon add
and see when the problem appear.

Something is different in your current install vs stock install, this have to
do with the problem and we have to find what it is.

Much Thanks for your help !

Dan

PS: do you have any message in sysbox like "Ground Impact:" for example ?



Message modifié ( 30-12-2006 05:24 )


Offline Travis Reed

  • Sr. Member
  • ****
  • Posts: 354
  • Karma: 0
Reply #20 - 30 December 2006, 06:54:05
The sysbox simply states:
Quote
Welcome aboard
Gear collapsed
Hover engine failure
The scenario used to work with the DGIII with the names. Any spacecraft name issue I get seems to result in a CTD. Anyway,
changing the names didn't help.


The specific hi-res addons I'm using:
-PlanetHires060504.zip
-Mars060504_L9.zip
-Enceladus060504_L8.zip
-Mars060504_L10.zip
-Earth060504_L10.zip

After running it I had no problems. Then I tried using the same skin I did in the scenario I posted above. No effect, ran
smoothly. Of course I had set it to ignore the MeshSkin value in the scn files by selecting the space skin in the DGIV config
program. It still ran fine...until I editied the scenario (by hand with a text editor) to include 2 DGIVs, one wanting to use
the Space skin, the other wanting to use the NASA skin (both skins properly converted, aside from the missing gear layer).
After this I got the gear/hover failure.

<summary>
Gear/Hover Engine Failure Bug Successfully Traced
The problem seems to lie in the loading of skins when you have forced a skin using the DGIV config program and your scenario
contains more than one DGIV which would normally have different skins. </summary>



Offline Quantum Burrito Meal

  • Jr. Member
  • **
  • Posts: 75
  • Karma: 0
Reply #21 - 30 December 2006, 07:00:39
I get a CTD when grappling a turbopack with a DGIV


------------------------------------------
Proud creator of two (2) addons

One of which is soon to be out of date, and one is not yet useable. Great Success!

Offline DanSteph

  • Administrator
  • Legend
  • *****
  • Posts: 15407
  • Karma: 256
  • Hein, quoi !?
    • FsPassengers
Reply #22 - 30 December 2006, 07:06:00
Quote
Travis Reed a écrit:
summary&gt
Gear/Hover Engine Failure Bug Successfully Traced
The problem seems to lie in the loading of skins when you have forced a skin using the DGIV config program and your scenario
contains more than one DGIV which would normally have different skins. &lt/summary&gt



mhhhhhh  scratch scratch ... :wonder: :doubt:

Can you try this one please ? (only DLL to place in modules, take care to really replace the old)
http://www.dansteph.com/publie/DeltaGliderIV_travis.zip

Much tanks for your test !

Dan



Message modifié ( 30-12-2006 07:09 )


Offline DanSteph

  • Administrator
  • Legend
  • *****
  • Posts: 15407
  • Karma: 256
  • Hein, quoi !?
    • FsPassengers
Reply #23 - 30 December 2006, 07:07:36
Quote
Quantum Burrito Meal a écrit:
I get a CTD when grappling a turbopack with a DGIV


Sorry, can't do anything with so few info...
was it grappled to a mmu , on earth, orbit,  other ?Targeted by another mmu ?
can you reproduce it ?

My bet is that it was targeted by another mmu this bug was solved but not in your version.

Thanks,

Dan



Message modifié ( 30-12-2006 07:36 )


Offline Travis Reed

  • Sr. Member
  • ****
  • Posts: 354
  • Karma: 0
Reply #24 - 30 December 2006, 07:17:03
Dan, no apparrent effect with the new dll. The problem only occurs when the user has locked it to a specific skin using the
DG4config and attempts to load a scenario where more than one DGIV exists and at least two different skins are called for (as
in the scenario I posted above, one skin is the Space and the other is the NASA). The same occurs if I change them to any of
the stock DG4 skins you've provided (as long as 2 or more skins are called for in the scenario). Best bet is to not allow the
user to lock things to a specific skin in the config program and just make it easier to define things using Orbiter's
Scenario Editor.