Jump to content

Cruiser18

Members
  • Posts

    213
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by Cruiser18

  1. I have the Virpil TM-50 throttle, first generation. The red flip cover has two states; Open and closed. The throttle is programmable so it can interpret a switch in state as a button click, but you can also tell it that the open state is like a button being held down all the time.
  2. I just tried it myself using the brake handle on my TM50 stick. The jet brakes just fine using the brake axis, but the brake indicator in the CTRL+ENTER control surfaces interface does not reflect the axis inputs. Using my left and right wheel brake on my rudder pedals shows up normally and also brakes the jet.
  3. I experienced this issue as well yesterday in MP on supercarrier. Was told that flight was delayed. When I got a slot I found that the jet took a huge amount of engine power to get rolling. The others made fun of me and asked if I had remembered to remove the parking brake. XD
  4. I experience the same issue. Using the ground radar reduces my FPS to 2 until I turn off the ground radar.
  5. This actually happened to me yesterday as well on a MP server, at the end of a rather long flight where I had just refueled from a tanker. Shortly after that, I went on course for my homestretch but then my pilot just suddenly started seeing more and more double and blacked out with 20 seconds. I had to quite the server because the plane kept staying at altitude, event without autopilot on. My working theory was that I had somehow run out of available o2, even though I've never tried that on any other module.
  6. I believe in a way that this has been related to the issue that I experienced with the targeting pod which is now solved. The issue was that the slider axis on my Virpil TM-50 throttle was "jittering" which gave the targeting pod the impression that I kept changing the zoom levels which caused it to stay out of focus. Now fixing that issue, also meant that this issue is now fixed, so when I put a SPI on the ground it stays there. HOWEVER, I did a small experiment where I put a SPI on the ground and then moved the jets attitude up and down while changing the radar attitude as well. Doing this will move the SPI. I am fairly certain that it is not a feature of the JF-17 to have the SPI move when you move the radar azimuth and the jet at the same time.
  7. Alright, that was the issue. It was the thumb stick slider axis on the Virpil TM-50 throttle that was the issue because it kept sending small jitters which the JF-17 enterpreted as a change in zoom. I've applied a dynamic deadzone to the axis now through their setup software, and now the targeting pod properly focuses. Thank you for your inputs everyone. :)
  8. Huh, interesting. If that is the case, then it is highly likely that it is my axis that is the cause. I use a Virpil MT-50 throttle and it's not uncommon for the axis to create "jitters" because they are so fine-grained. In other air frames I have not had trouble of this kind before, but they also don't pull double duty on the controls this way. I'm gonna have a look into this after work. It might be the cause of my issue with the HUD SPI as well.
  9. I do have a axis I use for radar elevation, but I'm not under impression that I use it for zooming on the targeting pod? I'm gonna have a look at that bind after work and see if it also works as a zoom for the targeting pod.
  10. Well thats the whole issue. It's like its moving the SPI while I'm moving the plane. Check the video and see if I'm doing something wrong.
  11. I set the SPI at fairly close range, 3.5 NM according to the HUD. Also, the NM decreases and increases with the attitude of the plane, as if it's moving the SPI away and closer when I pitch the plane up and down respectivly.
  12. On the pod? No, only a button to switch between near and far.
  13. *Edit* Issue has been fixed. See post #11. I am experiencing an issue with the targeting pod where it is always out of focus whenever the targeting pod is SOI. Here's a small video that demonstrates the issue. Notice that the pod goes out of focus every time it is made SOI and immediately regains focus when it is not SOI. This issue also occured all the time before today's patch.
  14. No slewing is taking place. I'm simply planting the SPI on the ground in front of me and then it wobbles around with the plane. I've updated the first post with a direct link to the video with the issue.
  15. I am having an issue that also happens to me even before todays patch. When I set the HUD as SOI and set a SPI, that SPI will move with the planes attitude while the HUD is SOI. As soon as another SOI is selected, the SPI will stay in place, which I believe is what would usually be intended. I recorded a small video of this issue (ignore the first 15 seconds of me not remembering how to reset the SPI) (Here's a link to the video as well, since the player doesn't seem to be able to handle it.)
  16. Oh. That might have been the problem then. Will have to check it out. Thank you. ^^
  17. I was sitting and learning the JF-17 and trying my hand at the AUTO bombing mode (CCRP), and I found that I couldn't get the SPI marker to lock a target while the HUD was SOI. Chuck's guide states that TDC 5 press should lock the target, but what it seems to do now is switch back and forth between having the next waypoint as SPI or the manual SPI selector diamond on the HUD. After quite a while of messing around, I found that I could get the SPI to stay on a target, if I deselected the HUD as SOI. I have not found any reporting a bug on this or any kind of documentation that this is intentional. Does anyone know?
  18. Good to hear. I ran into the same bug yesterday.
  19. Hello. I'm running version 2.5.5 (before they broke everything), but yeah I'm pretty sure I let VAICOM update itself to latest version. I will try rolling it back and see what happens. Thank you. :)
  20. Installing VAICOM PRO seems to have broken my DCS a bit. Whenever I start a mission, I no longer see a mission briefing like I used to, even though the game is paused. I no longer see any text whenever AWACS or my wingmen communicate with me, despite having specifically selected that I want to see text in the game. I've tried resetting the settings and the LUA file and restarting DCS, but I still will not work. *Edit* Tried running repair on DCS. I had it throw away the changed Common and speech .LUA files. Now DCS works normally again. Reinstalled VAICOM and the problem instantly appears again where VAICOM ignores my chosen option settings. :(
  21. Chucks guides are definitely the best go-to source for getting up to speed on a plane. He covers most of the features without too much explanation or mincing words and usually keeps them up to date. His guide for the Viggen should get you well up and running. Looking for Viggen tutorials on youtube is also a good source for show-and-tell.
  22. Its been a while since I took off in the BF-109, but here's the things that I remember: Turn off take-off assist. You'll fight the computer for control, which is not something you want in a plane that is as finicky as the BF-109 on takeoff. Make sure the tail wheel is locked. Thats when it is pushed forward and latched down. Set the down trim wheel to about 1-2. Helps keeping you on the runway and build up speed before you really want to take off. Dont go full power from the start. The torque can send you all over the place. Get yourself rolling and settled and then slowly increase the throttle to takeoff levels. I seem to remember something about using a bit of right stick as well to counter the propeller torque, but I might be mistaken. Oh and raising the seat to get a better view over the nose is also nice. Not quite as crucial as in the FW-190, but still a nice to have in my experience. It take a lot of practice to get this plane off the ground in a somewhat competent looking manner, so just keep at it. :)
  23. Weird. I tried the mission over twice and nothing happened either time...Maybe I should take a look at the mission in the editor, see what triggers are set up.
  24. I'm having trouble with the navigation training mission, the trigger that should set off at WP 1 is not firing. I do as instructed, I take off, go gear up, set to nav mode and climb to 10.000 feet and head towards waypoint 1 (not that far away) but despite flying over waypoint 1 several times at over 10.000 feet, nothing more happens.
  25. Have you turned up the volume for your radio?
×
×
  • Create New...