daemon1808

Hi. I have a couple of tutorials that explain this, as far as I can: (min 13:30) The A-4C radar is not intended to designate targets. Think of radar as an aid for the low visibility navigation. What you are seen from above is a representation of the montains and "high ground" ahead. When you are fliying low, you should search for a gap between the peaks of the closer line of montains. Fly directly to the gap, search another gap in the next line of peaks, etc. If no gap appears, you will need to gain some altitude. Keep in mind that the pitch of the aircraft affects what radar gets. If you point the nose toward the ground, everything will appear as "high ground". If you point the nose towards the sky, everything will be "clear ground". The trick is get a "confortable" altitude, make little pitch variations to find where to avoid the terrain ahead. If you navigate a canyon, the lateral montains will appear as parallel lines, with a "clear gorund" between them. You just should maintain the aircraft in the middle "clear ground". Something like this ( "L" symbol is the aircraft path): ---- L ------- ------- L -------- ------- L ------- ------ L -------- --- L ---------- ---- L --------- ----- L --------- L And regarding the AG, it not search for anything. It is simply a "radar" pointer to measure the distance from your nose to the ground. If you want to attack a target with rockets, it is an aid to know when the target is "in range". Just point rirectly towards the target and the radar will give you the distance... start firing when the target is in range.. In the second part of the tutorial I explain this just at the begining.

Not at all. And thank you again for your efforts!

Don't missunderstand me. I wan't any credit for the mods or anything like that. I just take VSN and the MQ9-REAPER mods as basis, mix them and changed some parts for make them work for me (and other people with same or similar problems). Beside that, I have changed some other things to do more to my liking (like using f-15 cockpit with a-10 avionics, payloads or liveries), but no other big changes at all. I'm not a modder, for sure, I just found the solution to my problem with the try and error method. I have changed the mod name because seems that some people are not having problems at all with the originals. Others can fly the original mods only in multiplayer, others can't fly them at all, etc. I wanted to differentiate this mods from the VSN, and make them able to live together with the originals, if the users want to. As far as I'm concerned, this mods are yours. As I said, VSN are the basis and I have done minor changes. If you want me to remove the Eurofighter and don't publish more changes to other mods, no problem at all, just tell me. Seriously, I don't want to bother anyone and, to be fair, I really want the original mods to work again because some functionalities have been lost with the changes. :)

Even with the awesome work of VSN modders, after the last DCS updates, some of us still have problems. Even having the FC3 or the correspondent standalone modules, the mods are not flyable or crashed the game in single player. If you have problems too (after installing FC3, of course), you can try this other version for the Eurofighter. Find the mod in the description of the video.

The problem with the skins should be fixed now. Try the link of the version v1.1 in the description

In the description of the video you can find the link :smartass:

Finally I have found a solution, at least for my non- flyable problem. I don't know what is the problem yet, but it seems that this works for me

Hello, It seems that choosing a higher waypoint number do the trick but, at least for me, when I add the coordinates of the new waypoint something weird happens. I type coordinate to this waypoint directy to the north of my position. It looks good on the map screen as far as I don't deselect "data". But as soon as I deselect "data", the new waypoint appears directy to the south of my possition. The other waypoint configured through the mission editor seems to be ok, but the new waypoint is not in the expected possition.

Aaaaaand.... Now it works again. Don't ask me why, but now I can type the coordinates in the harrier keyboard and they appear in the MFD without problems. Same steps as a week ago, so I guess they have fix it ^_^

Nothing again. It is a pity but it seems that, at one point, one particular dcs release has broken all the vsn (at least for me) Some of them are not flyable, others are flyable but F2 view does't work and the cockpit is invisible (but the hud symbols remains)

Nothing again. Same issue as before: I can add the aircraft in the mission editor, I can select player pilot, but when I jump into the mission, it is not flyable. Maybe this behavior only happens in Steam version. Maybe I am wrong but... I was expecting *.dll files in the f-15c bin folder (I think I have access this folder before and found standard dlls) and I have found F15.dll.crypt. What a weird extension!... maybe this has been changed? Nevertheless I have change the extension for the copy/paste files, but same problem. :cry:

First of all, thank you for your support @cdpkobra. Really appreciate! Nop, I never purchased the Su-27 (only a-10a, f-15 and su-33), but in fack before the DCS upgrade I had changed the .lods files to the cockpit SU-33.. and it worked then. Now after the DCS upgrade It doesn't work anymore. Even I tried to use the a-10a cockpit (throught the "(z optional) A-10A-Avionik.cmd" file) and fails to get the plane flyable. And, as @JFCshloss said, I haven't installed them. Just decompresed manually the files into the c:/user/savedgames/.... folder. (but this worked in the past) Just to be sure: this is the direct link to the last version of the mod? https://www.dropbox.com/sh/z38jlgy34by4o9v/AABEjT1crgtzInnTlKuM9dQta?dl=0&preview=VSN_Tornado+v2.5.5.01.zip

The SU-33, the F-15 and the A-10a as separate modules. All was working fine before the last beta releasei n Steam. By chance, I tried the VSN tornado Wednesday without problems... and Friday all was boken.

It makes sense. Nowadays all electronics can store basic configurations (as the BIOS of a CPU) almost indefinitely. Then, I think the only reason to reset the IPP is if the aircraft has been transported to another base as a cargo, a system failure, or if it is in the aircarrier and for any reason the cable is not available.

Yes, that's it. The IPP step seems to be "broken". And I quoted broken because you can set the coordinates manually anyway (although it tricks you, not displaying them in the first stage, but storing them somehow). Then, the system ignores the coordinates and align the aircraft to the real position... but who wants to type wrong coordinates on purpose? So you already can "simulate" that you are aligning the aircraft, if you type the righ coordinates and ignore that they don't appear in the MFD until you start the GND alignment... as in the video ^_^

Nope, the problem for me is different: The game doesn't hangs. I can add a "VSN_tornado_GR4" in the mission editor for single player (for example) set player as the pilot, launch the mission and, when the mission starts, the aircraft is no-flyable (the AI takes control, the F1 view is not accessible, only external views, etc). This happens online, offline, logged in DCS account or logout. What can I say?, I am always "the special guy" ^_^

Ummm, it's weird. Using the DCS 2.5.5.31917 Open beta on Steam It seems that these new versions don't work. Neither the other mods with old versions. Thanks anyway :(

And this is other video is one example as it seems to work months ago: :(

No, no... i have readed it. Even so another unofficial short manual that I have found in some other post. The manual says: INS Alignment Procedure All modes 1. Make sure that the INS mode selector is in the OFF position. 2. Select EHSD o the MPCD (either left or right). 3. Select DATA on the MPCD. 4. Select AC (aircraft data) on the MPCD. a. Aircraft present position will be shown. b. UFC/ODU will enter Aircraft Position mode. c. The following ODU options are available: i. Option 1: POS (Lat/Lon position coordinates). ii. Option 2: MVAR (Local magnetic variation). iii. Option 3: WIND (Wind Direction and Speed). iv. Option 4: SHIP (Carrier heading and speed). v. Option 5: THDG (Aircraft true heading). 5. Enter AC initial present position (IPP) latitude and longitude. 6. Enter local magnetic variation (MVAR) if the value shown is 0. 7. Place the INS mode selector knob in the selected alignment mode: SEA< GND, IFA or GYRO. The alignment process will start immediately if the required data has been entered. 8. When the alignment is finished place the INS mode selector knob either in NAV (for degraded mode navigation) or IFA (for GPS coupled navigation). It is in the step 5 were I having problems. When I type the AC latitude and longuitude the system do weird things. As far as I know, and the manual seems to said the same, you can enter the AC lat, long, MVAR, wind manually. But in the case of lat and long the harrier just ignore your imputs. I have found many videos from time ago, where people input the data without problem, but in my case you can see my issue here (go to min 1:55 and before):

I have found in the end that they are there, even if the option is grey. Thank you!

No, the ones that explodes where not the VSN as far as I know. The A4e and the aermacchi m346 had this "explosive" problem, but in the last beta was solved. The new problem affects only the VSN modules. The are not flyable anymore, at least for me, since the last 06/06/2019 upgrade. :(

Yes, as Rudel said only FC3 cockpits can be used in the VSN mods. It is a pitty, but it will be ****ing awesome :pilotfly: And yes, the trick is to coping some .lua configurations from one mod to another, but you can do it only between VSN mods. Here is a video with an example (Tornado with F-15 cockpit and A-10a avionics):

I'm a bit frustrated with the Harrier INS too. I am not able to align it in any way after many tries. I am having two problems: 1. Many vids explain that you need to connect groung power, but I am not able to connect to grown team. How they are contact? the "ground team" option always appear in grey, even if I turn on the radio and contact the tower. 2. Nevertheless I am trying to align INS without connecting groud power. But I can't: I enter Data->A/C submenus and insert coordinates, but the harrier refuses them. After I click ENT key, the coordinates are reset to 00'00'00 in the frontal display and are not stored in the system. The funy thing is that I can set the mag variation without any problem O_O The manual does not help, I am following the steps, but it doesn't work. What I am doing wrong?

It is just for me or after yesterday DCS beta release all VSN mods are not working anymore? :cry:

Hello all. I've been having issues with my Lenovo Explorer vr headset regarding the clickable cockpits. The "clickable grid" does not match the real possition of the buttons, dials, etc. I mean it seems that the clickeable areas are displaced so, when I want to click one particular button, i have to drag arround the mouse cursor near the button area to find where to click really. I have tried to change the game resolution, the desktop resolution, the headset resolution, but nothing solve the problem. Does anyone the same problem and know how to solve or workarround it? I'm using a geForce 1070 Thanks