Zeros

Must of mised that thread.Thanks for the heads up.

Specifiic textures where they are distiguish the areas on deck in the US Carriers. are missing.Although CV Admiral Kuznetsoff looks fine and CV Forrestal look fine. Picture from ME https://ibb.co/hBR8Q2m Running latest DCS-mt version

Goodmorning IanC58 Thank you very much for your offer. I made some trial tests on my mission and here is what i've got.First of all the mission profile is SEAD from a pair of AI AV-8B's set Veteran skills.They are suppose to take of from an airfield and conduct a low level profile flight to a target area (Target area consists of 2 groups of SA-6's and one group of EW Radar).Points are: MSL is the proper altitude set for low level flights,tho there is a catch.If a group that will perform the mission includes group activates....(lasing,low level flight,etc)....the first WP after take off must be place far...far away from the engaged/detection area of target.They have to rendezvous first before proceed to the group activate.In my case is the low level flight where the flight leader flew at 1600 to 1900ft....(despite the fact that there was never set flight plan to such an altitude)....until his No2 came to rendezvous.In case of someone places their group to spawn in mid air all of the above dont matter. Tasking.Although the mission is a SEAD mission tasking the group as SEAD is a bad idea.The thing is that for some reason flight leader and the rest of the group brake the rule of low flight and accent to an altitude of 2000ft way berofe the firing range of their weapons,they get detect by the SAM's site and they just jettison their weapon trying to evade fire. CAS is the trick.Task the group as CAS and on the last/nearest point to the target set a trigger of "attack group/unit" and that's it. Formation.Not usefull.I set a formation trigrer (close group-line abreast) and the flight leader kept flying above the set altitude which it resulted been detect jettison his weapon to evade and consequently failed to proceed with the mission task.No2 kept a low flight profile and proceeded tasking. Those are my finding to anyone is interest. Thanks IanC58 for his insight. Thanks man i appreciate.

Both. When set on msl the aircraft holds about 2100ft and when in agl about 1600ft. The funny part is that on this example the harrier must take off and proceed to the given waypoint while on another mission where the harrier spawn on mid air they spawn aproxiemetly at 300ft and start immediately accend to 600ft trying to mask the ground (but i can recall what set altitude is on agl or msl) and trying the other way around ist just climbs tou 1600ft.

Goodmorning fellow simmers I have a question.Am setting a simple SEAD mission using the SKYNET script and assing a pair of AV-8B's to engage a specific SAM site(SA-6's).I gave the Harriers waypoints route with altitude of 400 ft (to avoid detection).No matter the set waypoint altitude Harriers keeps a 1600 ft lowest in route altitude.So what gives?AI is unable to fly below 1600 ft?.PS. Using the Syria map for this mission and the route is on Cyprus island where most of the terrain is flat. Thank you in advance

So as the title of this topic says AI AV-8b's are unable to take off and keeps crushing. Here's the thing.I've created a simple mission on the Syria map where i stampled on this weard problem. On the mission i have 2 squadrons of AI f-18's (4 F-18A whith SEAD objectives and 4 F/A-18C with fighter sweep objectives and a E2 AWAC all of the activated through radio menu) and they are operating from a Super Carrier.They work smooth as butter....triggers and everything. I also have 1 squadron (4 aicrafts) of AI AV-8B harriers operating either from TARAWA LH-1 or the Juan Carlos L61 (also activated through radio menu) and on mission ONLY the leading AI Harrier manage to make a succefull take off the other 3 goes to "drink"(nope they are not heavy loaded....keep reading on to the next example) i also have a client AV-8B for me with a wing man on Kingsfield airfield(Cyprus)...but no matter the priority (either am the leading aircraft..or change to the AI to be the leading aircaft) ...my wing man is unble to take off...when am the leading aircraft he keeps rear end me damaging or worst and when he is the leading aicraft he keeps crashing on the fence at the end of the runway.All AV-8B are set to "veteran" no heavy loads but still can get then to the air.Any suggestions?

I believe you're looking for this.It's not in PDF format but you can figure it out .https://wiki.hoggitworld.com/view/Threat_Database

As the headline says i stumbled on a bug while setting a single mission. I have 2 AI squadron on the SC to spawn when ever i please to via F10 menu trigger. On my first test run i spawned the f-18's first and after 10 sec spawned the F-14's (both of them cold start.) While the f-18's took off normal the first in line from the F-14 got stack right before catapelt one. I thought that spawning 2 squadrons with very litle time spacing might be the reason for the F-14 to stack i reload the mission and spawned just the F-14 no F-18's...and still the Tomcat got stack again. Is there a way to fix this? [img]https://i.imgur.com/JR5u1Q6.jpg[/img]

Thank dark_wood for the reply Found the culprit On my first trigger argument had to change radio item "group"(the culprit) in to radio item coalition. That did the trick..now my F10 menu contains all my appointed aircraft units ready to spawn. Found a bug also on the Super Carrier.My F-14 squadron is unable to maneuver and make it to the catapelt.... the deck is clear of any kind of static objects and not clustered by any spawned units. Thanks again mate Cheers

Okey here is the thing am building a single players mission where am trying to spawn some airplane units,some of the in land bases and some of them onboard naval vessels(SC).I have succefully manage in other mission builds of mine to spawn airboard units via F10 menu(radio item action) but they where single units(Reaper for JTAC or KC130 for AAR) but on this current mission am trying to spawn squadron o 4 units,pairs of 2 units and singles. In total i have created 5 occasion of spawning but for the life of me seem that i cant make it to work.At first i thought that it was imposable to spawn squdrons of 4 but on a test run the only functional units was my AV-8B squadron out of the Tarawa.I feedle on the ME with the "late activation" check boxes and on the next run the AV-8b's where gone and the pair of 2 of my Mirage's appeared on the F10menu.All units are checked as "uncontroled"...all units have been set with a "start" trigger on the main menu of the unit.(not to be confused with the actuall trigger menu). On the main trigger menu all units are using the same arguments and are as follow: 1trigger "once"---conditions "none"---actions "radio item push"-"flag x""value z" 1Trigger"once"---conditions "flag equals x-z"----action "ai task push"(message to coalition and sound also but i took them out just to test) So does anyone else have issues with this? P.S.No scripts involved. Thanks

Increíble mod. Señores, muchas gracias. Incredible mod gentlemen. Thank you very much.

That explaines alot.Thank you very much Aernov. ***To admins of this section please move/remove my post at your discretion.

Goodmorning guys Got a strange issue here.I haven't been loged for a while in the game but after the new update (2.7) got right back on the saddle.I regularly fly the AV8B but after the 2.7 update i got an idle problem.It seem that the idle of the engine is no less then 28%....its power enough to start rolling on the tarmac on an empty configuration aircraft. I tryed everything....for startes i want to say that my cutt off function works perfect on my throtles rear detent. Tryed to calibrate the throttle through the TARGET gui app but didnt worked...i even found here on this forum a Calibration tool for the thustmaster throtle which i use it but still ...no joy.I moved to fly my F/A-18 modyle and there the trotle works perfect...even the "throtlle right-left idle/off" works. So does anybody else faces a simular problem? Thank in advance.

BIGNEWY Thank you sir......and.....excuse my previous outburst but coming out strong on a insignificant bug such as this was my only option at the moment. Again thank you for your time and hope the developer team adress this issue with the proper attention.

#kengou yes i undestand the night operation of a FLIR but am confused when i watched all this tutorial videos on how the NAVFLIR operates on the HUD area and they did not have the problem that am having.The FLIR is a very good solution for spotting targets on a blending color enviroment.Probably Rasbam at some point updating the Harrier "fixed" the FLIR to operate only on night time.Thats to bad cause its a game breaker for me.Am using a 42" TV screen and position my self 5 feet away from it.Am not gonna stick my face on the screen just to spot target on daytime missions.I wiil put the harrier aside and move on learnig the F/A-18C. Thanks for the insight friend.

Hey there fellas here is the story.Am on training missions ....A2G specificly and want to use the HUD FLIR function during day time to spot my targets but it seem that there is something wrong with the HUD every time i switch the HUD switch from "DAY/AUTO " to "NIGHT".I followed the procedure written on the manual..which is the same as the one followed on any tutorial video i have watched but never incounterd a problem like the one am having.So every time i switch the HUD switch in NIGHT time mode the HUD info disappears....wash off....you can barely seen them.(see the photos below)So what gives??? HUD on "DAY or AUTO " HUD on "NIGHT" Sensor HUD Reject/TGP on Cheers

As of April 19 and after DCS World open beta 2.5.6.47224 update the "bort number" problem is not fixed.(picture below) Not only that but also new problems have arrived.You can see on the picture above..and below that the new problem is that while the aircraft is inside the hangar the sunlight paasses through like there is no haggar surrounding walls. What up with that??

I have made another picture maybe this will help better explain what i mean On the .lua file am using the "BORT_NUMBER_KIL_Switz" {"F18C_BORT_NUMBER_KIL_Switz_R_100", 0 ,"F18C_2_DIFF_aces",false}; {"F18C_BORT_NUMBER_KIL_Switz_R_100", ROUGHNESS_METALLIC ,"F18C_2_DIF_RoughMet",true}; {"F18C_BORT_NUMBER_KIL_Switz_R_100", DECAL ,"F18C_bort_number_aces",false}; {"F18C_BORT_NUMBER_KIL_Switz_R_10", 0 ,"F18C_2_DIFF_aces",false}; {"F18C_BORT_NUMBER_KIL_Switz_R_10", ROUGHNESS_METALLIC ,"F18C_2_DIF_RoughMet",true}; {"F18C_BORT_NUMBER_KIL_Switz_R_10", DECAL ,"F18C_bort_number_aces",false}; {"F18C_BORT_NUMBER_KIL_Switz_R_01", 0 ,"F18C_2_DIFF_aces",false}; {"F18C_BORT_NUMBER_KIL_Switz_R_01", ROUGHNESS_METALLIC ,"F18C_2_DIF_RoughMet",true}; {"F18C_BORT_NUMBER_KIL_Switz_R_01", DECAL ,"F18C_bort_number_aces",false}; {"F18C_BORT_NUMBER_KIL_Switz_L_100", 0 ,"F18C_2_DIFF_aces",false}; {"F18C_BORT_NUMBER_KIL_Switz_L_100", ROUGHNESS_METALLIC ,"F18C_2_DIF_RoughMet",true}; {"F18C_BORT_NUMBER_KIL_Switz_L_100", DECAL ,"F18C_bort_number_aces",false}; {"F18C_BORT_NUMBER_KIL_Switz_L_10", 0 ,"F18C_2_DIFF_aces",false}; {"F18C_BORT_NUMBER_KIL_Switz_L_10", ROUGHNESS_METALLIC ,"F18C_2_DIF_RoughMet",true}; {"F18C_BORT_NUMBER_KIL_Switz_L_10", DECAL ,"F18C_bort_number_aces",false}; {"F18C_BORT_NUMBER_KIL_Switz_L_01", 0 ,"F18C_2_DIFF_aces",false}; {"F18C_BORT_NUMBER_KIL_Switz_L_01", ROUGHNESS_METALLIC ,"F18C_2_DIF_RoughMet",true}; {"F18C_BORT_NUMBER_KIL_Switz_L_01", DECAL ,"F18C_bort_number_aces",false};

BIGNEWY I'm not having trouble with any texture..and by the way am using the official F/A-18C template.The problem lies with the bort_number.....(thats how they are descriped inside the description.lua file)...bort_number are the dynamically changable ID number of an aircraft and they are 3d modeled.As in the pictures i uploaded....(take a closer look when your are checking the left side cause the sunlight glares on the tail surface and make difficult to distinguish the bort_number)On the left side the bort_number is located at the bottom and MIDDLE of the Vertical tail while on the right side the bort_number located on the bottom and FORWARD to the vertical tail. Cheers

i used the photolinked ability of the phorum but it seem not working..anyway here it is again via http link https://imgur.com/PDniia9 https://imgur.com/FVaWvMo You will see that the Bort numper on the right vertical stable finn is place in the middle while on the left vertical stable finn is placed all the way in front..almost to the front edge of the vertical stable finn.It like the 3d meshes that represent the bort numbers are misalignged. Thank you for your time. Cheers

Hello there Am almost finishing a desert camo for my F/A-18 when i stabled on this issue. The Bort Numbers on the vertical tail finns are not aligned correctly. The bord number on the left side tail finn is alighed in the middle while the bort number on the right is located far front on the finn.Is this a bug or am i doing something wrong? I have also attached two external links from imgur.com with photos targeting the problem am describing..but it seems that those links are invisible on the thread presentation...they dont show up.

Hey there fellas Am just another newbie who flyies the Harrier and joined the Havoc Dedicated server for the first time...and i must admit that i really enjoed the ride.Just one question...are the Mav's65E(IR) prohibited from this server...cause..for the life of me..i couldn't make them to "rifffle".Check all my procedures to deploy the weapon..and everything was set to the point.Does anyone else had the same problem?

Thank you Ramsay.Your answer is very helpfull. Cheers

Am running on the latest Beta version of DCS (DCS 2.5.5.34108) and i realised a weird function when am adding WPs manually.First of all i keep the rule of setting at least one WP in the ME.So when am in the game and i add a waypoint using the UFC panel i realized that every time i add a waypoint the coordinate setting is working on a zig-zag pattern.To explain what i mean....when i add my second WP (the first is allready set in the ME) the order of setting coordinates is North coords first and East coords second....but when i go to set a third WP i must set East coords first and North coords second...on the next WP North coords first and East coords second...etc. Is this normal??

Good morning fellas Am aware that this is and old thread and hate to bump on it like so but i have a question regarding facetracknoir and since this is the only thread i found that is related to that software i thought putting my question here instead of opening a new thread.I thing it would be pitty to scatter all over this forum multiple threads regarding the same software...besides it would be much easier for other users of this software to look in one thread possible solutions instead of looking in multiple thread. I apologize if my thinking is wrong....any way..here goes nothing. I have a trackhat clip but i have desided to use it with the facetracknoir software instead of the trackhat/opentrack software cause it give me alot of jittering. Any how i purchased the latest version of facetracknoir software (V201) and set it up with my trackhat clip which is running smoother and more to my liking but it seems i cant make the zoom function to work when i'm looking side ways. While when am looking forward the zoom function works perfectly...when am looking either left or right...the zoom function still zooms forwarward direction instead left..or right. Any ideas to solve my problem is appreciated. Cheers