Jump to content

Maulkin

Members
  • Posts

    733
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by Maulkin

  1. I have been following along with your pdf document and I must say it is very well formatted and concise. I did run into a bit of trouble however and I am not sure if I managed to misunderstand something, or if there is something I am trying to do that is not doable. I am trying to bind the "Tail Wheel Lock" system to JOY_BTN7 on my TM warthog such that when the switch is activated the tail wheel is locked and when it is not activated the tail wheel is unlocked. I have added the following code to the 'default.lua' in the Bf-109K-4: -- Sporn / Tail Wheel Lock { down = device_commands.Button_21, cockpit_device_id = devices.CONTROLS, value_down = 1.0, name = _('Tail Wheel Lock LOCKED'), category = _('Systems')}, { down = device_commands.Button_21, cockpit_device_id = devices.CONTROLS, value_down = 0.0, name = _('Tail Wheel Lock FREE'), category = _('Systems')}, { down = device_commands.Button_22, cockpit_device_id = devices.CONTROLS, value_down = 1.0, name = _('Tail Wheel Lock (toggle)'), category = _('Systems')}, { down = device_commands.Button_21, up = device_commands.Button_21, cockpit_device_id = devices.CONTROLS, value_down = 1.0, value_up = 1.0, name = _('Tail Wheel Lock 2-Pos On/Off'), category = _('Systems')}, The last line is the new one I have added. I then bound Button-7 on the TM Warthog Throttle to the new command "Tail Wheel Lock 2-Pos On/Off" In game I can verify that pressing the button will activate the tail wheel lock but releasing the button does not deactivate the tail wheel lock. It just leaves it on.
  2. I used CTRL-ENTER to monitor my input and it was rock steady
  3. Sadly it is pretty much unflyable in this state :(
  4. I would agree with the stalling but the way it oscillates is almost like a loose aileron flapping around and less like a stall. I confirmed that auto rudder is disabled, and take-off assistance, aileron trim and rudder trim are set to zero.
  5. It has been this way since day-1 but since it is no longer in a beta mode I figured I would report it now. Opening and closing the canopy is very choppy. To compare, you can see that the L-39, whose canopy also opens to the side, is animated very smoothly.
  6. I have been trying to learn how to dogfight in the Bf-109 and it has been a real struggle. It seems that I easily enter into a rolling oscillation (despite holding my controls steady) making it impossible to turn with a P-51D. I have been keeping my speed above 300km/h so I have no idea what I am doing wrong. It gets so bad at some points that I can get no response from the controls. Does anyone have some suggestions on what I am doing wrong?
  7. How do I install the eclair pod? I didn't see it in the armament list in the mission editor.
  8. Yeah thanks you are right. I was a work and had to guess. :)
  9. Chuck you might want to make some adjustments for the "Special modes" in regards to CCM. I was a bit confused when you say: "You can cycle through them using the SPECIAL MODES FWD/AFT controls on your HOTAS." It was my understanding that FWD would cycle through all modes, as would AFT, but in fact FWD will only cycle through the Horizontal modes (BA2 and BAH), and AFT will cycle through boresight and either Vertical or HUD-scan mode depending on if you have the 530D selected on the PCA. Also, Slide 38 should indicate there is a control for button 5 when depressed (which is to unlock I believe)
  10. This can be observed using the instant action mission "Takeoff". Start the aircraft in a roll and the polygons of the pilot will be flashing through 1st person view. The only way to mitigate this is to disable the pilot body (LSHIFT-P). I am using a single monitor view with 1920x1200 resolution.
  11. Hollowman, I got stuck on exactly the same thing. ;)
  12. Ah thanks! I though I had read in the documentation that FWD or AFT would cycle through all of the CCM modes, but now that I understand it this makes more sense.
  13. I am using build1.5.4.55584. I am able to toggle between the two horizontal scan modes (BA2 and BAH) using the "special modes FWD" button but it does not go to the boresight or vertical scan mode. But the "special modes AFT" will get to the boresight mode and something called 'SVI', but not to the BA2 or BAH horisontal scan modes. What is SVI? Is this the vertical scan mode? Where is the HUD symbology? Why doesn't the FWD and AFT buttons cycle through all of the modes?
  14. I retested this mission but had the target aircraft fly a perpendicular vector and the 530 missile does not do that nose dive manuver when the rocket engine shuts off. Only when I am flying a parallel course directly behind the target as I have in the mission file attached above. I think it is safe to say this is a bug and the thread could be moved into the "Bugs" section.
  15. Agreed but it is clear that the missile has plenty of kinetic energy remaining. As soon as the rocket engine on the missile shuts down the missile performs a nose dive into the ground. The mission file is attached. M-2000C A2A missle test.miz
  16. Does it happen every time or is here something I am doing that triggers it? Is there a way to make it not do this?
  17. The following test was performed on build1.5.4.55584: I have been trying to learn the new A2A missile functionality so I set up a small mission where an unarmed aircraft is flying straight ahead and away from me. Everything looks good and I have the aircraft just over 5nm ahead of me. I fire the missile and it appears to be tracking well but then suddenly the missile does a nose dive towards the ground. I have attached a track. I didnt submit this as a bug because I think I might be doing something wrong. If I am please let me know. Mirage strange 530D behavior.trk
  18. I thought there was a bug where changing the response curve would cause it to stop working completely. Sent from my SM-G935W8 using Tapatalk
  19. Yup same here
  20. I am getting ready for my PPL exam and thought I would experiment with what I have been studying regarding pressure and density altitude. I created a mission where I have a TF-51 sitting on the tarmac at Bselan, the ambient temperature is set to standard (15 degrees Celsius). I then set the altimeter to standard pressure (29.92) and confirm that the altimeter is indicating the pressure altitude of the airfield: 1772 feet. I then change the mission to set the ambient temperature to 25 degrees celsius, set the altimeter to 29.92 inches and the altimeter displays approx 1710 feet! It went down? The formula I have learned is this: density altitude = pressure altitude + (100' * [actual temp - {standard temp at sea level - standard temp at altitude}]) So this comes down to: DA = 1772 + (100 * [25 - {15 - ~3.4}]) DA = 1772 + (100 * [25 -11.6]) DA = 1172 + (100 * 13.4) DA = 1772 + 1340 DA = 3112 Shouldn't the altimeter display this? Or does this just mean the aircraft will perform as though it is operating at that altitude but the altimeter will not display it? In that case why does the altimeter go down when I increase the ambient temperature? I am using this as reference: http://www.langleyflyingschool.com/Pages/Flight+Operations--Pressure+and+Density+Altitude.html
  21. Yeah I agree that would be a nice touch. I also wish chocks were a standard for all DCS aircraft but mostl for the prop planes
  22. After bailing out of my Mig I waited until I floated down to the ground and discovered that there is no animation for walking. The pilot still moves around but he is stuck in the standing pose. I checked some of the other pilots in the other modules and they don't seem to have this problem.
  23. While I am not expecting the Hollywood-ish "ka-POW" I feel like I have lit off fireworks that made more sound. I'm wondering if it just might be me so I'll try to make a video and attach it.
  24. LOL I might have found the answer in the v1.2.7 changelog: http://www.digitalcombatsimulator.com/en/news/dcs_1_2_7_is_now_available/ More specifically this: So I guess the bug is that there are still default loadouts that contain these. :)
  25. It seems the only way I can get access to these rocket launchers is if I use a pre-existing loadout. If I try to righ-click on a station and select rockets I can only see LAU-131's and LAU-68's. Does anyone know why the LAU-61's are not on the list?
×
×
  • Create New...