Jump to content

OzDeaDMeaT

Members
  • Posts

    153
  • Joined

  • Last visited

3 Followers

About OzDeaDMeaT

  • Birthday 01/18/1978

Personal Information

  • Flight Simulators
    DCS
  • Location
    Canberra Australia
  • Interests
    Fast jets, fast cars/bikes
  • Occupation
    Systems Architect

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Thanks mate, if you guys need any UI testing or feedback please keep me in mind.
  2. so was able to verify that -w "PROFILENAME" still functions correctly as a shortcut, but selecting the different profiles seems to only load the DCS.openbeta folder even if there is another path specified.
  3. So I have only recently wanted to use two different profiles in the Launcher. I have saved the app config and when i load it back up, it shows the specific profile paths I want to use with that specific slot, but when i load the game using the "Launch VR OFF" button it seems to create a profile in DCS.openbeta. Is there a way to stop this form doing that?
  4. This has been a problem since the very first version of DCS World. Colour me shocked that you were unaware of this problem. It is incredibly well known in the DCS World content creator corners of the internet. I have attached two missions showing the issue, the AI doesnt even make it over the bridge one. No Scripts, just DCS Ground AI doing its best, hopefully now that we have brought it to your attention we can get this fixed. If anyone has simple examples of these AI Bridge problems please post your examples here. Try not to use scripts, keep the missions as simple as possible. BridgeStuck_01.miz BridgeStuck.miz
  5. People could still use Skatezilla if they want the more complex stuff available, Skatezilla is more a manager and not a launcher. Liveries, Missions, Mods etc etc, sounds even more complicated than Skatezilla's is already. Not sure we need that for a launcher that you know, launches the game.
  6. I completely agree that the team over at Hoggit do a fantastic job. To my understanding, they do rely on information from Eagle Dynamics developers on changes or new features like the warehousing system. (I understand @Grimes was involved in the development of these features as well which is a fantastic nod to someone so dedicated to the DCS scripting community). I also agree that the documentation supplied by Eagle Dynamics (ED) is subpar, out of date and in dire need of some love and possibly a restructure. We can all get on the "Please suck less at documentation ED" train but frankly I don't think it's constructive and will change nothing. I love this sim, I taught myself Lua over the last 6 months with a laser focus on getting good at DCS Scripting so I could make my idea of what a persistent mission should look like.(with patience from the Hoggit guys and other people in the DCS API community) We also need to acknowledge the elephant in the room. Writing DCS API documentation does not make ED any money. We have "managed" with what we have been given, and it has been deemed "good enough" for 15 years now. It is up to us to show we are mature enough to provide meaningful and productive feedback. I believe the best way to do this is with a centralized forum location for us all (including ED Staff) to have these conversations. I have also experienced first hand several times the inconsistency between patches of API commands. This is quite frustrating but lets be honest, mistakes happen and bugs are introduced. One of the big things I think a Forum could help us with is calling out undocumented API changes that break functionality. There are API inconsistencies, the EventHandlers are a fantastic example of what I can only describe as Russian Roulette every time a patch comes out. This really does need to be addressed, but those are internal engineering and code versioning issues, not really the scope of what I am trying to put forward. This also isn't my first rodeo, I was a community contributor with Bohemia Interactive from the Operation Flashpoint days all the way through to Arma 3 and even did work for my Government using the Military Simulation product VBS and VBS2 and VBS3, all are amazing success stories. Bohemia IMO are the benchmark in community interaction and support with both great documentation but even more critical to that, they listened to their community when shortfalls and gaps where discovered in their API. It's important to remember that Bohemia Interactive didn't have a wiki for their commands in the beginning and the company produced Command Reference wiki really only came online around Arma 2 's release. The early 'command references' were maintained by us 'the community' for YEARS before they saw the value in it maintaining it themselves. Long story short, lets start an honest dialogue and get some support from Eagle Dynamics to make the DCS API environment(s) better for everyone. Better documentation, code examples, open up some conversations with developers about some of the holes in the current API's that us as a community would like to be filled or fixed.
  7. You can create random explosions pretty easily in a zone or polygon. You can even find buildings and explode them based on type. I wrote a function for a friend that destroys all the bridges in an area.
  8. A simplified Skatezilla Launcher would be fantastic. Also having links to news letters, patch notes etc. But I think being able to execute the game external to the launcher would also really need to be a requirement. TLDR; Optional == Good
  9. already requested a few years ago. https://forum.dcs.world/topic/289887-option-to-not-scale-the-text-boxesf10-drawings-with-zoom/
  10. Yeah, I am talking about multicrew specifically. This can not currently be done.
  11. As we see more and more multicrew modules become available, it is becoming apparent that there is a gap in the DCS API that does not allow individual players (in a multicrew aircraft) to interact with the game. I would like to propose a SLOT based commands. The purpose of this is so it would allow an individual player to have various aspects of the user interaction experience with DCS be customizable to that specific user. I propose a variant for the following DCS Mission Scripting Environment API commands: Adds a command to the "F10 Other" radio menu allowing players to run specified scripting functions for a specific player missionCommands.addCommandForSlot(number slotId , string name , table/nil path , function functionToRun , any anyArguement) missionCommands.addSubMenuForSlot(number slotId , string name , table path) missionCommands.removeItemForSlot(number slotId , table/nil path ) add / remove OtherCommandForSlot would allow specific players to interact and customize the game or request information specific to them. trigger.action.addOtherCommandForSlot(number slotId , string name , string userFlagName , number userFlagValue ) trigger.action.removeOtherCommandForSlot(number slotId , string name ) outTextForSlot would be amazingly useful to allow specific players to receive information from the game and not interrupt other members of the crew. trigger.action.outTextForSlot(number slotId , string text , number displayTime , boolean clearview) outSoundForSlot would be very handy, if a member of a crew wanted to get notifications for something that other crew members would not be interested in. trigger.action.outSoundForSlot(number slotId , string soundfile ) markToSlot would allow for marks specific to a player be available. trigger.action.markToSlot(number id , string text , table vec3 , number slotId , boolean readOnly, string message)
×
×
  • Create New...