Search results

igel submitted a new addon: VM package release 2021.04.19 - VesselM, Historical Spaceports, R-9, First in Space, Vostok, Soyuz, Proton, Collectors Read more about this addon...

By multiple requests, this is a re-upload of my VesselM-based package of related addons: Historical Spaceports R-9 First in Space Vostok, Soyuz Proton Collectors Addition Includes versions for both Orbiter 2010 and 2016 (due to some unavoidable breaking changes in 2016, older 2010 version is...

I'll try to find some time to pack all zips into one zip (two times, for both versions) and upload them... guess upload process has also changed... This may also loose some extra info that was on Hangar page, but I'll see what I can do. But not soon, not maybe within a few weeks. It all will...

Oh, then I don't know how to solve it easily... These addons are all about "multiple files" but packaged "closer together" to provide installation flexibility without mixing them up. Uploading them separately into individual "addons" will be a tremendous effort leading to tremendous confusion...

Sorry, I have not been on this site for a couple of years. On a quick look, it seems that something has changed on OrbitHangar. The link in the original package post (both for 2010 and 2016 versions) points to just one randomly selected zip file. When I uploaded them, this was indeed a "package"...

Hm. Very very strange... What do you have for second elevation-related option? This one: For some reason (don't remember what was happening) it did not work with other settings of this dropdown. I can't check it myself at the moment, not till weekend at least...

For Soyuz (from Common VesselM Features - v0.8b.pdf manual):

Yea, not many secrets left from that time by now...

Not really flight testing - by then Soyuz was well reliable and operational, so it happened as a huge surprise to everyone :-). Could not be hidden because it happened right in the middle of APAS preparations, lots of Americans around :-). I asked Makarov about his experience the very first time...

:) :):) If all problems could be solved that easily... Glad for you, have fun with 18-1! That was one hell of a flight!

...and what is the difference between 'default' mission file (from 7K, I guess) and yours? What are you trying to change? If one works, and another does not, maybe that's where it hides...

Here are a few hints on progressive troubleshooting: to open some stock Soyuz scenario (better the one not using ISS, to verify Soyuz is installed properly); to copy Soyuz 18-1 scenario and replace 3rd-party payload (7K) with TMA from Soyuz addon (this will verify that mission is defined...

Can you post the mission record from SoyuzMissions7KT.cfg file?

Just to verify - you use Soyuz 1.2 version, not 1.3?

Hi diogom, Your method, though not optimum, seems done correctly. Should have worked. Not sure what fails, but with so many indirects, it may be as easy as a typo in some file. Try a cleaner way - same way scenarios in "5. Custom Missions Demo" folder are done: do not modify any files or...

Good news, thanks! I'll also now be more cautious with new releases, knowing they are directly used in other popular addons. With such mass of code and files, I long ago rely on automated testing, and it mostly keeps quality at pretty good. But even automation won't help if there is no test case...

Great! Just to help you with the future iterations: Soyuz and Proton both support a way to fully separate dependent customizing addons into alternative folders. See supplied "Custom Missions Demo" scenarios in Soyuz on how it is done. Not only for textures or meshes, but even for the Missions...

I see. These are Soyuz 7K scenarios. To verify that Soyuz launcher itself is installed OK and works, use pure Soyuz scenarios - best are "1. Soyuz TMA to ISS and back" if you have added ISS, or "2. Soyuz TMA emergencies" if no ISS. But I'll throw in one more idea - the order of addons...

How is it "not working"? Crashing? In which scenario? This log i not telling much , unfortunately. All these "not cataloged" errors are not important: I think Orbiter 2016 simply complains that 2010 bases are defined not quite exactly the way it expects, but it is not a show-stopper in any way...

Soyuz\_Baser error comes from a small addon packaging error (to be fixed in future release). This happens only in one supplied scenario, "Soyuz Static Exhibition". To fix in current deployment, replace "spaceports_Traveller:Soyuz\_Baser" line in scenario with...