Rolds

Solved NVM :doh:

I get this result in the Mi8 with the built in NS 430 and in the YAK 52 using the 2D version. Could be similar to the KA-50's GLONASS not working if you aren't on a Soviet country? May affect other countries but I only tried Canada.

Try this version of one of the missions you posted. I set up the tanker the way I would for my missions, by using the orbit-race track option. Orbit-race track will cause the unit to shuttle back and forth between the waypoint where the orbit command starts and the next waypoint. Note that I set the duration for some long time, like 5 hours. The unit will automatically RTB when it runs low on fuel. Also note that you need to set the altitude and airspeed of the unit during its orbit. Finally, this will seem somewhat challenging because you need to be able to refuel during a turn, but it can be done.

The problem is pretty easy, look at the speed set for the tanker in all of its waypoints. It is set to 430 knots in each mission at some point after its start point. To keep things simple, the speed you set for an AI unit's way point is the groundspeed it will try to maintain on the way to that waypoint.

The latest update added a couple of range rovers for Iran and it would be cool to see them towing missiles.

Is there any way to tow the silkworm behind a prime mover? Can't find one in the editor, but it would be great and useful technology for any future towed artillery.

NO BUG NO BUG NO BUG! When I put my computer back together today I accidentally plugged the monitor into an HDMI slot on the mother board rather than the graphics card. This appears to have resulted in the system switching to a configuration where the CPU would handle GPU functions itself and the GPU was ignored. Obviously DCS was having none of this!

Attempts to load a few missions from the editor, and some aircraft quick start missions, all result in a crash which throws a crash log. The sim has not successfully loaded any mission since I downloaded today's update. Somewhat complicating things is that I installed a new all-in-one liquid cooler, then downloaded today's open beta update, not sure if that has any relevance. I've run a repair (twice) and downloaded the latest nvidia driver to try to remedy. Thanks!

Since it is a mission you made could you please share the .miz file?

Hi all, I've been working with the 9-line system to create my own mission and find it extremely frustrating. Mostly using AFAC. The following problems have been encountered: - cannot force the AFAC to designate a target in preference to others, appears to select tanks above all else and I cannot find a way to override. - AFAC will sometimes not give a mark even though one has been requested (lazer, IR pointer or WP) - AFAC will sometime call "no mark" after reading a nine line which includes "marked by lazer" - AFAC will sometimes call "laser on" but does not include the "lazing call", lazer does not appear to fire in these cases - AFAC routine will sometimes break, for example if the AFAC gives me a no-mark call I cannot engage (because I am in the harrier and he gives coordinates in MGRS which cannot be input). A call of "unable to comply" will sometimes result in a new 9 line and other times will break the script and prevent the mission from continuing. Here is the mission. My intention was to have the AFAC designate the artillery group, and if I got that working to then have him go on to designate other targets in an order that I could select. What would really help is: 1. If the AFAC could be forced to designate targets selected and be forced to use the marking method selected. 2. If units could be commanded to mark targets outside of the 9-line system, for example a target could be lazed or marked by IR using an "AI task push" 3. If we could select the format of AFAC coordinates to be either MGRS or LAT LONG Thanks, love DCS overall and this feature could be awesome with some improvements.

In one example in the mission editor I was able to get it to launch HHQ-9 missiles through a "fire at point" command, but they only fly straight up to an altitude of almost 3,000' and explode. In trying to build another mission to test this, I found I couldn't get the ship to fire at point anymore and can't figure out what was different between the two missions. Here is the mission where the HHQ-9's explode midair (they are not being shot down unless I'm really missing something that doesn't appear in the log).

So AFAC air units (at least the reaper drone I tested) will mark by IR pointer and it is visible in NVGs when flying A10-C which is really cool. Many attemps to get ground units do mark by IR pointer did not succeed. Here was the setup most recently tried: FAC unit: 1 bradly IFV Advance waypoint options ROE: Weapon hold Invisible: on Invincible: on Set frequency: 133mhz am Set callsign: Dark knight 1 FAC assign group Group ID: TGT1 Weapon: Auto Designation: IR pointer Datalink: on callsign: Darkknight number: 1 frequency: 133AM time of day was 0100. Map: Caucuses Openbeta hotfix 4 version 2.5.3.21708 I am able to contact the FAC to get the nine-line but he always gives me "no mark". Attached is the example mission.

Ok if you are the one flying, use the set internal cargo trigger to adjust the Huey weight and have the troops you are transporting spawn when you land in zone (at which point set internal cargo is used to fix the weight to empty, or whatever you want).

Other information - played today on open beta after hotfix 4 in the 342M.

If possible I think it would be cool to have FAC/AFAC units call coordinates in LAT/LONG or MGRS depending on which aircraft you are in. Gazelle, Mirage, and Viggen can only accept inputs in lat long, so if the FAC routine output was lat long if the player is flying one of these it would be very helpful.

I can post a .miz or video if needed, the problem I'm having is I've set up a reaper drone as an AFAC for the gazelle, the purpose being to have the reaper designate a target with IR pointer at night. This does work in my test mission with the A10-C. With the gazelle, after reading the nine line, nothing further happens after I select "ready to copy remarks". This prevents the CAS mission from progressing. As a side note, it would be great if the FAC's could provide lat long instead of MGRS based on what aircraft you use to contact but I don't think that's a Polychop problem. Thanks guys, loving the dixmude campaign! It was mission 3 where I saw the IR pointer in use that made me think of doing this, but I notice you used a script to get the IR pointer to appear.

Here's the mission editor, can anyone spot the problem? If I change the AI viggen to RB04's it will attack but with the 15's it continues its route and does not attack. Thanks!

Just played mission 7 on open beta, wingman did not leave the hanger. There is a C-130 that gets stuck by a stationary awacs at the intersection of taxiways echo and foxtrot near the beginning of the mission, I wonder if that is related? Possibly if people take off without doing the full alignment and start up they are rolling before it gets stuck and then the wingman follows them?

With today's OB update I am getting a lot of freezes in the mission editor but this one actually threw a crash log.

Mind posting the .lua you ended up with?

So unfamiliar as I am with the forum, didn't realize you can't send files via PM. Therefore to the guys that wrote me, here is the FMOptions.lua file from DCS 1.5. You just replace the "Eagle Dynamics>DCS World>Mods>aircraft>Bf-109K-4>FM" file with this one.

I've had a chance to work with the new openbeta version. First off, my way of getting back to the old model was to replace the FMOptions.lua file with the version found in DCS 1.5 (that I downloaded yesterday). Today's update did not change those values. After the update I compared this file to a backup I took yesterday and could see no difference. However having done some pattern work and tests I do think they made some sort of change today, I just don't know what it was. It still feels like Messerschmidts on Ice to me so I went back to the DCS 1.5 friction values.

Don't feel like I'm ever going to change minds but I'm still convinced that in these situations the 109 should tip over. But I don't care so much anymore because I figured out how to get the old model back! It now drags a wing when I ground loop :thumbup: Anyone interested in my technique PM me. A lot of friction values were changed. Some of the friction values for the tail wheel were 60%-94% reduced from their old value.

Where I say safe I mean undamaged and the pilot is not hurt. And these videos are no where near as bad as a situation where the plane lands fully crabbed! Have you flown a plane? Would you ever consider doing any landing, let alone cross wind, with your feet off the pedals?

Could I please have the files you used? I want to do this too.