- Joined
- Apr 14, 2012
- Messages
- 2,585
- Reaction score
- 0
- Points
- 36
The easy way: scenario editor. (consumables are actually handled as propellant resources, so you have access to them via ScenEdit).
The realistic way: dock any full cargo module, punch up the transfer MFC and transfer the cargo over to your vessel.
Thanks, I suspected that, but I wasnt sure. Its a better method, but Im used to coding resources internally so that users cant cheat by pumping fuel via an MFD :lol:
Sure, we have the VASIMR![]()
:facepalm:
I actually never use the VASIMIR, since it sounds a lot like the real thing may never arrive. It ultimately looks like Ion & Nuclear Thermal are the only real options for the foreseable future I guess. (I also wouldnt have the patience to fly at milligees either)
That is a wrong assumption. Those projects slid into obscurity because they were, at their very core, an evil hack. Orbiter Galaxy isn't really complex... It's interaction with Orbiter itself minimal, wherein lies one of its major grievances. It's just too clumsy and slow, despite Artlav ramping up the texture export to incredible speeds (provided you have the hardware).
Orulex's problem, and the OGLA client's problem in extension, was that terrain collision detection never worked out. It just couldn't be made to work in an acceptable way, so it wasn't used.
Orbiter Galaxy's problem is that textures have to be exported completely before loading a new system.
Both could be solved by terrain and texture LOD support by the orbiter core. The Doctor is at least working on the first, as far as I'm aware.
I dont know if its fair to call it an evil hack, the final Orulex combination is actually fairly stable. All the same though, projects like this do seem to suffer for the lack of experienced programmers available to work on it. At the moment, youre busy with RL, Im just working my way up in terms of experience, & we have PeterRoss working on the source code. Its tough to do projects like this because its just so much work to accomplish in spare time :shrug:
Speaking of the source, can you post that soon PeterRoss? I would like to set that up on my end soon.
Page 24/144. Working on more logical operators. Hopefully I can get most of them copied down by the end of today.
You keep mentioning terrain in the next Orbiter version, I thought we were actually getting farther away from that, no? Maybe I missed an announcement somewhere.
Uh... In fact, you can't use RCS before you power up the control module. You need your computer running to control all the systems. You can only attach and integrate when command modle is offline.
---------- Post added at 23:26 ---------- Previous post was at 23:17 ----------
As Jedidia said, you have no LOX_LH2 tank to fuel your RCS. Preview pictures contain some vital information needed to use modules. All RCS modules are using LOX_LH2.
Yep, CM is one of your first priorities, and LOX/LH2 is needed for RCS. That being said, I should probably create some more realistic RCS parts using more conventional fuels. I guess you could use LOX/LH2 for attitude control, but Ive never heard of it being done before.
Sorry for bombarding this thread with my questions... ._.
No, not at all :thumbup:. Its good to get some more activity around here.
I'm finding it rather hard to read through the guide (the link on the first thread), as its like a cobbled up wall of text that makes it a bit hard for me to pick out which requirements does my craft need. .-.
Im getting there eventually, but the documentation wont be ready for another week or two at least. Hang in there
Just wanted to leave this here, & pick up my prize for the strangest looking IMS ship so far

, but happly IMS doen't give a damn about fuel specs, you can define whatever you want in config file later.