ajax

See my reply in your other thread.

The fix is 7 MB zip file that gets dropped into the dcs\bazar\world\textures folder without unzipping. It's available on the 159th TeamSpeak channel. (Sorry, I don't have the address handy.) Anyway, go there and right click on the main lobby and open the file browser. Find the file and download it.

Well, it depends on how you look at it. Some of those functions can operate on your machine, such as sending messages and adding menu commands. But for trigger functions in general, yes. There are other functions that relate (or can relate) to your machine. For example, you can get location, speed, altitude, and heading for any unit in the game, including for yourself. This link is good place to see all that is available: http://wiki.hoggit.us/view/Simulator_Scripting_Engine_Documentation

Yes, indeed it is. Not quite. Some trigger-type actions are available to Lua scripts: trigger.misc.getUserFlag trigger.misc.getZone trigger.action.activateGroup trigger.action.addOtherCommand trigger.action.addOtherCommandForCoalition trigger.action.addOtherCommandForGroup trigger.action.deactivateGroup trigger.action.explosion trigger.action.groupContinueMoving trigger.action.groupStopMoving trigger.action.illuminationBomb trigger.action.outSound trigger.action.outSoundForCoalition trigger.action.outSoundForCountry trigger.action.outSoundForGroup trigger.action.outSoundStop trigger.action.outText trigger.action.outTextForCoalition trigger.action.outTextForCountry trigger.action.outTextForGroup trigger.action.pushAITask trigger.action.radioTransmission trigger.action.removeOtherCommand trigger.action.removeOtherCommandForCoalition trigger.action.removeOtherCommandForGroup trigger.action.setAITask trigger.action.setGroupAIOff trigger.action.setGroupAIOn trigger.action.setUserFlag trigger.action.signalFlare trigger.action.smoke trigger.action.stopRadioTransmission

DSPALLASVI, what you propose is unfortunately not possible. See this thread and in particular post #3 by [FSF]Ian: http://forums.eagle.ru/showthread.php?t=135987&highlight=cockpit+arguments+lua The gist of it is that the X:COCKPIT functions are not available in the scripting environment. [url=http://forums.eagle.ru/showthread.php?t=135987&highlight=cockpit+arguments+lua][/url]

Could've been that long ago. I haven't worked on any missions in a while. Thanks for the confirmation, at least I'm not nuts. (Well, I guess that's debatable.)

Has the ME changed how it displays the start time for a unit? I'm referring to the text boxes for entering [hours] : [minutes] : [seconds] / [days] on the waypoint dialog panel. The [days] box used to be the offset since the mission start date as defined on the briefing panel. The initial value was always 0. Now it contains the offset since the "standard" DCS start date of June 1. Has anyone else noticed this?

1st Line is latitude: 42097 = 42 deg 09.7 minutes (the 1 is the WP or TGT PT.) 2nd Line is longitude: 042237 = 042 deg 23.7 min Latitude requires one less digit because latitude only ranges between +/- 0 to 90 deg. In contrast, longitude can range between +/- 0 to 180 deg.

I don't think that's right, StrongHarm. To enter 44 deg 45.46 min into the PVI-800 you enter 44455 (rounding 45.46 to 45.5). Unless you really meant 44 deg 45 min 46 sec, in which case you're right.

It is the default value for the AWACS display. If set to "off" then no information is displayed (depending on the setting of the next variable, awacs.awacsWarning). If awacsWarning is set to "on" then when an enemy aircraft gets within the specified range, it will be displayed regardless of the setting of awacsDisplay. So, if you want to totally disable the display, both awacsDisplay and awacsWarning need to be set to "off". Note that these are default values. Each client can set them the way they want.

That's good to know. Thanks.

Also, I thought the function requires the flag to be a string, e.g. trigger.action.setUserFlag("19",1)

You can also use the ERBL TO function. After you set a TO location, the "glide slope" is displayed at the bottom center of the ABRIS (the area labelled BHAB). It is terrain-following, so don't overreact to the cues. Edit: On the NAV page, that is.

Did you enable allow_object_export in your network.cfg file?

Good question! I've spent a lot of time over the past few days trying to spawn a FARP. I can spawn all the associated static structures (tent, command post, ammo dump, etc.) but not the FARP itself. Apparently, a FARP is not a 'static object'. A FARP will not be returned if you use StaticObject.getByName(), Group.getByName(), or Unit.getByName(). However, Airbase.getByName() will return a FARP. So, even though a FARP is added in the ME as a static object, DCS treats it differently. (And it stands to reason it would... it has warehouse properties, radio comms, etc.)

I've recently run across a problem where some dynamically spawned groups (a mortar team, specifically) are no longer controllable via the F10 map view. It used to work fine in MP -- now it does not. Also interesting is that everything works fine if they are controlled from the MP host, but commands issued on a client machine are ignored. This indicates to me that there is nothing wrong with the script, but rather something has changed in the scripting engine. Does anyone have a clue what might be going on?

Don't you love it -- it'll make you pull your hair out, eh?:)

Look in {DCS}\FUI\Fonts. Backup font_default.tga and font_default.txt . Make copies of a larger font, say, font_arial_17.tga and font_arial_17.txt . Rename them to font_default.tga and font_default.txt, respectively. This may affect more than the chat text. I don't know.

Ez-Ian, I don't believe your suggestion will fix the problem... at least it did not for me. Did you do your testing as the host? The problem only affects remote MP clients. If the script is run on the host, then the script works as expected without crashing.

I use the CH Fighterstick for BS, and I'm very happy with it. I use the pincky button for trim. One thing I particularly like is the x and y adjustable pots -- helps fine tune the Shark's attitude.

The Palm Springs Air Museum is pretty nice.

I found the thread I was thinking of: http://forums.eagle.ru/showthread.php?t=136826 But it turns out it is related to sending messages to CA players not getting userID.

I had trouble setting initial heading as well. I don't know if you're doing this or not, but there is a unit parameter 'psi' that needs to be set to the reciprocal heading. I did it like this: ["psi"] = -heading,

I recall seeing a recent thread where it was mentioned that Mist was able to get CA names. Sorry, I can't find that thread at the moment. Perhaps looking through Mist code might help.

That was in dOoOm's thread: http://forums.eagle.ru/showthread.php?t=133953