I wonder how the two would work together. How does OG deduce fuel usage in a vessel that have unlimited fuel and arbitrary fuel tank linking?
Orbiter Galaxy is pretty limited in those capabilities and relies on the user using standard tools like TransX or the Orbiter Navigator for the arrival burn. All Orbiter Galaxy gives is a vector and a burntime for the ejection burn based on the current engine specs and fuel supply, plus the option to specify a percentage of the propellant as fuel reserve. Once arrived at the new system it gives a rough estimate of the time to start the burn, also deduced from the engine specs, velocity, and propellant reserve.
Since at relativistic speeds a few hours can mean the difference between succesfull injection, overshooting and drifting out into open space or falling short a few deca-AUs carefull planning of the arrival burn with a more sophisticated tool is mandatory. TransX has a problem in that it has a limited maximum delta-v to plan in one go. The Navigator works exceptionally well, but does so exactly because it takes mass-decrease by propellant expenditure into account, and calculates with fixed full thrust. I'll have to see how the Hius performs with those, but my first guess it that it won't work too well (no mass decrease, and variable thrust).
And what the hell is wrong with that texture generator...
I'll be damned if I know...
Ok maybe a little bit off topic, but is it really possible to fly directly to a star (without jumping) by using orbiter galaxy? And is it possible to insert one of this star systems developed by orbinauts to orbiter galaxy?
Both are certainly possible and well documented in the manual (there's even a whole seperate manual in the download that describes how to add a custom system). Allthough I'm yet waiting to see the first custom systems supporting orbiter galaxy, noone has made a compatible release yet. Adding a system just to target it is just a config file with a few lines, but to get the system to display in Orbiter Galaxy's system overview is a bit more work, depending on how much of the data you want to provide...
Seeing WHERE you are pointing at.
That is pretty easy in Orbiter Galaxy, thanks to Jarmonics code for the Vector view.