Jump to content

itarrow

Members
 View Profile  See their activity

  • Posts

    144

  • Joined

  • Last visited

 Content Type 

Everything posted by itarrow

  1. itarrow
    I use Warthog HOTAS, no MFDs. I rebuilt the F14 profile by disabling (-1) MFDs and enabling (1) "comm menu by active station", and then I've tried it again in quick instant actions scenarios: Jester menu is more consistently responding (without shutting down without answers) but I still get the "Stick buttons... Done!" message on the Target GUI, even if less frequently. Could be because those last test were with quick instant actions while the previous were with long DCE Campaign missions... not sure... anyway Jester was answering more reliably. Not sure what I'm doing wrong anyway... maybe I'm building the F14 profile with some bad settings ? I will go through those again... Meanwhile if you have any suggestion about things I can do to get a better understanding about the issue feel free to chime in...
  2. itarrow
    Hey there, I'm getting weird behaviour from Jester menu: sometimes it becomes unresponsive or select different answers vs. what I've chosen/selected. I'm using VR, so moving my head to select menu input and then Jester AI (down on intercom throttle stick). Sometimes it works, sometimes (often) not. I'm using all latest luas, including june hotfix. A thing I've noticed is that compared to other modules, the Target GUI is cluttered with "Stick Buttons... Done!" messages when I end a F14 session with those Jester UI issues. Notice I don't have any other problem with other COMMS. Anyone else experiencing those issues ?
  3. itarrow
    There has been a misunderstanding: it was a 50% possibility of an increase in performance which happened to somebody and doesn't happened for somebody else as per the results thread.
  4. itarrow
    Never been able to get a feedback from tanker in that mission (short). Comm 1 or comm 2 doesn’t change outcome... in both cases no feedback at all from the tanker... (using easy comms, shouldn’t anyway change things)
  5. itarrow
    I've checked: the AV8B fuel probe switch doesn't work neither on the WH Throttle "RDR ALTM" switch (official docs) nor on the FUEL NOMR ENG L WH Throttle switch (jpg here on the first post). Using latest luas (AV8B wh 2.28 and AV8B 2.34 kb).
  6. itarrow
    Agreed on everything, at the end it is up to you. What's really good is that there's so many options, all finally at a really good quality level. I've enjoyed my Vive, but the Index gives a much better quality... I am playing a lot just thanks to that in this last few days... And I imagine it's the same or better for anybody trying the Oculus S or the Reverb or whatever it's your favorite one. Thinking back at when I bought F15 Strike Fighter on a ZX Spectrum and I was enjoying it...
  7. itarrow
    He never said real pilots do that. He said is a minor annoyance to who’s using VR. I’m not sure I understand what’s your goal here ? To explain us VR cultist in a VR forum why we shouldn’t have fun because obviously the only way to have fun is yours ? On a mission to convert VR gamers back to flat monitors ?
  8. itarrow
    One last thing (sorry about it): checked back the AV8B and the refueling probe switch on the WH throttle (rdr altm) doesn't work... can you check it ? Thanks again... EDIT: saw now that the layout jpg about the Harrier in first message of this thread is different from the one in the CTS docs folder. Here the refueling probe is in a different throttle switch, while on the one I was trying there’s anticollision lights. Will test according to the layout in the first message here and report back if everything works OK according to it (meaning the jpg in the docs folder of CTS are outdated).
  9. itarrow
    “Unplayable” in this case seems to be quite subjective. I can read everything with the Index, so not sure what makes it unplayable. Of course I understand everything is clearer on a 4K monitor, anyway to me it would be “unplayable” watching a screen and pretending that I am flying, now that I have tried VR (and it was the same with the original Vive). As both of us are playing what is “unplayable” for each other, it seems that everybody can play what others define as unplayable. So it’s playable.
  10. itarrow
    After experimenting a bit more with the Index (mainly DCS and Elite Dangerous) I suggest everyone experiencing god rays to try to move a bit the headset around to find the best possible fit. Yesterday I suddenly realized what a “sweet spot” is after placing my headset a bit higher on my cheeks than what I was used to with the Vive, and everything got clearer and sharper and no god rays anymore.
  11. itarrow
    Mine arrived today, did some quick testing vs my previous set (original Vive). Readability is much better, SDE is no longer noticeable, FoV doesn’t seem this big jump probably because I was expecting too much, sound is superb, confort is much better. What I was not expecting is a big improvement in colors, which seems to me quite more vivid vs the OG Vive. And even black seems better that the grey noise I was getting with the OG Vive. Bah. At PD of 1.3 (in game) DCS seems a new game. Will provide further results if I am able to use it a bit more (here in northern Italy is quite hot now... using a headset is not really a nice experience at the moment...).
  12. itarrow
    Well, there's no way you have to say sorry about something you do so well for the community and for free. Thanks for what you do and keep doing so well.
  13. itarrow
    Here it is (added .txt extension so to upload it), thanks for looking into it. DCS_World.tmc.txt
  14. itarrow
    Second that... can't fly missions with wingmen as well as DCE campaign since 2 weeks now... I went back to the F18 so I'm still getting my DCS weekly dose, anyway I am really missing my F14...
  15. itarrow
    I've updated to the new lua profiles (2.34) both for kb as well as WH, VAICOM is not enabled. Checked also modifiers are still there (and they are). Did some further testing without success, even after setting MFDs as -1 (it says to try it just for troubleshooting, so gave it a try). I've discovered also that the speedbrake doesn't work with 2.34. Reverting back to 2.33 F14 luas makes everything works again: comms menu appears as soon as I push comm hat left or right and speedbrakes correctly deploys/retreat. Not sure what else to try... I will stick to 2.33 and see if I can came up with a solution... suggestions welcome of course...
  16. itarrow
    Just tried it (F14): suddenly the "comm hat" on the Warthog throttle works just for Jester... Left or right presses don't bring out the Comms menu... Probably did something wrong, anyway a quick check for the usual errors didn't brought up any glaring misstep in updating... So here I am writing here to check if anybody else experienced same issue or if it's really just me... UPDATE: reverting back to 2.33 solves the issue, so it seems that Comms menu disappearing is just a 2.34 thing... Anybody else with the same isse ? Because if nobody else has it, I'm really struggling to understand what's the problem on my side...
  17. itarrow
    Issue still here after today’s update.
  18. itarrow
    Tried after today's update, issue is still there.
  19. itarrow
    Tried that (deleting stuff in the front of the carrier) so to have my wingman take off but nothing changed. Will try again by removing everything and see what happens. I am talking about Tomcat over Caucasus.
  20. itarrow
    Hey there, is the Stennis TACAN still 74X ? Can't get it to work with the “old” 74X (compass keep rotating) and I don’t know where to get the info (tried on the mission planner before the mission but TACAN is not there, nor in the mission briefing or in kneeboard)... EDIT/UPDATE: found the info, is in the campaign summary... Stennis TACAN is now 37X while Vinson is 38X
  21. itarrow
    Didn't thought about it, I will try it and see if there's anything meaningful I can gather... Thanks !
  22. itarrow
    Thought about using Nvidia stuff, problem is I'd like to see what happens outside. I am on slope, AoA is OK (or at least I see a circle), everything seems OK, however when I try an instant action/training mission I always land, while when I came back after a long DCE mission I'm literally unable to catch any wire. Sounds so weird that I want to check, and in the cockpit everything seems OK.... So I need to check from outside... Anyway if there is no possibility, I will get back to the Tomcat and stick with it .. at least with it I can reliably land both in training missions as well as after a DCE Campaign mission...
  23. itarrow
    Hey there, I am struggling with carrier landing with the F18. I am doing fine in training missions, however when I fly in DCE campaign missions I become the bolter champion: even if everything seems fine, I miss the wires and have to redo till when I quit out of frustration. I would like to see what's wrong, problem is that a reply with the usual track file of a similar (long) mission would be too long and my aircraft would anyway crash before (as I often fly low). Short missions as said are not a problem. So is there any way to get a proper reply of the last few minutes of a 1 or 2 hours mission ?
  24. itarrow
    No problems, especially after last updates with the prune utility. Try it !
  25. itarrow
    Unfortunately so far I wasn't able to reproduce it consistently... not sure how this issue kicks in. I've done some simple instant action scenarios and I never got problems. I've got it in a couple of DCE Campaign missions I did previously (which usually take longer that an instant action), so when I will have time I will see if it happens by doing a DCE Campaign mission again...
×
×
  • Create New...