Jump to content

microvax

Members
  • Posts

    1300
  • Joined

  • Last visited

Everything posted by microvax

  1. Noice =RvE=MicroVAX KA50
  2. Reserved for Future Use Current Toaster: PACT role assignments No15 gets 2 x high end fighter [Flanker family] 4 x mid tier fighter [Mig29, M2Kc] 1 x CAS/SEAD/strike [AJS37 or SU25T] 1 x Transport helo [MI8 5 lives] [bB] gets 2 x low end fighter [Mig21 or AJS37] blokovchan (lonewolf) gets 1x high end fighter [Flanker family] =RvE=Krippz (lonewolf) gets 1x CAS/SEAD/strike [AJS37 or SU25T] Darkwolf (lonewolf ?) gets 1x lotatc slot as GCI Pact slots remaining in wave 2 : 1 x high end fighter [Flanker family] 4 x mid tier fighter [Mig29, M2Kc] [Plox consider flying mig29] 2 x low end fighter [Mig21 or AJS37] 6 x CAS/SEAD/strike [AJS37 or SU25T] 1 x Transport helo [MI8 5 lives] 2 x lotatc 1 x Combined arms NATO role assignments IRIAF gets 4 x high end fighter [f15c or F14, just in case] 2 x SEAD simulator [sU25T] 104th gets 4 x mid tier fighter [M2Kc or f/a-18c] SF gets 3 x mid tier fighter [M2Kc or f/a-18c] Team Tricker (lonewolf group) gets 3 x low end fighter [f5E] Turborush (lonewolf) gets 1 x mid tier fighter [M2Kc or f/a-18c] sydy (lonewolf) gets 1 x mid tier fighter [M2Kc or f/a-18c] Dedde (lonewolf) gets 1x lotatc slot as GCI NATO slots remaining in wave 2 : 1 x low end fighter [f5E] 4 x CAS [A10C or AV8B] 2 x transport helo [uh1 5 lives] 2 x lotatc 1 x Combined arms
  3. Clarification Post Reservation 3.August - KH66 and D2M are banned due to them not being used or beeing able to be used on available platforms. Disclaimer was added to the first post. 4.August - Added clarification about quota per sign up per role and proceedings in case slots become free due to withdraw. 7.August - Added R77 to restricted weapons list since it hasn't been in service within 1989. 8.August - Clarrified that the amount of roles equals the available airframes. So single life, no respawn, repair required except bugged plane. 13. August - first wave of assignments done, second phase of sign ups for left over slots ends on 19th of August. After that slots will be assigned on a first come first served basis. - Planning discord with dedicated rooms for NATO and PACT: https://discord.gg/7zxayGG 14. August - Objectives and Unit/stores availabilities added to NATO and PACT channels on planning discord. 28. August - last allocation wave done, rest of slots are first come first served. 9. September - fixed NATO availability, announced shift of event to 15th september final time 1730z, briefing 1700z.
  4. Wings 0,45% edition Okay, the event has been rescheduled to the 15th of September, 1730z and is going to run for 3 hours. Please be there 1700z for patching everything together. Planning discord with dedicated rooms for NATO and PACT: https://discord.gg/7zxayGG This event will be run according to the following ruleset, purpose of this scenario is to have an wargame including as many aspects of air combat represented in DCS working together in a planned fashion to achieve a Mission success. Scenario: This scenario assumes a non nuclear Cold war gone hot in the last minute scenario in 1989. The force compositions are oriented towards 0,45% of airforces and airdefences and 0,3% of ground forces which would have probably participated in a european conflict zone in that scenario. Since we dont have a european theater, the event will be held at the next best replacement, which is the caucasus map. There is no historical background to this geographically, the frontline will be assumed to be todays russian border since its terrain wise the most sensible frontline. Glorious video by War Aesthetics capturing the vibe. TL;DR The rules are mainly here to have a fallback to decide stuff and make it clear up front how things are going to be handeld, so we can minimize stress, frustration and all that stuff during the event or during planning phase. In case anything is unclear let me know and I will post a list of clarifications in chronological order in post #2. Don't be intimidated by the rules, they are really just here to maximise smootheness, a normal sign up will do and you have until the 8st of September 2018 to really fully read them. [And even in case you don't, you mostly will have some small disadvantages in comparison to the people who did and might be subject to penalties during the event due to violations.] Assets and Objectives =========================================================================================== - Each faction will get briefed a set of objectives to defend and to attack, this doesn't mean all objectives will be engaged by the enemy nor the enemy necessarily knows of all objectives. The to be defended objectives just are a reference to what units in the gameworld are actually considered by the scenario as an asset relevant for scoring. - All airbases are considered Targets and doing damage to them will be reflected in scoring. Damaged areas of the runway will be considered closed and a repair time will be decided upon by the game master. Meanwhile undamaged areas may still be used for operations. The minimum length of undamaged runway to be considered operationally usable is 1000m. - Each faction will get assigned a complement of stores, Aircraft and ground assets which they can distribute over Airports, in the case of munitions and airframes, and the map in the case of defence assets. The latter will be achieved via a mechanism detailed in the corresponding section of this ruleset. If one side does not chose to take advantage of this the Gamemaster will place these assets. - Each side will get 2 FARPs which can be used as makeshift roadbase and or for helo ops warehouses, if desired. Command structure =========================================================================================== - Each side is expected to run at least one organisational meeting where representatives from each Squadron are sent. During this meeting a side commander needs to be elected, also a second in command should be assigned for redundancy reasons. - The role of the Side commander is primarily to interface with the Gamemaster for communicating unit placements and channel, if possible, questions considering the execution and rules of the wargame. Also in case discussing factions cant reach consensus over unit placement, stores and airframe placement, task timings and other strategic concerns, he may make the final choice. This is an combined arms focussed wargame, someone has to call the shots to stop the "too many cooks" problem from ruining things TM. Any tactical concerns of how a flight achieves a task is down to the flight lead. If a faction feels this rule is too intruisive a 2/3s majority is required to abolish this rule. - In case a faction chooses to operate without a designated commander, the Game master will only take mission changes from a assigned mediator. Recon System and mission setup =========================================================================================== - This event will attempt a reasonable Intel, static assets are known per default [satellites TM], static sam sites, as in SAM sites which aren't designed to be moving with troops, will be revealed 24 hours before the event, including only site position, not singular unit placement. Mobile units will only have an Area of operations marked on the Intel map each side will get. photographs of unit compositions may be handed out at the start of the mission or not, depends on weather and feel of the Gamemaster mostly. :D - The Factions will get reasonable weather forecasts with reasonable inaccuracies in the days before the event. - Airframe and Stores assignments to bases need to be made via a List to the gamemaster. - defence asset placement will be done via copy pasting groups from faction prepared missions into the final mission which will run on the server. Each group will need to have one unarmed unit on a reference point on the Map so I can easily place it via copy paste. absolute placing accuracy is limited so keep that in mind. Each Side is limited to a Maximum of 10 groups. - The Mission state will be frozen 48 hours before the event. =========================================================================================== Sign ups The sign ups will be open until 12.August 2018 during this time Squadrons, lonewolf groups and lonewolfs can sign up for given slots. Lonewolf groups have to be declared in their signup by each of the connected lonewolfs. Squadrons and lonewolf groups will be treated equally, singleton lonewolfs are the last in the waiting list for a slot. Since role slot availability is fairly limited the slots will be assigned based on dice roll. To maximise chance of participation, signups for multiple roles across both factions are allowed. A maximum of 1 sign up per role per faction may be issued, with a maximum of 4 players per role. Squadrons or groups who sign up for a single role type will be given priority over mixed sign ups. The dice roll deciding over slot allocation will happen first for homogenous groups of each type, then for groups of 3 homogenous, then for groups of 2 homogenous, then for groups of no homogenous roles and then for lonewolfs. Group sign ups of size 2 or larger will be considered homogenous in case they only contain a single role type. In case all slots of role A are already taken and a hetrogenous signup group is choosen by dice roll and includes a slot of role A, the chosen signup is eligible for a slot of each role, except role A. In the case that after the first round of slot allocations there is still other role slots available, the remaining slots will be first made available to signups which didn't get a slot as part of a group due to already fully populated role slots. Sign ups are to be made via role type, not aircraft type. Once a role type has been allocated to your Squadron/group, you may select one of the AC available for that role for your side. You communicate that to your side commander or mediator and it will be "hard coded" into the mission via his hand in. So technically the last time to change your mind is before the last hand in your sides commander/mediator will make before the lockdown 48 hours before the event. The role of SAM and artillery commander will be done via combined arms, GCI and airboss duty will be done via LotATC. In case a slot becomes free due to withdraw of allocated participants, the slots will be made available to the waiting list first in the same manner as the initial allocations and only after that they may be allocated to people outside the sign ups. =========================================================================================== Sign up examples: #1 homogenous vs hetrogenous sign ups: $random squad 1 f15 1 f18 1 av8b 1 a10c $awesome squad 4 M2000c $random squad will be considered before lonewolfs, but only after homogenous sign ups like $awesome squad have been part of the dice roll for the given slot. #2 multiple sign ups: $smart squadron 1. 4 [high end fighter, blue] 2. 4 [mid tier fighter, red] 3. 4 [strike, red] 4. 4 [cas, blue] 5. 2 mig21bis [low end fighter, red] $smart squadron will be included in dice rolls for high tier fighter, mid tier fighter, strike and CAS and low end fighter in the order of listing. =========================================================================================== Each slot is a single airframe, except for transport helos. So if you get shot down you can not respawn, if you land with a damaged plane you have to repair. If a plane is bugged a time penalty will replace the repair option. Available roles for sign up : NATO 4 x high end fighter [f15c or F14, just in case] 10 x mid tier fighter [M2Kc or f/a-18c] 4 x low end fighter [f5E] 4 x CAS [A10C or AV8B] 2 x SEAD simulator [sU25T] 2 x transport helo [uh1 5 lives] total: 26 AC slots PACT 4 x high end fighter [Flanker family] 8 x mid tier fighter [Mig29, M2Kc] [Plox consider flying mig29] 4 x low end fighter [Mig21 or AJS37] 8 x CAS/SEAD/strike [AJS37 or SU25T] 2 x Transport helo [MI8 5 lives] Total: 26 AC slots [The AJS37 will get different amount of stores a2a and a2g stores depending on in which role it gets selected.] Both Sides: 1 SAM/Artilery coordinator [Combinde arms] 3 GCI/AWACS/Airboss whatever you like [LotATC] Weapon restrictions: 1989 in other words(including weapons/pylons that were never used on available platforms but are implemented as such) No BLU108 [CBU97 CBU105] No Wind Corrected Munitions Dispenser [CBU103 CBU105] No AIM120 [if we only had the A] No AIM9x [just in case] No AIM7p [just in case] No R77 No JDAMs No Vikhrs [9k121] No AGM65 H, K, J No D2M No RN24 No RN28 No RBS15 No BK90 No RB75B No Kh66 The R27E series will be available in very limited numbers [15% of total R27 inventory] The blue side will get a single [!] litening TGP. Technically the litening 2 didnt enter service but since LGBs were used very extensively in desert storm I want to at least emulate the aspect of LGB usage and limited lazing capacity. In case I forgot something which wasnt in service by 1989 or something in the list was in service with the respective platforms in 1989 feel free to approach me. =========================================================================================== Just stability things: It is my plan to run a similar load mission to the final variant on the 25th of August 2018 to prevent the mission breaking on us on event day. I invite all the sign ups to participate to ensure smooth event execution. S!
  5. I got mine this week. The Buttons have a very nice haptic and audible feedback of the button action, the backlight is very good imho. During the day it increases contrast at night it makes the stuff easily readable. The box is also very rigid. Overall I couldnt really be happier with it. The price is imho very fair, given what other products cost and at that point arent even replikas like this. f18 UFC would be instabuy ! :)
  6. Harddeck, because A7s try to hide from AWG9 in ground clutter only in real life training scenarios tm.
  7. These posts show as deleted in the closed thread. I read them and know at least one of them was purely constructive. And I dont see them merged in this thread either.
  8. Okay first, there were constructive discussion items in the old thread, theese were just deleted, not merged into this one. Imho bad move. My main gripe with DCS MP that things are implemented in a blocking way since single threaded for the main simulation and graphics. Someone DC's crashes, server loads something, everyone has some seconds of blocking state. I think if this blocking nature could be parallized, i know its hard tm, much would be won already I think. Second main gripe, naval combat. Having serious fleet on fleet action in DCS MP causes very large instability due to the amount of actions happening in tightspace. I mean look at a Kirov class cruiser and kutznezow battling an US battlegroup and server performance will take a huge hit and there has been very high chance of straight away crashing soon thereafter in the past. That would be my 2 main requests.
  9. This is a general complaint about the situation that in 2018 we have a single threaded game engine that requires graphics capability to run a server. Business Intelligence delivered right to your doorstep.
  10. Master Mode selector to NAV is a requirement iirc.
  11. =RvE=MicroVAX Evil red GCI
  12. Glorious ! Already tried it, Viggen will now rightfully dethrone f15 and su27 as top of the line fighters. :D
  13. I already said this in regards to the INS update and I will reiterate it here. As someone who really is more into the scientific/engineering backgrounds then the flying part I am really happy to see this being done.
  14. =RvE=MicroVAX The Swedish hypersonic double Dorito [AJS37]
  15. Would be prime time to fix this, there is an a2a event 14th july. I am not sure why its broken but I would hope its fixable until then.
  16. Thanks for the intense fights, we really got a bit lucky I think. :)
  17. Yeah because the 154b was never bought or adopted by anyone so far.
  18. well switch off the taxi light sounds like a hotfix to me lel.
  19. I second this feature request whole heartedly ! I already wanted to post that for a long time, happy someone else did ! :)
  20. Same issue here running main game view at 3440x1440p
  21. Browser literally suggested the 2 old RB74 seeker related threads i created in may and june 2017. I am kinda i dunno confused this still isnt fixed since release. So the RB74 seeker is rear aspect only _as long as its on the rail_, also its flight performance is that of a aim9p, it should be an aim9l basically which now even is in game. This massively reduces a2a performance since you cant lead headon shots and for headon shots at all you got to guess an intercept vector to get the target into the missiles FOV in the future, because off the rail the seeker is all aspect. I hope we can get a fix for this rather sooner then later. :)
  22. Multiplayer performance and netcode, datacartridge support on the hornet, Missile guidance logic, fragmentation damage both a2a and a2g.
  23. Great communication on your part Deltaalphalima1 ! Looking forward to getting axis slew on the warthog throttle ! :)
  24. I agree that there should be a statistically reasonable amount of female voiceovers. I agree that something like pilot model would be nice, again statistically reasonable to reflect rl composition. For starting youtube videos, would ofc be more inclusive to start it with something explicitly gender inclusive, but tbh I did go and ask my youtube statistics its literally listing 100% male viewership over 15k views or so. I know there are the every now and then 1-2% female viewers turning up in the statistics on some videos. So yeah. Its an idealistic and better decision to be inclusive. But I wouldnt mind it to much as the 1% minority if someone fails to be explicitly inclusive. I share the annoyance towards the reactions of some wannabe hotshot pilots though. :D
  25. RvE MicroVAX Krippz Dackster Snowman Yorz Covernow Jman Tito Vertitech In terms of aircraft whatever gets the job done Discord: QQtHwAU
×
×
  • Create New...