OHM DG-Launcher (Russian Federation) v1.02

OrbitHangar

Addon Comments
Joined
Apr 9, 2008
Messages
3,832
Reaction score
18
Points
0

Author: n_molson

Last of the DG-Launcher series, the Russian Federation edition of the launcher can lift more than 27 tons from Baïkonur to the ISS. Unlike it's predecessors, it uses an "in-line", multistage configuration.

Includes 1 test scenario (launch from Baikonur Site 110).

Requires :

  •  Velcro Rockets (by Sputnik)
  •  DeltaGlider IV (by Dansteph)
  •  UGCO (by Dansteph)

Recommended :

  • Baikonur surface tiles 1.1

See the included doc for detailed specs & instructions.


Update v1.02 :

  • The DLL files required for the particle effects have been recompiled (release) against Orbiter 2010-P1. The add-on was not working properly anymore, should be fixed.

Have fun !


DOWNLOAD
 
Possible Problem

It might just be a issue on my end but upon installing the addon all DG launchers and all velcro rockets using the LF2 exhaust textures wont display the flame or smoke. I tried reinstalling velcro rockets which fixed the flame issue but it still would not show the smoke trails for any velcro rocket (unless I've been blind and just not noticed they don't have smoke trails).

Errors from Orbiter.log

Code:
>>> ERROR: Could not load vessel module:
>>> [Vessel::LoadModule | .\Vessel.cpp | 5432]
---------------------------------------------------------------
---------------------------------------------------------------
>>> ERROR: DGL_RU_B_ParticleGEN
>>> [Vessel::LoadModule | .\Vessel.cpp | 5433]
---------------------------------------------------------------
---------------------------------------------------------------
>>> ERROR: Could not load vessel module:
>>> [Vessel::LoadModule | .\Vessel.cpp | 5432]
---------------------------------------------------------------
---------------------------------------------------------------
>>> ERROR: DGL_RU_V_ParticleGEN
>>> [Vessel::LoadModule | .\Vessel.cpp | 5433]

Other than that it's a great addon:thumbup:
:hail::probe:
 
The LF2 thing is normal. The add-on includes a textures that overwrites the default LF2, so that there is no exhaust texture (few people use LF2 exhausts, I think...)

The particle effects are generated by the two files that point your Orbiter log. You need 4 files : 2 .cfg files, and 2 .dll modules. Their are included in the download.

Of course, those modules were compiled under the Orbiter 2010 SDK & will not work under previous versions...
 
Ok, I have installed on a fresh install of Orbiter 2010 with nothing but velcro rockets, DG-Launchers and everything else needed to run it. I have all the C++ redistributable packages. And made sure that all the files in the addon were extracted to the correct places.

I see the 2 dll files:
DGL_RU_B_ParticleGEN.dll
DGL_RU_V_ParticleGEN.dll

I'm assuming (correct me if I'm wrong) the 2 cfg files are:
DGL_RU_FX
DGL_RU_FX2

Everything looks like it should work but I'm still getting the same result. Any thoughts?
 
I'm using VC++ 2008 if that can help...

It works correctly on a clean install of O'2010 on my comp, so I don't get it... To install the add-on, I copy the zip file on my O'2010 root directory, then I click "Extract here"... So the files go in the expected folders.

The .dll files have to be in the "Modules/" directory
The .cfg files have to be in the "Config/Vessels/Velcro/" directory
 
Well, it works for me. My video card is crappy, so it is indeed choppy before the LRBs sep. Is ther an AP?

There is no exhaust of any kind though, no texture, no particles, nothing at all.
 
Yes, as written in the doc press "O" for launch, as with any other Velcro vessels...
 
Ah, I didn't read the doc.... lol :blush:


I did see something about "O" in the scenario description when I went back to try for a better (read "successful") orbit, and I hit it, the countdown started and I saw nothing else, so I hit it again, and I guess maybe I turned it off. But it just kept on going straight, all 3 stages, then I decided to see what could happen, I and cranked up the DG-IV (which I have set to it's lowert fuel and thrust settings btw), and turned on the turbo pumps.... with 1.4% fuel left, the ApA had long since gone to "N/A", I cut the engines and surface MFD still showed a slight increase in speed, and I was at 148m Km, Earth was fading in the bacground, the moon was a mere 340m Km away, and if I had been pointed at it, I could have made it there in a straight vertical launch with no parking or transfer orbits necessary. :lol:

(just shows how over the top the DG-IVs engines and fuel tanks are)
 
I looked through some comments on your other DG launchers specifically the American DG launcher. I have the same problem as Wonderer did/does. I think it might be a problem with SmokeGEN.dll. I have it in the right folder but it's acting like its not there giving me

Code:
>>> ERROR: Could not load vessel module:
>>> [Vessel::LoadModule | .\Vessel.cpp | 5432]
---------------------------------------------------------------
---------------------------------------------------------------
>>> ERROR: SmokeGEN
>>> [Vessel::LoadModule | .\Vessel.cpp | 5433]

Deleting the file gives the same error in the log. I also tried a solution you suggested...

These parameters can be read only by the Velcro module, and the SmokeGENs have their own modules. Thank you for pointing it.

Concerning your problem, I think that I forgot to include some C++ libraries in the .dll, or something like that. I think that some people use the SDK, and have the libraries already set, it's why that works on their computer. But I may be mistaken, and I'll have to look deeper into this. However, I want to release the third launcher first.

What you can do now is replacing the "LF2" exhaust parameter in the "DG_Launcher_GEM60" config files (2 files) by "KERO". That should display the standard Velcro textures (better than nothing).

Replacing the exhaust parameters does change the flame color but still doesn't add smoke/particle effects. However, I do have a small particle effect before starting the engines but it goes away a few seconds after liftoff (see attachments)

But other than the flame/particle effects everything seems to work great.
 

Attachments

  • American DG-Launcher.JPG
    American DG-Launcher.JPG
    58.4 KB · Views: 26
  • American DG-Launcher 2.JPG
    American DG-Launcher 2.JPG
    85.6 KB · Views: 22
I still have the no exhaust problem with the american launcher and now with the russian launcher as well.
 
The small particle effect you have before launch is related to the DGIV module, so it's normal.

Yeah, I remember that Wonderer had exactly the same issue.

The fact is that, for some reason, the .dll does not load. Orbiter tries to load it, but there is an error somewhere in the process... Which make me think again to a library or a VC++ 2008 redistributable installation problem...

I'm not sure at all, but the Framework.NET packages sometimes get involved into this. I have Framework.NET v4.0

Edit : so maybe if we find what is common to your 2 configs, maybe we'll be able to track down the problem ?
 
Just downloaded .NET Framework 4.0 and get the same error with SmokeGEN.dll
 
I'll see if can find another way to add particle streams, but it will probably take some time...
 
Awesome! I love your DG-Launchers, just today I launched to the moon using it to launch the DGIV.
 
N_Molson, I too am having that same problem.

I'm running on Windows 7 Professional 64bit with the Framework.NET 4 client installed, and both 2005 and 2008 VC Redistributables.

Orbiter 2010, and everything seems to be installed ok. As I said, the launcher works, sounds are there, it stages, all that, just no particle streams.

I'm seeing this in the log file -
Code:
---------------------------------------------------------------
---------------------------------------------------------------
>>> ERROR: Could not load vessel module:
>>> [Vessel::LoadModule | .\Vessel.cpp | 5432]
---------------------------------------------------------------
---------------------------------------------------------------
>>> ERROR: DGL_RU_B_ParticleGEN
>>> [Vessel::LoadModule | .\Vessel.cpp | 5433]
---------------------------------------------------------------
---------------------------------------------------------------
>>> ERROR: Could not load vessel module:
>>> [Vessel::LoadModule | .\Vessel.cpp | 5432]
---------------------------------------------------------------
---------------------------------------------------------------
>>> ERROR: DGL_RU_V_ParticleGEN
>>> [Vessel::LoadModule | .\Vessel.cpp | 5433]
---------------------------------------------------------------
Finished initialising status
Finished initialising camera
Finished initialising panels
Finished setting up render state
---------------------------------------------------------------
>>> WARNING: Obsolete API function used: oapiGetStationCount
At least one active module is accessing an obsolete interface function.
Addons which rely on obsolete functions may not be compatible with
future versions of Orbiter.
---------------------------------------------------------------
---------------------------------------------------------------
>>> ERROR: Could not load vessel module:
>>> [Vessel::LoadModule | .\Vessel.cpp | 5432]
---------------------------------------------------------------
---------------------------------------------------------------
>>> ERROR: Mayfly
>>> [Vessel::LoadModule | .\Vessel.cpp | 5433]
---------------------------------------------------------------
---------------------------------------------------------------
>>> ERROR: Could not load vessel module:
>>> [Vessel::LoadModule | .\Vessel.cpp | 5432]
---------------------------------------------------------------
---------------------------------------------------------------
>>> ERROR: Mayfly
>>> [Vessel::LoadModule | .\Vessel.cpp | 5433]
---------------------------------------------------------------
 
Yes, that's the landed smoke effect that comes with the DGIV.


Lol I have used the DGIV only twice and never noticed it had smoke effects. It's a good ship but I like flying the XR vessels personally.
 
The problem with the SMOKE_GEN modules is most likely that they were compiled in DEBUG mode rather than RELEASE mode, causing them to depend to rely on debug versions of their dependencies.

A quick recompile of the modules in RELEASE mode ought to fix it.

For now a download of MSVCR90D.dll should fix the problem temporarily: http://www.dll-files.com/dllindex/dll-files.shtml?msvcr90d
 
Last edited:
Back
Top