Jyge

What about mission 13? I formed up, but there was no guidance afterwards. I refuelled, but did not get quite to the top before disconnect, so I was just thinking that I did not activate some trigger and tried frustrated to connect again and refuel to the full until the mission timeline was utterly screwed. Is there then no acknowledgement and further instructions, just take some fuel and truck on?

Yeah, well the thing is. I am not 100% sure whether the notice is coming from Jester or the wingman, but if Jester reports a contact, I would really expect him have set-up the TID so that it is visible on it, where did he get it otherwise...also the contact reports, at least on an otherwise empty sky, coming from Wingman or AWACS should get some sort of attention from the dude, I think any normal RIO would look and see what the hell they are talking about...I think it difficult to see where Jester is paying attention to (if paying attention at all, except for his bong). Sure I am jumping back and forth between the seats, although setting up the TID on the backseat does not help anything, once jumping back front Jester goes back to the planetary scale. I hope there will be something in the near future updates, particularly knowing that the Phantom should be coming, I would expect a little bit more proof of concept style attention to F-14. I think the soft-lock and adjusting TWS accordingly would be a good start. I mean if the contact is at 40 miles, there is no reason to keep 200 miles scale on TID, sure, you can take a peek and that would be ok, but the main time should now be spent at 50 nm scale, that's I guess what a human RIO would do.

The problem is that Youtube is full of AWG-9 tutorials - some are good, but most were done before feature complete or whatever and at the moment I have hard time figuring what switch actually does a darn thing. I have real problems seeing/finding anything from RIO seat - I think current campaign (fear the bones) I am flying is F-14A - whether that makes a difference or not... From what I figure, going towards AWACS given contact and zeroing azimuth and elevation should give me something. There is only then the aspect switch, but mostly I see nada. Then comes the Jester from front seat. I always seem to get some astronomical scale on TID, again see damn all, even in the case I get a contact notification from him. I would expect him to set the TID range and all the stuff so that I see what he sees, but no. Then I do not seem to have an option to request a "soft lock" that I could get range and stuff from a contact, there is only STT option there. I have found exactly zero Youtube tutorials for AWG-9 from front seat where it is shown how to work with Jester so that there is even a trace of teamwork. I had a break of at least 1 year from F-14, flew couple of Hornet campaigns in between and I have now a feeling that I am starting from 0 again, but at the same time, I have a feeling that nothing has really developed in the radar and Jester during this time. I do not want to compain about tools, I really need to improve my skills, but I just can not figure out a place to start. I guess what I am looking for is a 1 min tutorial from Crash where he gets Jester to do what he should do and then tells everyone to eff off. I am dying of old age before Grim Reapers videos come close to making some useful point and even their tutorials are heavily dated and haven't really aged gracefully. They are not like watching a paint dry, they are like watching an expired paint dry.

Yes, I certainly put in the "W" - but it is good to know that it works, then the error must have been something else...

I made a small training mission on Nevada map for SLAM. I am now trying to give target coordinates in PP Mode and stupidly Tonopa ist W116 something. When I try to type that in UFC I get an error. It does not seem to accept the third digit on longitude degrees. How do I manage this...?

I am flying F/A-18 with VR and I am having some trouble with HMD Symbols. Firstly, the D/L Symbols for friendly aircraft, scarcely overlap with the aircraft. I have been watching some youtube tutorials and the tubers do not seem to be having this problem. My HMD symbols are also rather jumpy, so I think it is some sort of VR tracking issue. Also TGP Diamond has similar problems. In A/A radar lock and that kind of stuff is spot on. I also have some problems with precise targeting using the HMD in VR. I tried the alignment (on a shipdeck) but somehow it does not even accept the click on the crosses. I think it should go to the finer alignment once I press the button, but it does not do anything - I figure it is due to the problem that even here I have small vibrations on the cross position. I do not have parkinson by the way. Maybe the VR projection is done somewhere there on the HUD, so the leverarm is much longer as in the real helmet just in front of the eye and that makes out these fine tremors? Anybody else experiencing the same?

Ok, I did some experimenting around. It is rather weird or ackward and at the same time, at least the youtube tutorial I looked is a bit dated. The video said that you can not slew once in area or point track (or maybe that's litening - I experimented with ATFLIR) You can designate a waypoint as SPI in that you assign it as a target. If you designate somewhere else you can return here by activating TGT again on SA... It is, however, strange. If you don't depress the TDC once, you will return here when shuffling through area and point, which is a bit nerving (maybe). Otherwise you'll remain ground stabilized and the caret moves on HUD. You need to make the markpoint over SA or HSI and select that in the SA, which might require some shuffling... It is a bit nerving that I can not "hook" on markpoint on SA or anywhere, I need to use the up and down buttons and designate it as TGT. Is there a less clunky way of doing this or a good tutorial more to the point. Like something from "Laobi", carnage with the pod in a minute and eff off.

I am somewhat more adapted to A-10C logic and the whole logic in F/A-18 comes across as a bit clunky, but it is propably just the matter of the time spent on that platform, plus I just got a good brush up with Baltic Dragon's A-10C Red Flag campaign - would love it for F/A-18 in same depth. I am now playing the dominant fury campaign and I got a night mission where I just a bit too much with fifes and drums and got flapping over the target. I then decided to prepare myself a bit better for the next run. I watched couple of youtube videos again, but they did not actually address some of my grievances. Firstly, I can edit the target waypoint to my given target coordinates in the HSI (with precise option) and mark it as TGT on the SA. So far so good, but how do I get the ATFLIR (or Litening) to focus on that point? I am missing the SPIs and SOIs from A-10C here. The second question is concerning the HUD (or also the helmet targeting if I happened to have a day mission). I can not see any bloody cue on the HUD where that pod is pointing at? It just might be (after watching one YT clip) that I need to change the pod to "Scene" or even "Point" mode? (Is it the same for Litening) I am hugely missing these features, as in A-10C you can start from your waypoint, pan around and see it on the ground. If you get lost, you can always return to the waypoint and start all over. I am pretty sure there has to be something similar in F/A-18 but it is simply escaping me as it is. One further gimmick should be pointing to a mark point, but I would like to get the simple waypoint first.

Ok this review speaks its own language... Unfortunately he is too distracted once he mentions the cable - probably it is needed for performance and the wireless is not up to the task... Also he explicitly says that it is a step down from G2 in quality. So yes you probably deal with compression issues and what not and even with USB you can not match DP... so I guess nothing for me in the end...

What's the take on that "foveated rendering"? - is there actually another headset on market that's already doing it? Eyetracking could also enable some fancy stuff, but in the end that might a matter of implementation into each and every game individually, or not?

Yes, well MRTV said something like Half-Life running smooth and looking absolutely amazing. I am also sceptic about the wireless connection, but I would appreciate the benefits, however, even minimal stuttering would be already a no-go for me.

I have not been following the forum for a while, I am happily running HP Reverb G2. Lately I decided to check the forum out again and found about OpenXR and stuff like that. After trying to get me up to date with all the new stuff VR, I came across some Pico 4 reviews in YouTube, came back here but could not find any topics or on-going discussions about it? So what's the take on Pico 4? From the specs I find it actually quite inviting. For example: https://vr-compare.com/compare?h1=HdfjN_0UlPY&h2=PvfCDzaDK The resolution is in par with Reverb. I was never interested in Quest 2 and I am sceptical, how well the wireless connection would work here, but there could be some benefit there. SteamVR gets mentioned and I am wondering whether the OpenXR will work as well... It has potentially some further goodies which could be interesting, like foveated rendering. So in the end it might be interesting. My son has my old Reverb and he is cussing the cable as he does some classic VR gaming, so I mentioned it to him and he might talk to Santa. If we go down this path, I might borrow it and test it in DCS...

When I have the focus on let's say right DDI and I use Velocity Vector Slaved pointing method. When I press the designate I do not see the targeting pod cue going to that point on HUD and further more if I pan the cursor on the DDI, the cue does not follow on HUD, is this a bug or am I doing something wrong. It seems to be impossible to relate where the target pod is looking at when looking out of the cockpit. Shouldn't it be also visible on HMD? Somehow the A-10 is seriously better in this regard, but maybe I am setting it all up in a wrong manner...?

I flew the first missions and I got the code for the next one. I did not get a proper screenshot for all the details, but I would see it this way. For me SEAD, Trimmer and Fish CAP over Alpha? and Bravo. Hooters and Pickles also SEAD. Target coordinates 42 34' 57.76278"N 41 51'05.82007"E - it seems to be a bridge north of Zugdidi or so... So I started, I dragged my WP2 over that bridge. Apparently I can not change the assignment here in mission editor, but I selected the armament according to that list. So I think I got everything right on the deck and we got launched. I flew towards WP2 but I never got anything from SAMs, so I could not hit anything. There were red troops on that bridge, I do not know what they were but they did not want to shoot me. Flying around I got some handheld SAMs after me but that's that. Not once RWR from SAM. At some point my wingman got creased by a handheld as I was mooching around on deck and I then quit the mission because it was a road to nowhere. What did I do wrong? Should I have taken just some MAVs instead of HARMs and blasted, whatever was there on the bridge to bits? Does this campaign work properly? I saw some disturbing posts, for example like SAMs not shooting, depending on update, but the posts go almost a year back?

Yeah, that is not really the point. If the F/A-18 sensoric suite is able to place that HARM box in the HUD over the emitter, it should be very well in a position to point the targeting pod into that same location as a target. I am wondering whether the feature is there in the real life, just not implemented by ED or whether it is there but I am not just able to find it, or if it is not there because it is not there even in the real life.

I am playing Raven One campaign (yes could have asked on that forum too, but the question is rather general). In the mission one is supposed to check the HARM target with FLIR. Now, I can aim the HARM and all of that but once I have the SAM locked in HARM the FLIR is still looking God knows where and does not follow my lock. Is it possible at all, I would assume that that kind of sensor integration is implemented and it works with AA weapons as well, but HARM so far no luck...

Well the title says it all. The brightness does not adjust at least with the rotary on that panel. It is rather irritating when flying with NVG...is there any workaround or some night option for the display?

I am just playing the Raven One campaign and on my last mission I was directed to a surface target given in relation to bullseye. I was then messing around with the SA page and cursor but could not really do much good with it. I have now watched couple of videos and stuff and I am left with couple of questions. -Is there any easy way to create a markpoint or waypoint offset to the bullseye, so that I can navigate there? -Is there no "TDC depress" functionality in SA-page? Like hooking up in A-10? Can I not for example select a contact from SA page and have it also designated on the A/A Radar? -Is there no way to obtain for instance altitude information from datalink contacts?

I made the modifications manually as well and then the mission worked just fine. Thanks for sharing the trigger fix...

I was thinking about programming a keysequence that will engage autopilot using the Warthog HOTAS. As far as I can see the autopilot is controlled by UTC, so I was wondering if there was a way to define a keypress sequence that goes for ALT, ALT/HDG or PATH. not sure how changing the modes works, if I am let's say in ALT and switch to ALT/HDG, it would probably disengage the ALT option in autopilot panel? So I probably need to start each sequence with disengage AP, AP Button on UTC and then select the options? Did anybody do this so far? I am not convinced that HSEL replicates the real Hornet, not that I have so many hours on the real Hornet, but it feels counter intuitive that I need to set a heading before engaging HSEL. I would really expect it to use current course, unless set to something else, who would want to fly north as a default? It is almost as if I have Altitude Hold and AP will set the target altitude to 0 unless I set it before engaging... Also seems that I can not use UTC to tip in the values (unless I first use the the HDG switch with a longer press - there I get a HSEL option which I can tip in), for altitude there does not seem to be any option to tip in anything, it seems contrary to the whole purpose of using UTC for the autopilot in the first place...is it certain that this is the way it is in real Hornet? It would really turn me off from buying one and I would consider a M2000C instead.

So what about the priority numbers? Of course I can use the button to switch on and off the datapoint tracks on TID, but how do I perform my attack most effectively then? Switch back and forth, ensure that I see them, switch the datalink off and start shooting? Somehow that does not make sense? Apparently the DL tracks are upsidedown symbols but shouldn't I still get a prioritization between the rightsideup symbols at least (well this question stands)? Yesterday, I hooked singular targets from the TID and blasted away and I even hit some, but they certainly did not have the priority numbers on them at that moment and I had contacts showing on DDD, I just can not be sure if it was them, as there were quite a few contacts on that mission. I'll need to pay attention to the symbols when I fly the mission again today. BTW, shouldn't I get a P STT or PD STT lock also from a datapoint track by hooking it and pushing the respective button, the system knows where to point the antenna (unless the contact is in a filter)? Similarly I would expect TWS auto to point the antenna to the direction if I hook a DL track, so that I get my own radar contact? Is it then more recommendable to use the TWS manual initially and only switch to auto after establishing contacts?

I have been playing with F-14B every now and then. I now started with cage the bear campaign and got rather confused during the first mission. I already played the F-14 red flag campaign, but apparently it did not require that much knowledge as the cage the bear campaign. Firstly, I tuned in the datalink and I think that I get quite a few contacts displayed through the datalink without "seeing" myself them on the radar. In that case of a datalink contact I am not sure if I can launch them. The module has developed quite a bit so not all of the tutorials are very accurate. Somewhere during the mission I wanted to launch a salvo of AIM-54s but I could not see any priority numbers on the contacts? Was this again due to the datalink nature of those contacts or did I have a wrong radar mode, at that time I was in TWS Auto... Also I am not sure about the IFF. At times it works with the TWS (I think), when pressing the IFF and the radar is doing the sweep and at times it does not seem to work - well it seems that the TWS can see them but once I press the IFF, the contacts disappear and will not "blip" - I reckon it is different type of radarmode, as it shows the stuff in ranges instead of closures. Is there a way to select a contact on TID and make the DDD lock on that contact, let's say in PD STT or so? I am also missing all kinds of indications about the probability of a hit on TWS mode and going for the RIO sixshooter? Well I have plenty of more questions but those were few that came into my mind after playing the mission, crashing on the carrier and debriefing myself on what just happened during the mission. It is way more harder than the red flag missions. Maybe I should just fly around and stay out of RIO's seat and not try to do two jobs at the same time.

Yeah, well I have always been a Bf-109 kind of guy, I rather have K-4 than none, but I dislike sims preferring to bring out exotic variants like K-4 for the online arenas and completely ignore historical mainstays. I would prefer to see F-4 or G-6 in the game. FW-190 D-9 and A-8 fit the bill better by being more standard late war types, without being too ueber with too much steroids. Nevertheless, the K-4 feels pretty well done and also here you have the excellent campaign from Reflected - would just feel more historical with Gustav. I hope there are more to follow I really would not mind a Dora campaign from them. So if I measure the modules by the time they kept me occupied and happy I am happier with K-4 and A-8 and D-9 was more or less wasted money, although I think I got it dirt cheap in some sales action.

Depends what you want to do. If you are offline player for Dora there is only the boring stock campaign. For A-8 there is at least the Horrido campaign from Reflected. So far I have only played few missions - I like it very much so far, I already played their Bf-109 campaign which was excellent, so I am putting high hopes on this one too. I am not sure how finished they are. I have not looked at the Dora for a long time, the ground handling at that time was quirky and very doubtful, the A-8 at the current state feels an accurate replication of the accounts I have read about Focke-Wulf, maybe they did some fixes meanwhile on Dora too.

Hard to say. I had this feeling that my old Odyssey+ was actually heavier on my hardware than Reverb G1. Simply because I had to use much more pixel density for Samsung. With Reverb I have no pixel density and stuff. So it would be a simple matter of ordering one and trying it out. If it does not turn out well return it within the 14 days...BTW, I have 1080ti