Limaro

Sehr schade. Aber vielen Dank für die klare Antwort :)

Hallo zusammen, kann man wenn man zu zweit im Multiplayer fliegt, der eine A10, der andere F18, sich irgendwie gegenseitig im Datalink sehen? Im konkreten plate ich aus der A10 aus jemanden in der F18 zu hooken. Gruß Limaro

Ok, that's what I wanted to know:thumbup:

But what and when would be the commication about the assigned stack?

Hi, after some time of landing on the carrier I wanted to know how it works with the stacks in case 1 landing. I guess i've understood it in general. However, in the manual I don't find the part in the comms, where marshal tells me, which stack I should wait on, and also I tried to set up a game with douzends of F/A18 landing to force the need of stacks - but it just does not happen to change. The only thing is, that I do net get the Charlie signal when arriving. Do I miss something?

that was the one I tried to point out :smartass:

oh wow, thats a funny timing. thanks.:thumbup: Side note and maybe question to ED: I am wonderung how the decision are made to make this behaviour switching from one function to another. Particulary because there is a real plane with a real "how it works" as template.

Hi, IIRC the TGP "resetted" to look forward again, when pressing China Hat Aft short. Now, the Laser search is starting. How can I let the tgp look into default direction again?

Here is my contribution:

Generally I prefer the F/A 18, but . I would say A10C anyway because it would fit best in the collection of what you already have. (Have to mention that beside I only now F/A 18, not the Harrier.) Maybe you should now only decide the order of modules to buy ;)

I was testing VR. And I agree on your dogfight-issue. But once, putting on also by headset with still mounted TrackIR - TrackIR took over control of the view. However, it was not that smooth as usual. But maybe there is a way to switch of the VR for such a case.:huh: To the thing of "hitting" the buttons with the mouse. I have some side buttons on the mouse, and added the "precision-button" on it. So whenever I need to click I could fastly switch it on and again off.:thumbup:

Thanks you were right. a lot of things were messed up. Commands suddenly there multiple times over category "General" and "GUI Layer". Strange, that there is not a "replace" warning, when assining.

Hi, did the way how to create mark points change? I cannot create/see them with the Open Beta. The Release seams to work. Regards

I have the impression this is caused, wenn mission starts at night, and later on, at day, the comms are messed up.

I read some pages of the whishlist, and found many COMM-related things. Maybe the following idea was already mention somewhen, but as I consider this easy to implement, I hope it gets a bit more focus - or gets developed secretly hiding any feature-dev-workflow :smilewink:. Idea: COMM selector cursor to easily select and jump through the comm options - Assignable to keys or buttons of a HOTAS. It would reduce significantly the need take hands off the hotas to the mouse or keyboard. Example (please forgive me my use of paint) :

Ah now I understand. So it's kind of mode, where my stick movements are ignored, but also the AP is not active. Is this good for anything? Any situation? @ randomTOTENI now also see it on the DDI. This was a quite unexpected behaviour for me. Thanks for your clearifications! :thumbup:

I've uploaded a video that shows the issue as you can see in the controls view (bottom left) at some point I am making a lot of movings, but the plane does not react (as if autopilot is on). But the altitude is not kept in the same moment. Then, when suddenly the plane moves, I pressed the button to disable it on my hotas.

Hi, I em experiancing something in the Open Beta since some time, which I cannot explain. And I cannot remember having that in the release version (2.5.5.???) a) Sometimes, when activating the barometric altitude keeping autopilot, the two dots don't appear. So it seams it is not active. b) Other times, when it's active (and there are the two dots) - they disappread suddenly - without me doing anything unusual. When this happens, the plane starts changing altitude. But when that happens and I try to steer, I feel that the Autopilot is still active as I have to steer a lot until it reacts (Or I can deactivate it by button). I have this quite often. Autopilot on - BALT not marked active, altitude changes anyway. What is the reason for that, and what can I do to keep autopilot active?

I see. Not it's workingm using 110.90. Dont know what I did wrong presiously. But now I am still consued as I am missing is the Glide Slope. The Localizer seems to work, but the other. Is this normal for some airports?

Hi, I wanted to exercise landing with ILS. Trying so landing in Dubai, I dont get it to work. I've set up the ILS, it's on, according to Map it's to the right frequency, I am only 7nm away. but somehow it does not work (getting no information in HSI nor in HUD. However, I hear the peeps). What am I doing wrong? (I also tried the other ILS frequency) This is my actual view:

Hi, I am having trouble with this, but cannot tell on what side, PC or Tablet. I have actually two tablets I am testing this with. Conditions: One Tablet Samsung A6 with Android 5.0.1 and the second Huawei with Android 9 Wifi quite ok for normal stuff. 2/3 Bars. (good for 2k Streaming) - First of all, only one of both tablets can be reached at once. - When connection is established from PC, the tablet remains in "Waiting for Connection" for several time. > This sometimes gets only (sometimes) solved by wildly clicking on one of the Modules in PC Application (A10c, F/A 18,...) - Often when testing, the APplication from PC does not allow me to Make the Instrument placement (disabled button) - Also often the App on tablet seams not to start well. Screen remains black for some minutes. - The Displays from F/A 18 are totally not sharp (screenshot) - The only thing which I got to work was one MFCD for the A10c, and the latency of the images was,.. not impressive - After some tries for F/A 18 I was within two hours (No connection, No content of MFD on tablet, crashing apps, not found tablets at PC) finally having DDI and picture (looked as in screenshot, nothing readable) on my tablet. After 10 seconds and 10 frames, the picture freezed and only the buttons worked afterwards.. no more FLIR image. How can I get those things to work? Is there some special trick that I oversaw in the manual? (http://lumatek.sk/aInstruments/aInstruments.pdf)

Thanks, that was the solution :music_whistling::thumbup:

Hi, since some time now I am wondering about the COMM Systems from the F/A 18. I've read that actuall the two comms would work identically. However, using COMM 1 does not really work in my case. Setting the frequencies, and then pressing the COMM1 button, the expected one is still greyed out. When "overriding" this grey state, it is set up in the COMM 2 (Manual mode). Am I overseeing something?

I just got my HP Reverb, which was ment to replace my 32inch 4k screen for DCS (+TrackIR). From this special point of view, my personal recommendation currently: Upgrade your Monitor, but not necessarely wide-screen. I am sending the Reverb back. Main reasons for this decision: 1. Even with the HP Reverb having 2160² pixels resolution per Eye, I feel like counting pixels coming from my 4k-Screen. Its sharpness is currently unbeatable for me (it's placed about 50cm in front of my eye) Of course, this is extremely subjective. Compared to my old 27inch full HD Monitor, the sharpness from the Reverb would be quite ok. 2. About why I would not take wide screen: My biggest WOW-Effect on the Reverb was actually the gain of field of view vertically. In my plane while making a turn: Looking up is just amaizing. This is what I miss most on my Monitor. I even think, that having 4:3 Screen-Ratio with 4k would be even greater than 16:9. 3. The image in the/my HP Reverb is blurred at the side, when only moving the eyes (I've read that this is quite of normal for VR). But this forces me to move the head 100% towards the thing I want to look at. This is espacially painfull, when you have to read buttons on the control panel on the sides, or look to the back. Secondary Reasons: 3. The "Overhead" of tweaking performance with extra shader mods and other special settings, keeping all up to date - I dont like this much. But maybe I am only too old. 4. I deadly missed the possibility to "quickly" type stuff on keyboard. Beside of mouse and hotas, I feel kind of blind. I desperately hope, that in two to four years, I can upgrade my PC again and get 4k*4k per Eye VR. With a little more Field of view as well.