Jump to content

St3v3f

Members
  • Posts

    499
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by St3v3f

  1. Not tested, but this should do: mist.getMGRSString{ units = {'Unit1', 'Unit2'}, acc = 3 } mist.getLLString{ units = {'Unit1', 'Unit2'}, acc = 3 } mist.getBRString{ units = {'Unit1', 'Unit2'}, ref = coalition.getMainRefPoint(coalition.side.RED), alt = 15000, }
  2. It's not throwing any error message at me, but I still can't get it to work. trigger.action.radioTransmission('message.ogg', trigger.misc.getZone('New Trigger Zone').point, 0, false, 124000, 100) I tried both 0 and 1 and the soundfile is definitely in the mission Anything stupid that I am missing here?
  3. Might be too late now, but for the future, I'd suggest not to delete the installation files. It's never a bad idea to have the install files of the current main version on a flash drive or external hard disk
  4. The # operator only works with numbered indices up to the first nil value. tab = {a = 'v1', b = 'v2', [2] = 'v3'} #tab == 0 tab = {a = 'v1', b = 'v2', [2] = 'v3'} tab[1] = 'v4' #tab == 2
  5. Maybe Joyride wants to use a triggerzone created in a script for script functions that use names of triggerzones as an argument. I would certainly see the use if Mist functions could accept "raw" data for triggerzones as well as names
  6. Same for my DCS A-10C retail key
  7. Ah yes I see what you mean now... Sorry, I don't know how / if it is possible to insert a new zone. Would certainly be useful
  8. TriggerZone = { point = Vec3, radius = Distance } So you can simply create a table with the appropriate fields and call it a trigger zone :) zone = { point = {x = 123, y = 234, z = 345}, radius = 10000}
  9. The dcs.log contains valuable hints to why a script dies. In your case it reads: 00762.067 UNKNOWN MissionScripting::initialize: mist.scheduleFunction, error in scheduled function: [string "C:\Users\St3v3f\AppData\Local\Temp\DCS\/~mi..."]:96: attempt to index field 'DBS' (a nil value) Go to line 96 and replace DBS with DBs After that, it will die with: 00865.217 UNKNOWN MissionScripting::initialize: mist.scheduleFunction, error in scheduled function: [string "C:\Users\St3v3f\AppData\Local\Temp\DCS\/~mi..."]:97: attempt to concatenate global 'zone' (a table value) zonesByName returns a table, not a string. So to get the zone's name, just append .name to zone in line 97
  10. You can also use env.info(string, false) to log into dcs.log. Setting the boolean to true will also create a popup window
  11. I am having an issue with creating a radio transmission in a script: From the wiki: function trigger.action.radioTransmission(string fileName, Vec3 point, enum radio.modulation modulation, boolean loop, number frequency, number power) Problem is with the modulation. Neither the documented enum radio.modulation works (global value radio is unknown), nor calling it with true or false as posted here works. What is the correct syntax here?
  12. Thanks, I hope you can think of something :thumbup:
  13. Is there any chance of adding an optional soundfile argument for mist.message.add ?
  14. I'm getting into mission building using scripts and have made some good progress. Now I want to get a unit's speed and I am unsure about how to do that. Using my somewhat rusty bits of math, I would go with something like: speed = Object.getVelocity(unit) speed = math.sqrt(speed.x^2 + speed.y^2 + speed.z^2) Is that correct? If not, how does it work? And on this note: Thanks to Grimes and Speed for their contribution with MIST and Slmod and the scripting documentation on the wiki! :thumbup: Edit: Another question that came up: I want to build an event handler, that reacts to pilot ejections. The function is properly called with event.id == world.event.S_EVENT_PILOT_DEAD, but I can't seem to get the unit that ejected. I've tried event.initiator, event.target, and event.place, but they're all set to nil. Any way to do that?
  15. I have the same issue, SA-11 Search Radar does not appear on A-10C RWR. It appears however in the F-15C and the A-10A BEFORE it is deployed. And it also WORKS before being deployed.
  16. Yes, it's really helpful :thumbup: One thing I though about though: You oftentimes have players with cyrillic letters or other special characters in their names. With that, it's pretty much impossible with a western keyboard to kick or ban them. So my thought would be, if it is possible to add a similar menu to kick and ban as there is for load. Example: -admin kick To kick player "Goose", type -kick 1 To kick player "Обсуждение", type -kick 2 Thanks for creating and maintaining this tool!
  17. It's not that your idea is bad, using all available resources is a good thing. But not only is it not a new idea and has been brought up many times, you also make it sound a simple thing to do which it is not.
  18. Modern GPUs have hundreds and are getting towards having thousands of Cores :)
  19. Just on the topic of CPU vs. GPU Don't overestimate the power of GPUs. Of course they have more flops than CPUs and they are a lot faster calculating some stuff. But think, if they were as awesome as you make them sound, then why does Intel still exists? Why hasn't Nvidia taken their place, after all, their GPUs must be so much better than the Intel CPUs? The answer is simple. Because they aren't. GPUs have their strong point in performing the same operation many times simultaneously. That's what they're build for. You have many many pixel that need to be calculated and you perform the same operation with different input on all them. CPUs are universal. They don't parallelize things. But they have a significantly higher clock rate. And that means that they are faster in performing operations that influence each other. If the output of one operation is required as input for the next one, you can't run the second one before or simultaneously to the first. That is the weakness of GPUs and that is why we still have our Intel or AMD clockwork.
  20. You should be able to call a tow truck that brings you back onto the tarmac though :D If you get off the tarmac, these are some important points: 1. Don't stop, keep moving until you are back on solid ground 2. Be easy on the brake 3. Be easy with the steering If you keep that in mind, you can usually get away with it.
  21. Looks like the effect from copying standalone configs to DCSW. Try deleting your Saved Games\DCS\Config\Input\A-10C folder and set up the controls from scratch
  22. Infantry does attack a Ka-50 who is unlucky (or stupid) enough to fly slow and close to them. And even though they don't hit hard, they can be lucky and hurt you seriously, taking out hydraulics for instance.
  23. - DCS does not use multiple cores? correct (except for some sound stuff that is running in a seperate thread) - Setting the affinity dedicates a core to a process? No, it limits the process to certain cores. Huge difference
  24. And please fix the repair of Doppler Nav, HUD and Intercom :)
×
×
  • Create New...