Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
https://gtm.steamproxy.vip/workshop/filedetails/?id=1754405903
First of all, it is looking awesome and I am very excited for your future builds. All doe, I am still figuering out, how to attach the harness's. Could you help me on that?
In regards to your question about building extra modules. Absolutely feel free to go ahead. I have no misgivings about anyone pulling apart, enhancing or reusing anything I build.
And regarding the water tanks you added, can I build some extra modules for the chopper?
In regards to the water tanks I just have one and its mount dead centre under the rotor. Adding any more could mean pushing it to the sides or back/front which may through the balance off. I found that I had more then enough water to deal with a single source fire and could put out about 4 fires on the Rig before having to get more. With that in mind I'm a hesitant to throw on another tank. However I had played with rigging up some optional water tanks that were mounted on the rails in the cargo bay. That's why I put the electrical and Fuel/Water Connector in the bay. I may revisit that.
In terms of the Cross Connect it appears to be working as per design. The Cross connect is just a single valve between the fluid inputs in to the Engines that when open connects them together. When It is closed each engine should "sip" from it's own tank only. When open they will draw from both tanks.
Both Jets are entirely symmetrical (i.e. same PID values for maintaining Combustion RPS, same hookups) and ideally should work the same. Where I think the imbalance is happening is that the output to the rotors is a single channel and I combine the power of both Jets together by using a T connector. The RPS going to the main Rotor (combined Jets) drives the Required Combustion RPS which are individually calculated using PIDs for each jet. What I think is happening is that the Port Jet Combustion RPS calculations are happening before the SB Jet. As a result the Port Jet may be ramping up faster. The SB calculations then determine it doesn't have to run as hard as the Port may have already upped the RPS on the Main Rotor. This is all just speculation but would seem to make sense.
The system on the GRYPHON is based off the HERMES where I have a variable available per memory slot where you can set bits to represent a condition for the WP. I'm thinking it's a matter of defining that a bit set on a WP will indicate it is only a node in a path. The chopper would then continue on to the next point after it reaches the current WP. Just like the HERMES you need to specific a "Last Leg" bit to tell the vehicle that after the next WP it will turn off AP. Just need to find the time to do it. Spring has sprung and lots of stuff on my "honey do" list. :)
I'd like to build something that corrects for those movements in all directions... that's where the heavy math comes in. GPS X/Y/Z hold tied to movement in three directions with pitch, yaw and roll changes... may have to find my old Applied Math books from University and reacquaint myself with Matrix mathematics.