Flyingsix

Schonmal metashaders und fxo gelöscht? Gesendet von iPhone mit Tapatalk

Awesome! Thank you for the quick help! It's weird with the weak wind logic. But from now on I know what I have to do. Thanks again! Take care!

Hey, as mentioned in the title - i tried to get an ILS-Signal of RWY 14 @ Tonopah Test Range (KTNX). I tested it with C101, A-10C and F-16. With no A/C I got an ILS, wether LOC nor G/S. On the other hand, I tested all A/Cs at Groom Lake and Nellis and there I got an ILS-Signal. Is it a bug? PS: I used the original beacon.lua of Nevada.

Jupp. Auch der Modulbildschirm und die Serveraktualisierung mucken rum. Gesendet von iPhone mit Tapatalk

CombatFlite ist klasse. Mit den implementierten Funktionen kann man richtig viel machen. Ich nutze es selbst für den Missionsbau und für das Planning damit die Kollegen Kneeboards bekommen. Zur Zeit habe ich allerdings Probleme mit den errechneten HDGs. Bei stärkeren Winden in der Luft passen die leider nicht. Wenn man jetzt nicht gerade rein nach HSI, Kompass und Timing navigiert, ist es kein Faktor weil man Point to point fliegen kann und die falschen headings nicht auffallen. Für raw Data Navigation ist es so aber nicht nutzbar. Gesendet von iPhone mit Tapatalk

Thx for response. I've done some testing and I can say, that the Mavs are now working for me. My mistake was: I tried to lock Buildings or trees (static map structures). But the RB-75s seems to work only with units.

Hey Guys, I have trouble to get the Mav's shooted. Following Procedure: 1) Radar Mode ANF 2) Weapons Selector RB-75 - now I get the Crosshair 3) Pressing T1 Knob to activate Slew Control 4) slew over any target 5) Pressing TV Fix - no reaction. The Crosshair is not locked over the target. Any known bugs, or am I wrong with my procedure? Is it necessary to have a "M" Waypoint? Greetz

Alright! Thanks for your answer. Well, when I re-install the campaign, that means, i have to do all previous missions again? Yeah, at my 3rd run I tried this, but unfortunately FE aborted the PO because I diverted from the last given heading of 040 (Crosswind). After three calls that I have to keep this heading he aborted. :-D

After 4 trys I gave up mission #3 - Traffic Patterns. It seems that I'm missing positioned triggers. After WP2 I flown HDG 260 at Angles 8 (which should be WP3) and there is no response, after passing WP3. After my self-induced turn inbound airfield (approx. 10 NM west of WP3, after looong waiting of response) there coming a text message (no voice-over) to ask Batumi for vectors. Ok, after getting an rough vector to Batumi i centered the plane towards the runway at Angels 8. Over the threshold FE is calling "RWY is blocked" stay at pattern ALT between 200 - 250 knots at the upwind. At the other side of RWY he is calling turn HDG 040 at pattern Altitude... after this command I flown multiple times at this heading and there was no further advisory from the FE to continue towards Downwind. As mentioned before - I tried this multiple times and always I have big trigger issues.

Roger! Thank you for the fast response, sir. :pilotfly:

Hey Guys, thx for the huge Manual. I would appreciate a PDF-Version for mobile purposes. I also have problems with the shown TIT explained as EGT. Does the note mean, that the F110 EIG Version will show an EGT-Indication? If yes, the TIT isn't explained yet for the present illustration!

Hey dudes. I'm also flying real FBW-Aircraft and worked for many years on avionics. I totally agree with Ranchgrom. Thank you for your analysis. The throttle curve may be a matter of adequate thrust correction in relation of throttle-movement. In my opinion, and if I understood Ranchgrom right he meant the same, the characteristic of the a/c performance in relation of power-setting isn't ok. Commercial pilots are very focused on pitch+power concept. Here we need the constant AOA concept what normally should be more easier than P+P. Nevertheless the aircraft shows a very indifferent behavior. With only a delta of 1% N1 RPM the A/C gives a large feedback. Descent Rates getting high, approach is getting unstable. @Druid: I also made the experience, that the aircraft tries to nail the AOA, what ever happens... The a/c shows the feedback of decreasing speed, with decreasing power. I don't have the big picture of the flight modell...Maybe the trim-controller is working to slow to get the correct STAB position for the present power-setting. Result: A/C has to lower nose (faster than the STAB Movement) to keep energy state and AOA const.... This is what it feels like. But guys - for now its a very nice module. I love to work with it and I'm looking forward for the improvements! Greetz

Hey Folks, is it possible to select previous set initial points as waypoints in the aircraft? Background: I'm trying to build realistic IFR Training Missions. Therefore I need some "free", not predefined waypoints which the pilot can choose. Normally you can put some waypoints on a group, but the pilot should choose his waypoints in accordance with ATC or published departure/approach charts. Otherwise the pilot is nailed to stay with conventional nav-aids like TACAN, NDB, etc.. If I remember correctly the A-10C is able to select inital points as waypoints. Is there a way to do it with the Hornet? Greetz

Hey Grimes, thank you for your fast answer. I tried it with your code, but it doesn't work. No Error Messages, but also no Message when passing the 'gate'. In sum, I think, I understand the mechanics behind the function fastPIP. You say, that all units, which are alive should tell it's point inbound the polygon and set a specific flag true. Outbound the polygon, the won't tell any point, because the haven't any points inbound. As soon as they pass the first polygon line they will tell their points. In detail...What means the #units argument? Never seen the '#' in according with a for-loop. Is it the argument which says --> 'give me all units out of the units-class in this mission' (mist-database?) ? Also I don't understand this... timer.getTime() + 1, 0.05 Why the +1 sec argument? Would i not have a first measurement with 1 sec delay? In the moment I'm not at home, so I can't do any tests. I'll try some troubleshooting later. Greetz

Hey Grimes, sure. Yes, it's a client-aircraft. How does this matter? xx_PolygonTest.miz

Hey Guys, it's time for another little test object. I want to detect an aircraft within a polygonzone. Here are the facts: The polygon is created by a late activated helicopter (poly1) with 4 points. No closed loop (lines are not crossing each other) One A-10 is flying towards this polygon @ 200ft AGL Passing the Entry-Line of the Polygon a text message should be triggerd via DCS-Editor Trigger condition: Flag is True (101) As detection function I choosed: do mist.flagFunc.units_in_polygon{ units = {'[blue][plane]'}, zone = mist.getGroupPoints('poly1'), flag = 101 } endIt doesn't work! No Error Message till now, so I assume the MIST.lua is loaded correctly. May u can help me? Cheers!

Hey Grimes, thank you for the .miz file. That helped a lot. I did a VERY stupid mistake by using the unitname player1 as groupname... :doh: Oh my godness... Thanks a lot!

Ok, guys. First I tried it like Grimes described it. Then in different other ways.... Increased the time for mist.lua file, local or global variables, etc., etc., but no way. Always the same error (refer to #3). In last instance I extracted the local variable unit via: do [u]local myUnit = Unit.getByName('player1')[/u] local AoA = mist.getAoA (myUnit) trigger.action.outText (string.format('%-25s', 'AoA: ') .. AoA .. ' degrees\n') end Step by step I commented out every line and always the script stuck at the 3rd line: local AoA = mist.getAoA (myUnit)

Oh yes, I see! Due to the object "unit" which contains in the mist.getAoA(UNIT) prompt I have to connect the string player1 to unit. Thank you. Nevertheless the script doesn't work correctly. It seems the MIST.lua file doesn't initialize in the right manner. With init-trigger order: MISSION START > TIME MORE (2) > DO SCRIPT FILE (mist_4_3_74.lua) I got the error: "...attempt to index global mist (a nil file) .." Next step. As stated in another thread I used this init-order: MISSION START > TIME LESS (2) > DO SCRIPT FILE (mist_4_3_74.lua) I got the error: " ... attempt to index local 'unit' (a nil file) ... 1: in function 'getAoA ... " Is this a script-error or a init-error with the master MIST.lua file?

Hey Folks, I read a lot about scripting and the possibilities. Presently I want to use MIST for a simple task --> showing the actual AoA in a message. The data has to refresh itself instantly, if it changes. Later on I want to exploit other flight data as well like speed, height (AGL), power-setting. Reason behind is to configure a basic flight training mission for each of my module. I want to fly analogical to the manual and get a information on screen for reference data vs. present data. I found the mist.demos.printFlightData () part in the mist.lua but I have problems to adapt it to my mission. At Mission Start Master Mist.lue file is loaded after 1 second. Here is my script which I open via DO SCRIPT FILE: do local AoA = mist.getAoA (player1) trigger.action.outText (string.format('%-25s', 'AoA: ') .. AoA .. ' degrees\n') end I'm not very experienced with lua-scripting, but eager to learn it. :pilotfly: Cheers

Oh, I see! :doh:

Presently Tacview is not working on my system with its actual version. Have to wait for the fix. Then I will make a track.

In my opinion, yes. But I suspect we're talking about two different things. If I understood your post in the right manner, then you're talking about the interrogation line (a bent line on top of the VTB, as you described it) and that I must not confuse it with any other lines. I mean the dashed straight line which appears sporadically, when the radar is scanning against a jamming aircraft and sometimes getting an echo strong enough to display a trackable contact on the screen. Then you can see a straight dashed line from the origin to the contact for some seconds. This line also moves in relationship to your actual longitudinal direction. If this straight line has an other function, than please correct me :doh: But to confirm the correct usage of IFF... 1) pressing the interrogation button (NWS-Button) 2) looking at the VTB and see the bent line in the top (confirmation that actually the interrogation is running) 3) checking for diamond- or non-diamond-aircrafts and the last point, if I've actually locked on a target... 4) checking for an blinking "A" on the HUD (A = friendly) Greetz

I had exactly the same situation yesterday. Two times. After the teamkills I got kicked (also @104th). The first kill was a non-jamming contact and i choose the “standard” lock-on procedure via RWS->TWS->STT. The IFF panel was set to CONT. The second kill was a jamming contact. I’m not sure if the jamming blips showing diamonds if it’s a friendly guy. Maybe you have an answer for that. But nevertheless I followed the sporadically trace (dashed trace-line) on the VTB and switched to horizontal close combat mode. After some minutes of search I got a track. I IFF’ed him and there was no diamond and no “A” in the HUD. Shoot him down and got kicked. Maybe it’s a misinterpretation or it is a bug. Don’t know. But I will try to keep an eye on it with tacview.