Assorted Add-On Questions

[XonE32]

Hey all, I didn't want to create a seperate thread for each of these add-ons as they're somewhat banal questions and shouldn't ellicit too complex a response. but with regard to...

IMFD 5.1m: You don't need an earlier version of IMFD installed for it to run is that correct? I took out all references to the earlier version before I put in 5.1m.
And in 5.1m does Tangential Transfer work? Whenever I switch to the Tangential Transfer page the IMFD display lines flicker all around and don't stop no matter what I put in for the settings. In fact I've never seen the Tangential Transfer page "stable" and "unmoving".

PreludeII Bases: Ya know how the pad has those cool blue lights flashing to the centre? Is that effect part of the .dll or can you make flashing-in-sequence lights without making a .dll?
In addition, is there a way to make a night texture for the pad? Or would I have to create another mesh that fits over the landing pad and has a night texture of it's own? I'm curious because I'd like to have the circular ring around the pad be lit at night if possible, but because the PreludeII is a vessel the whole process is causing me stress.

World Of 2001: Is there a reason, or more importantly a fix for the goofy changes in the animation state of certain animations on certain vessels? (e.g Clavius Dome or the landing gear on the Aries). For instance I'll be in the middle of landing phase in an Aries with gear up and do an external view and the gear is sort of down but not really without me having touched anything. If I hit G the gear goes up and pokes out the side of the ship lol. Sometimes the Clavius Dome gets "inverted" in the same sort of way when I switch vessels to open it and then switch back to the vessel I'm flying.


Any thoughts would be greatly appreciated and thanks in advance.

Cheers

XonE 32

 

[Bill LeClere]

me too!

I've never gotten anything but what you describe in tang. transfer in IMFD myself. Am looking forward to any replies that might help.


bill

 

[caningo]

IMFD 5.1m: You don't need an earlier version of IMFD installed for it to run is that correct? I took out all references to the earlier version before I put in 5.1m.
And in 5.1m does Tangential Transfer work? Whenever I switch to the Tangential Transfer page the IMFD display lines flicker all around and don't stop no matter what I put in for the settings. In fact I've never seen the Tangential Transfer page "stable" and "unmoving".

The 5.1m version works by itself. I have never been able to get the tangential intercept to work either. What I do is adjust the arrival and departure values in target intercept to get the Hohmann transfer. I assume Jarmo is addressing the issue.

 

[eveningsky339]

The tangential intercept program of IMFD 5.1m will not work properly if there is not a proper launch window. For example, if you want to perform a transfer to the Moon with this program, but you are 2 degrees out of plane, the program will not work.

As for the WO2001 problem, I recommend installing it on a clean install and checking to see if the animation problems persist.

 

[XonE32]

Ahh, ok. so I must be using Tang. Transfer incorrectly. I didn't know about the Out-of-Plane factor. Admittedly I'm not that familiar with it so I'll have another gander at the IMFD .PDFs.

Honestly the WO2001 "animation funkification" isn't that much of an issue, just a little irksome as it doesn't happen all of the time. Just curious if anyone else had seen it happen.

Thanks guys.


Any thoughts on the PreludeII things? ...anyone? ...Bueller.


-----Post Added-----


Anyone out there who has both WO2001 and IMFD 5.1m installed? And also has the "Aries at Prime Base" .scn located in the default WO2001 "Mercury" folder?

Just wondering if someone could run a test to see if you can setup a trip from Mercury to earth with that scenario while using IMFD5.1m.

Everytime I try and set it up I get an orbit eject burn time of around 5800 seconds, but it never makes it. The autoburn just stops after a while.

Can IMFD handle these long burn times? I thought if you set it to "realtime" it works, but I can't figure it.

Thanks in advance.

XonE 32

 

[sputnik]

The dome animation problem is a known issue; appears to be a spacecraft.dll issue, which is why we're thinking about writing our own .dll for v3.2.

But the Aries gear animation problem you're describing is new to me. Any idea what causes it? Or rather, is there any consistent way you can trigger it?

 

[XonE32]

Hey Sputnik, sorry I haven't checked this thread in a few days, but thanks for responding. I will now do further investigation. I can tell you for one thing it's intermittent. I would assume that me calling it intermittent is actually mislabeling, it just means that I haven't nailed down what I'm doing to cause it.

my assumptions (hate those) are that it has something to do with either time compression or view changes or vessel switching. I had only seen it in the "floyd's Journey" .scns because those are the ones I was playing with most, but then I tried the Mercury mission "Aries at Prime base" and saw it as I was attempting to dock with the Aquarius. It doesn't happen everytime. It is very remminiscent of the clavius dome issue. I'll run the scenarios and see if I can get it to recur and hopefully nail down the trigger. I'll also post a pic to show you what it looks like.

Thanks again for responding.

Cheers

XonE32


-----Post Added-----


OK, so I seem to have found the trigger in my install. I say my install because I'm not sure if it's WO2001 prob or if I've tinkered with something that causes it. If lots of people have WO2001 3.1 and haven't seen this happen that leads me to believe it's my tinkering.

Anyhoo with regard to the .scn "Aries at Prime Base" in the Mecury folder:
1) lift off and gear up goes fine.
2)The AriesIIc has 2 propellant sources correct? The trigger seems to be when the 2nd tank or the booster tank of LOX runs out.
3)During my ascent from Mercury the gear was up, but I switched to exterior view when the LOX ran out and got this:

Without having touched G you can see the gear is sort of downish lol. That seems to be the trigger for me. Prior to the LOX running out the ascent looked fine (ie. gear was up and not visible).

This is after I put the gear up and then down. You can see how it's "broken"

A little later I switched to exterior with the gear down and it looked fine:

Thinking that all was well again I put the gear up and got this:

It's all very strange. The only thing that I may have done that i can think off is I seem to remember changing a texture or two for 1 or a couple of the exhaust.dds. If you look at the first picture, should the exhaust flames be orange or not?

Any thoughts would be appreciated, thanks in advance.

Cheers

XonE32

 

[Urwumpe]

looks like a problem with the changed behavior of the animation definition. The initial state of a animation when defined can be different to the animation state in the mesh at a time.

 

[XonE32]

looks like a problem with the changed behavior of the animation definition. The initial state of a animation when defined can be different to the animation state in the mesh at a time.

LOL, thanks ...uhh I think Urwumpe. I honestly wish I knew more about this stuff so that statement would make more sense to me but I'm just a boob, or is it noob... perhaps both.

I wonder why it triggered (gear appeared half downish, 1st pic) when the LOX booster ran out though. That to me is the oddest thing. I ran the ascent from Mercury's Prime Base 3 times with the same result. The only difference is... I'm getting really good at lining up with the Aquarius in Orbit lol.

If I can confirm it's my install I'll go through the very arduous task of taking out WO2001 3.1 and reinstalling it, but I'd rather not if I can avoid it.

Cheers

XonE 32


Update: Well at least I can confirm what I figured, It's not WO2001. Luckily I had a backup of just the base Orbiter install. I put Wo2001 +WO2001 3.1 + the patch in that and ran the Mercury .scn and had no probs with the landing gear as the LOX ran out. It's not the newer contrail textures I had put in either as I put back the originals and got the same issue with my install. Unfortunately my install is packed with add-ons so I have no idea where to start lookin, guess I'll start with removing modules. What a pain.

Update 2: Bah, what a pain, but Eveningsky was right. I think I had wacked install of WO2001. I took all reference to it out of my install including the complimentary add-ons that can go with it. Seems like things are working fine know. I just have go through the scenarios and see if there's any issues, but I don't expect to see any probs.

Thanks all, It IS appreciated as this is one of my favs. To have it seemingly and most probably fixed is a great relief.

Cheers

XonE 32

 

[Tommy]

A few pointers on IMFD:

I think you can set up a tangential transfer while landed if you set the source (src button) to the body you are landed on. Then you can use Surface Launch mode to launch into an orbit that has less than 2 degrees of EIn. I could be wrong, and I'm not at home to test it, so try it.

"Realtime" mode is designed for shorter burns, and is used for mid course corrections. Use Prograde, Retrograde, or Velocity Frame modes for the transfer burn, depending on the type of transfer you are trying to do.

While IMFD 5.1m doesn't depend on an older version, it helps to download the "old" manual since it contains things left out of the later versions.

 

[TSPenguin]

Regarding the Prelude base:

I would think that you could attach your light ring (however you finaly do it) to the base.
If there is no suitable attachement point, I believe it is safe to add one to the config file. Not sure about this or if this will be erased by dll actions. Confirmation is needed.