Mirknir

Careful, 124 Mhz, that's a lot of hertz for such a small plane :lol: Go get those evil F15s tiger :smilewink:

In Map: Open Conflict Tuapse - v3.0.2 Hello darkness, my old friend Switch weather and time frame to a late winter evening going into dusk The session should end in the dark instead of starting with it. L39 Channel 0 have be set to 124Mhz, the AWACS frequency. They should now be able to access report more easily My knowledge of the L39 is not enough to test it, tell me if it fixes your problems

Nope, still almost full. However, next reset might be a full restart so I can push an update.

Don't forget you can check f10 map or your instrument to get the local time of the server and have an idea of where the sun is going. At the moment, the time frame is about one hour before dawn. I will change it to 3h before dusk to have the one hour more dark at the end of the session. The current time frame offers more dark that I wanted for one reason: crashes. When it crashes, the server at the moment reset to darkness. With the changes I want to do, a server crash will just remove some darkness instead of adding to it. I am not sure if it makes sense but yea the next timeframe will go in the night instead of from the night. :thumbup:

Thanks man, I really needed that today :thumbup: I am glad all you heli-pilots like these features. As a fighter pilot, I kind of coded them in the blind hoping this will add interesting content for helis lol. For the dynamic weather, I am glad you like it ; it was a pain to get something I felt comfortable shipping and I decided to re-use an early weather pattern from OC. It's hard to control random :)

Lets see how it goes first :helpsmilie:

In Masterscript: Skynet v3.3.3 Broken Unit Tracking Fix a bug in the 'Mistaken Identity Fix' that happens after a reset When the server reset, map units spawn before Skynet has registered its event handler and is able to receive the birth event. This leads to units being unknown by the script. Without object tracking, nothing would work properly including intel report and kill log Skynet will go back to using the untrusted DCS.getUnitProperty function for like the 1 min it takes for its event handler to register. Don't hesitate to report more unforseen consequences ; these changes affect the core of Skynet

Ok thanks for the report. I am surprised ; these the major issues didn't appear in my tests. Something must be different live ; I ll investigate :thumbup:

In Masterscript: Skynet v3.3.2 Mistaken Identity Bug Attempt a fix It's a difficult fix, some unforeseen consequences could happen Please report issues with a external screenshot of your aircraft with the '-me' popup displayed In Map: Open Conflict Tuapse - v3.0.1 Switch to dynamic weather Wind speed is thus a bit more out of my controls Both side may not have the same weather Please report problems

Thanks for all the pictures doods, I like to see how cool or messed up the server can become :thumbup: It brings some cheese to go with the whine :lol: Speaking of messed up, this weekend I will ship a potential fix to maybe attempt to kill the mistaken identity bug. As you can tell but my wording I am confident it will work. ------------------------------------------------------------------------------------------------------------------------ Because people sometimes asked me for more details about the behind the scene, I will now explain boring stuff. You will then understand in detail how Skynet tracks you, your family, your cats and buy AI porn on internet with your credit card :P When you join the server or any server for that matters, your connection gives the server your IP, your username and your unique ClientID. That's your ID number 1: the UCID This is the ID by which Skynet references you and that's how the script will always find your stats and your ban status even if you change IP or name. ----------- When you are given permission to enter the server, you are given a slot ID, from 1 to max player number of the server. Slot 0 is the host. That's your ID number 2: the ServerSlotID This is the ID by which Skynet references you to the server environment to do server related stuff like: the ban, kick, get ping, send chat functions. ----------- When you join an aircraft, you join a seat in an unit in one of the playable group I put in the mission. They are defined as well as made unique during the mission edition and will not change during the game. "Player A10C @ KRY6 - Boise" will always be GroupID 438 - UnitID 577. That's your IDs number 3, 4, 5: The MissionIDs Those are the IDs by which Skynet references you to the mission environment to do mission related stuff like: send sound, send text popup, populate radio menu, retrieve your radio selection.... ----------- Then when you actually spawn; DCS creates an instance of the aircraft and this aircraft is given what I call a RuntimeID, meaning an ID "unique" to your aircraft. If you get killed and just respawn in the same slot, a new instance of your aircraft will be created and a new RuntimeID will be given to you. That's your ID number 6: The freaking RuntimeID This is the hardest to track because it changes a lot and sometimes, the same runtime ID can be reused. This is the source of the mistaken identity. This is the ID by which Skynet will identity your aircraft in the world, associate the weapons fired to the aircrafts, get your speed, position, altitude, your airborn status.... That's what makes a lot of deep feature possible like rescue / capture / explosives.... Long story not short, I need to maintain all these IDs and many more information per players using different sources, from DCS functions, callbacks and events to sometimes to just geometric guessputation. The function responsible from the mistaken identity is: m_ObjecRuntimeID = DCS.getUnitProperty(m_ObjectMissionID, DCS.UNIT_RUNTIME_ID) This function tells me what is the current RuntimeID of the current aircraft spawned for a MissionUnitID so that's why it's so central and hard to bypass. My fix is to stop using it and rely purely on BIRTH events to maintain the player RuntimeIDs. It "should" work as long as the messages are reliably sent and so far, in my tests, even if they can take some time to come, it seems like they always come. You might experience a bit more delay before your registering to Skynet (the welcome popup) and worst case scenario, the server will explode. ------------------------------------------------------------------------------------------------------------------------ I have also updated the '-me' command to display more information about this so I can debug better in case new problems emerge. So starting from Saturday, if you have the mistaken identity bug, please screenshot the '-me' command text popup and post it here. It will look like this:

I expect screens :)

Might wanna pack some NVG :music_whistling:

Server should be back on and updated to last version with your Mistral thingy :thumbup: Windows 10 is still being a huge pain and doesn't want to update but fudge-it :angry:

Yea I would also prefer your explanation:helpsmilie: Working on restoring the server. In the meantime, look at this (not safe for work - happy ending!!!)

Nope, I said CAP zones. Helicopter pilots are too much of trolls to have the CAP ignore them :lol: It's working as intended! The Deep Assault Convoy is ... wait for it... an assault convoy that goes deep into enemy territory. Following it will cause you to invade enemy CAP zone and take missiles in your face :thumbup: I am trying as much as possible to use accurate name ; in Open Conflict, Operation "Desert Storm" would be called Operation "Save 'Dat Oil".

I removed it when it was unstable and crashing the server a long time ago. Never had the courage to do the experiment again :lol: I am not sure I understand this request. The objective system can display you in metric or imperial system (-opt unit). You can also ask for a detail report and it will display you the grid and lon/lat coordinates of non moving targets (-ag <objectiveCode>). I am not sure what other coordinates there are except spherical coords from the center of the earth :)

Yea I used to isolate and report them but never have I received an answer or a fix so I kind of opted to bypass the bugs as much as I can. So far, I've managed to bypass most of them and create a guesstimate algorithm to compensate for others :thumbup: Thanks, I appreciate the support. Yea, I am soon to do a map update. ok might not be an actual quote but I wanted to know if the new AI zones are better for the couple of weeks? Do you feel you have more space to express your feelings and kill each other without AI intervention? Thanks Your absent Overlord

"huey is life!" *takes a bullet in the face :music_whistling:

As I've already said, there is a mistaken identity bug in skynet I am working on. DCS API is getting more and more unreliable as they update the game. Usually, the problem is missing information in events but since 1.5.4, the API started to give me wrong information. I am working on a work around but it's not easy to untrust an official function. I know what's happening so I don't need more information on it or a post each time it occurs. It's just a matter of finding a fix that causes less problem than the bug. I know it's frustrating but it is for me too ; Open Conflict is like one more official broken function away to lose key features. As usual, I'll keep you guys posted thru release notes :thumbup:

There is an elusive mistaken identity bug that Skynet have due to a DCS function giving me false results. I am working on it but it's not an easy fix to bypass a DCS function. Sorry for the inconvenience. Stay tuned!

Even if I recognize the accomplishment, I don't want this to be a thing and I think everyone can understand why. FOBs are not designed to be a target and Open Conflict is designed to welcome everyone, not just hardcore players that enjoy missiles in their faces on spawn. Repeated sneaking to and attack against the enemy FOBs will be considered trolling and will be fixed with more defenses and more AWACS cover. I know it's the conflict zone so everything should be fair game but there are fine limits because of the way I made Open Conflict. I chose to put every planes on both side and let everyone go to the team they want instead of activating my 'go to the weakest team' algorithm. This enjoyable freedom of starts often lead to unbalanced team and thus, I added protected zone, more SAMS defenses and AI CAPs to offer minimum help for everyone. Whether it's an accomplishment or not, whether the accomplishment was mitigated by stacked team or not, I just don't want people to get shot on their spawn points ; at least not repeatly. Again, I hope that's not a server breaking rule for you :P But don't get me wrong, I enjoyed watching the video (once I muted it) but I need to maintain a certain balance to the server and safety to the spawn zones. I guess I have to come back to do blue CAP because no-one is doing the job :) I hope you guys will understand it :thumbup:

In Map: Open Conflict Tuapse - v2.9.8 Come autumnal rain and wash away from my Server, That saddest of all Words: Bug

Yea the AWACS are further from CZ than before. However, I also want to balance the AWACS detection range with the abilities to hide because that's what made the su27 so deadly in Khashuri. Deep valleys and good AWACS detection. Tuapse is flatter as a map so I don't mind having more AWACS detection than in Khashuri especially since the lack of deep valley make the F15 a bit stronger with their nice radar.

Nope, if you go to deep in enemy territory and in the AI CAP zone, it's normal that you get engaged and without support, killed. In the past, I've already setup AI to not engage helicopter and it ended up bringing more trolling than usual by helicopters. Sorry. However, I will check the CAP zones to make sure they leave spaces to have fun like it was also requested by fighters :thumbup:

Free Time Interrupted Hey guys, So recently, my situation has changed and I wanted to explain what's going on: I had to move because of Dust stalking me. hehe no, I actually got a new job! I am now cheating on Skynet and using my programming skills to develop a big ass game with an awesome team. I know what you guys are going to ask: "Can we kill F15s in the game you are making?" And the answer is no. Basically, that's why my presence in game and on the forum has been reduced. This and my family visiting. There you go, you guys now know what's going on and even if I know this doesn't satisfy your hunger for fixes and R73s in the face, I hope this will soften the burn of waiting. But the fixes and the R73s will come ; that's the good news. I hope you guys have fun!