Habu_69

F/A-18C radar page appears to display incorrect bullseye data. Attached MFD image shows my BE position as 350/44.7, which would be approx correct if BE were at WP2, south of me. BE is actually placed at WP3 (see SA page) north of me. On attached map image I am near the F14A and BE is at WP3. DCSW OB 2.5.4.28615. Track attached. I5 8600, Nvidia GTX 1070, 16 GB DDR3.

Certainly the ME is a powerful tool in itself and can accomplish most of the behaviors that scripting can. Scripting has 2 advantages, I think. Once learned, scripting can do more with less; and it is more CPU-efficient. Also, good script fragments are available for use in other missions. But, hey. Different strokes for different folks.

Tx, that is where I have it. Will re-download and reinstall.

Doh! Thanks. I have 2 blue bases, Soganlug and CVN. I had been clicking on the base icons with no success; however, clicking on the Base name TEXT does the job!

For mission creators who may not have yet discovered the power of scripts, I offer this simple example, using MOOSE in this instance: BanditWP = STATIC:FindByName( "My Static" ) BanditWPVec2 = BanditWP:GetVec2() -- location spawned aircraft will fly to MyAircraft = SPAWN:New( "My ME Aircraft") :InitLimit( 4, 1 ) :InitRandomizePosition( true, 60000, 40000) -- Radius band in meters :OnSpawnGroup(function (SpawnGroup) SpawnGroup:TaskRouteToVec2( BanditWPVec2, 600 ) -- Flight destination and speed km/hr. end ) MyAircraft:Spawn() These few lines will spawn one group of up to 4 aircraft (set to LATE ACTIVATION in the ME) at a random position within a radius band of 40000 - 60000 meters from its ME position and direct its flight path to "My Static's" location. Very handy for introducing a bandit at a random location. Script could also easily randomize spawn timing and type and number of aircraft. I have no previous coding or scripting experience, and while I am far from a scripting guru, I have become literate in the basics,

Selected static structures have missing textures. I noticed same with some of the Caucasus airfield templates.

TYVM for your helpful RTFM suggestion. In fact I have RTFM and am still stumped. According to the manual I can not figure out how to get to the BASE MENU so I can purchase an aircraft. My screen image shows no BASE MENU button and nothing I click on brings it up. Is my install FUBAR'ed? Am I missing something patently obvious to everyone else?

Lowest I have been able to get fighters to fly is about 500 ft.

I have placed 3 groups of 2 (4 F/A-18C, 2 F-14A) on the Stennis deck hot for takeoff. I placed an AI on each of the 4 cats and set Player group ON RAMP HOT. The ME shows the Player group off the deck over the sea, BUT in game, Player group is on deck aft of Cat 1 blast deflector. DCSW 2.5.4.28615.

Speculation abounds regarding the new Rift S model, which is believed will feature a camera-based or eye-tracking view orientation system, instead of IR sensors. If so, will these finger-pointing control devices still work?

I would like to explore this mission generator, but I can not get a flyable mission generated. A next-mission.miz generates, but has no blue aircraft other than a tanker. Attached screenshot of Mission Menu shows no aircraft units. Something must be wrong. My DCS OB is not in User Saved Games folder, so I modded the start.bat appropriately. Must admit I did not read all 32 pages of this thread.

Static. Have not checked Dynamic for any changes.

The newest .28461 OB version release appears to have improved rain and overcast cloud effects. Rain appears heavier, raindrops on canopy more pronounced, overcast a little denser.

Well, I also experienced wonky ME following .28461 update. Many missions would not load into ME, although they all flew just fine. DCS would completely freeze trying to load some missions. I suspected some new issue with one of the many mods I have installed, so I disabled all mods and began reinstalling one at a time to ID the culprit. Process is lengthy because you must close/restart DCS for each reinstall iteration. After reinstalling all my mods, I never found the issue and now all missions load in ME as expected. Very strange!

Shouldn't this mod's components go in mods\tech folder?

Remarkable improvement in OB in MFD display, as well as HUD! All Rift users should employ this.

Good stuff. I have had reasonable success with using F-16 Bl 50 SEAD on the shorter range SAMs (SA-15 for example), but not so much on SA10, SA-11.

Sensor Control Switch - Depress is a NEW keybinding included in the most recent OB update. Any older custom default.lua file will not include it.

From MOOSE docs: SPAWN.InitLimit. SPAWN has 2 kind of limits: The maximum amount of Wrapper.Units that can be alive at the same time... The maximum amount of Wrapper.Groups that can be spawned... This is more of a resource-type of limit. So :InitLimit( 2, 20 ) -- A max of 2 units can be alive in DCS and a new group will be spawned up to 20 times.

A/A TACAN: 37-63(X or Y). A-G TACAN: 30X-46X, 64X-99X, 30Y-63Y

You might consider upgrading the stick with RealSimulator force feedback mod to replace the gimbals. Cost probably similar to new Warthog set, but with Warthog you would also have the dual throttle and all those extra switches. It is also possible that the main PCB in the stick has become defective. Happened to me for no apparent reason, but the defect only affected inputs from the throttle. Solution: Warthog throttle. Good luck.

Silicone bump is a good idea. I use a small piece of velcro hook-side for same purpose. That tactile cue works quite well.

TX.

What .lua file specifies which aircraft are available for each country in ME?

I don't believe MIDS voice function is implemented yet.