Habu_69

I think original poster is trying to lase map building, not a positionable static building.

Observed bug in DCS command switchWaypoint: AI will follow switched flight plan waypoints 1 less than scripted. If script is written (3, 7), AI will actually fly ME flight plan waypoints (2, 6). However, if the new switched WP, as scripted (say 8 in the script, relating to 7 in the ME) is a LANDING WP, the AI ignores the command switchWayPoint altogether and simply follows the flight plan. Probably related to the ancient bug of AI reporting passing 1 WP less than actual location and involves WP numbering starting a 0.

:thumbup: Apoplectic!

Mod seems to function properly. Log errors disturb my aura.

Copied mod folder to saved games/OB/mods/tech. My log file shows many errors with M203 mod relating to lack of texture folder. A few examples: Can't mount e:/game data/saved games/dcs.openbeta/mods/tech/m203soldier/textures. there is no directory e:/game data/saved games/dcs.openbeta/mods/tech/m203soldier/textures.edc ZipDriver: Can't open zip archive e:/game data/saved games/dcs.openbeta/mods/tech/m203soldier/textures.zip.

My testing indicates the delay parameter does not work when a sound is called from a script. Too bad. Timer method serves for this purpose tho.

Anyone noticed the new "START DELAY" parameter for trigger.action SOUND TO? I wonder if the parameter will delay the playing of a sound when triggered by a script. I plan to test.

Sure, Notepad++, or any good text editor, will function adequately to edit .lua scripts. As a very novice script writer; however, I found Lua Development Tools, with the intellisence feature, an extremely helpful aid.

91 should be the line number.

Give your spawn group a waypoint with advanced action like SEARCH IN ZONE.

Be sure A/P Disengage switch is not accidentally on.

I find the aircraft very difficult to control after releasing a relatively light-weight AIM-9, especially pronounced while dogfighting with no AG weapons loaded. I certainly recognize that the missile release results in asymmetric wing loading, and roll trim does mitigate the problem somewhat, but, wow, I really have to work hard to regain control and the nose wants to wander all over the place. Has anyone encountered this issue and learned how to overcome it? Maybe release 2 missiles, wasting 1.

Seems you could use an EVENT.OnLanding method, then Destroy() the unit.

I have found this little key binding mod quite useful, but it has quit functioning. Must be due to either some change in my setup or a change in DCS. I can't find where I downloaded the mod from Can anyone help me?

What is the point? Submarines are invisible and have no function in DCSW.

Today's update to 2.5.4.29167 includes a new ME trigger zone function. It looks like a table of some sort in the parameter window where you set zone color and size. Any ideas??

Quick search for "weather" in this forum found a dozen threads including this one: https://forums.eagle.ru/showthread.php?t=235395&highlight=weather

Have you tried: GROUP:GetName() Inherited from Identifiable. Recently used this in a script: RedBandits = SPAWN:New( "Red Interceptors" ) :InitLimit( 8, 2 ) :InitRandomizePosition( true, 120000, 75000 ) :OnSpawnGroup(function (SpawnGroup) SpawnGroup:TaskRouteToVec2( BanditWPVec2, 600 ) end ) Sets WP for spawned group to BanditWPVec2 location.

Cockpit instrument clarity is paramount for me. Currently the Rift displays all the new F/A-18C radar and SA contact D/L and IFF data as a colored blur. Not good enough for "serious" combat. High hopes for the Reverb.

This works for me in Moose: SpawnGroup = GROUP:FindByName( "My ME Group" ) BanditWP = STATIC:FindByName( "RAILYARD BLDG Vec2" ) BanditWPVec2 = BanditWP:GetVec2() -- Map position for bandit WP SpawnGroup:TaskRouteToVec2( BanditWPVec2, 600 ) -- Speed km/hr. Default = 20

In DCS either X or Y TACAN mode will function correctly for aircraft; however, in US military, AFAIK, refueling aircraft are assigned Y mode.

No issues for me under DCS 2.5.4.28841 installed in Saved Games\DCS\Mods\tech. Maybe try new download from here and reinstall. https://www.digitalcombatsimulator.com/en/files/3301580/

I have created a few naval fire mission scenarios. This advice was posted in an earlier thread: Also, here is a Moose script that works: Ship1 = GROUP:FindByName( "UK_Ship_1" ) Target = GROUP:FindByName( "Fire Group" ) Zone_Vec2 = Target:GetVec2() SCHEDULER:New( nil, function() -- Trigger for the fire mission: if trigger.misc.getUserFlag( '44' ) == 1 then Fire1 = Ship1:TaskFireAtPoint( Zone_Vec2, 160, 20 ) -- Define Ship1 gunfire task (point, radius m., ammo count) Ship1:SetTask( Fire1, 5 ) -- Actuate Ship1 gunfire task, 5 sec delay. end end, {}, 15, 2 -- Run schdeuler after 15 sec delay then every 5 sec. ) Someone listed these gun ranges: Ticonderoga 14.5km Perry 14.5km Moscow 20km Neustrashimy 21.5km Rezky 21.5km Albatros 6km Molniya 15km

At this point I would certainly wait on release of the HP Reverb FR Pro. Early reviews indicate significant leap in resolution.

On reflying this mission, it is quite apparent that BE data is being reported in error from WP2. I believe the BE was located at WP2 before moving it to WP3.