

jumphigh
Members-
Posts
83 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Everything posted by jumphigh
-
Unfortunately, I mixed it up with the "Pylons On/Off"-mod. This is a skin you can apply freely. But the FBI agent or the medevac kit are loadouts, provided by a tech mod. I wasn't able to change these loadouts on FARPs or airbases via rearming menu like you can do with regular arms armament. With the latest DCS update you can load cargo into the chopper and now you can see it inside! The agent or the infantery group are now loadable via the cargo UI. But it is rendered as (packed into a) crate/box inside the Huey. So it seems to get this special "armament" you still need the mission editor. And you can't change it during a mission without losing its genuine appearance.
-
To answer myself: Similar requests for rearming/refuelling via script exist since 2017 – obviously unfilled? So I guess it remains a dream. Maybe till the introduction of the dynamic campaign core.
-
A player could load the passenger with a skin change via the rearm/refuel menu. But nobody mentioned the possibility to change skins via LUA script. I bet it isn't possible at the moment because otherwise all the talented mission designers out there would have used it in connection with the CTLD script suite? But it seems a way for the developers to easily add visible troop loading on a short term. Just introduce a LUA binding to the API the skin change functionality of the rearm menu relies on!
-
Aside from door gunners no one is ever shown in the back of the Huey. You don't see embarking troops. At the moment DCS doesn't support transport tasks with visual troops or cargo inside the airframe. The community provided custom skins with modelled persons in the back but that is a static effect. It is as bad as the normal behaviour – only the other way round. These static models remain visible when the (logical) troops are commanded to disembark. I don't know if these skins can be changed between an empty chopper and a crowded one in flight.
-
I see it now. This part isn't missing if the door is undamaged,so @yeti submitted a valid bug. But description could be better. I wouldn't call it a different pattern, a whole texture segment is missing instead.
-
Where do you see differences? I bet there is only one window texture, regardless if you're looking into the Huey or from the inside out.
-
As a German I would say neither nor. It seems to be a "Fugen-s" (linking element s) to ease pronunciation.
-
The Steam version has the module manager, too? That's the place where you enable or disable modules. No need to clean and reinstall DCS from scratch.
-
Some demo recording on YT.
- 119 replies
-
- 3
-
-
-
Please have a look there. I enhanced the strobe function and estimated suitable strobe placements on the tail fin of a Blackhawk. Looks way better than the default strobe above the rotor head. Use "{x = -10.3, y = 2.15, z = 0}" as new (last) function parameter. And "{x = -6.85, y = 1.80, z = 0.14}" is a suitable placement for the Kiowa's fin. But of course you can still use the old default placement.
- 119 replies
-
We've already talked in the Kiowa campaign thread. I promised to enhance your strobes. Here it is including a short demo mission for Huey, Gazelle or Kiowa. I took your WirtsTools version 2.1.5 as base file from your GitLab. Please excuse me but I had to run a formatter on the whole file so instead of a short diff I deliver a complete new file. But I only made real changes in the strobe related parts. With the help of the model viewer I estimated suitable coordinates on the tail fin of the Blackhawk and the Kiowa to attach our strobes. You'll see it in the mission and I noted it as examples of the ToogleStrobe function. Looks way better than the default strobe in the air above a unit. Some demo recording on YT. PS: The AI Blackhawk does not land in the mission – ignoring it's last waypoint of type "Land". WHY??? WirtsTools.lua IRStrobeDemo.miz
-
I had already a look into your code and figured out that you use a short laser beam available through the Spot class. You could enhance your WT.strobe.toggleStrobe function with two (optional) vectors for base point shift and direction/length of beam. Looks quite easy with the help of the unit's position. I'll try it and give you a diff as a pull request in your script thread. But what's about the built-in IR strobes? I know the Huey to have a IR position light that is invisible to the human eye and thus dedicated to NVG at low light missions. I don't know if it's working in the Huey module. And I don't know if AI units like the Blackhawk are modelled with such a (usable) light as well.
- 119 replies
-
- 1
-
-
I saw the mission video on YT and thought: WTF, the IR strobe is hanging above the main rotor of the Blackhawk? Now I know it is not wrong modelling but a generic script add-on. There isn't a possibility to shift the strobe placement to a suitable place on the model?
- 119 replies
-
To dangerous! Looking that way she could grip the wrong stick...
-
That's why he looks so angry... I just wanted to clarify that it is different to planes where the co-pilot or WSO is commonly subordinated to the pilot (captain, pilot in command PIC), isn't it? Interestingly UK's Apache crews have the same roles like the PAH. The front seat WSO is the commander. US Army Apache crews however seems to use the expected order with pilot as commander, WSO subordinated. Does anybody know who is who in a Tiger? I know that the pilot sits in the lower front seat and the WSO in the upper rear. But who is the aircraft commander?
-
PAH has no co-pilot! The left seater is the commander of the aircraft and employs the weapons. The right seater pilot is in fact subordinated and not the boss.
-
Because cyclic stick position matters! Auto hover does not disconnect flight controls. It only can adjust pilot's inputs in the range of the stabilization system. So if you move cyclic out of principal hover position auto hover can't move the swash plate back enough and hover will break. You always have to trim your stick – or hold it – to a near manual hover position!
-
What do the question marks in the control settings mean?
jumphigh replied to ASW's topic in Bugs and Problems
Right, but why is there such an error marking in the Gazelle for e.g. active pause? I never changed the key assignment, neither in the global UI section nor inside general section of the SA342 module. Both are set to the standard Win + Pause. So there is no conflict at all, but I have the exclamation mark from day one of installation of this module. It's the SA342, all other modules never show such small problems. But I don't care, since it works anyway, regardless of the red sign. -
Auto-Hover without auto-rotation to the left?
jumphigh replied to trimmermedal833's topic in SA-342M Gazelle
Auto-hover holds within the range of stick movements of a manual hover. So your static input needs to stay close to the holding point. You have to trim your stick if it returns to centre due to the spring load. -
What do the question marks in the control settings mean?
jumphigh replied to ASW's topic in Bugs and Problems
Are you meaning the exclamation marks? If you hover above, it tells you what is wrong. Most cases refer to a collision of function or assignment. But I'm in doubt if we can solve a function collision. In my opinion there shouldn't be such a warning with a module freshly installed from stock. -
It is the Liveries folder inside of your Saved Games\DCS! There you have to put the three Cockpit_SA342x folders.
-
Can you fix your server please? The link to the mission file uses unencrypted http which leads to a security warning in Firefox (unencrypted content on an encrypted page). If I modify the link myself to https I encounter an invalid server certificate because the presented subject is a weird name instead of gamesfromhell.com.
-
Already posted on this forum:
-
Textures with different level of details in Huey cockpit?
jumphigh replied to lwalter's topic in DCS: UH-1H
AFAIK cockpit resolution setting is only for MFD rendering, not the whole pit.