yallu

Greetings, looking for some advice, I have i7-4790K not OC'd. Would any of these cards work decently (keep 45 FPS) with the Rift: Vega 56, Vega 64 (nitro+) or RTX 2070? With high settings (but not very high or ultra), low shadows and reduced trees. I'm looking for guestimates or if you happen to have the same combo...

Just a little bit south and east and the original map would be perfect. Then it would include from Russian side bases such as: * Alakurtti (mot inf brigade) * Montsegorsk (air base) * Severomorsk (northern fleet) * Olenja Guba (missile brigade) * Petsamo (mot inf brigade, marine inf brigade)

var userProfiles = db.getUserProfiles(); for (var i = 0; i < userProfiles.length; i++) { var orders = userProfiles[i].getOrders(); var ord1 = orders.getOrdersByName(["dcs_black_shark_english", "dcs_black_shark_<l18n>"]); var ord2 = orders.getOrdersByName(["dcs_black_shark_2_upgrade"]); if (ord1.length > 0 && ord2.length > 0) { userProfiles[i].addNewOrder("dcs_black_shark_2_full") } } Thank you. :huh::music_whistling::P

4 x Fw 190-D9 4 x Bf 109-K4 Suitable for squadron night. Designed for team flying, not really suitable for free/solo flying. You will get your orders, takeoff together, fly together and then land together. After which you regroup, refuel and rearm - and finally request new task from radio (radio items are added to coalition level so you might want to coordinate who handles radio). Mission consists of variety of tasks that should keep your team occupied for 2-4 hours. Contains some random elements. Tasks may be harder when more players spawned. Start the mission via radio once everyone have spawned in. Task: You are assigned to 5./JG 301 II. Gruppe under Gruppenkommandeure Hauptman Herbert Nölter. Follow orders as you receive them... WW2 1944-08-R.miz

Looks like 1.2.8 broke this, same for anyone else or is it just me?

I'd like to see METARs used in all weather creation. You could use real world METARs or specify your own. An algorithm would render the same METAR exactly same way in all clients. I'd implement support for METARs in phases: Phase 1: - One static METAR for the whole theater - to get started. Phase 2: - Static METARs for all airfields that have them publicly accessible in the internet. - Transition from one METAR to another (from airfield to another). Again, same algorithm, same result in all clients. Phase 3: - 60/30 min (?) changing METARs for all airfields. You could give like N METARs for each airfield as snapshots of progressing time (60/30 min intervals). - Local transition from one METAR to another. - You could use internet METAR history databases to replicate historical weather data (like the five day war, data is still available) - or create your own weather progress. Phase 4: - Optional real time weather from the internet. - Sync'ed download to all clients. - Smooth transition to latest real time weather. Any METAR based weather progress could also be started from random METAR with some intelligence in randomizing the next METAR snapshot. For example, right now Sochi Adler METAR is: URSS 250830Z 00000MPS 9999 FEW030 BKN300 09/03 Q1018 NOSIG RMK R06/00000MPS MT OBSC QFE762 02000070 06000070 Which means: Location: URSS Day of month: 25 Time: 08:30 UTC Wind: True direction = 000 degrees, Speed: 0 m/s Visibility: 10 km or more Clouds: A few , at 3000 feet above aerodrome level Clouds: Broken sky , at 30000 feet above aerodrome level Temperature: 09 degrees Celsius Dewpoint: 03 degrees Celsius QNH (Sea-level pressure): 1018 hPa No significant changes expected in the near future Runway state: Runway 02 (or 02 Left): clear and dry, deposit less than 1 mm deep, friction coefficient 0.70 Runway state: Runway 06 (or 06 Left): clear and dry, deposit less than 1 mm deep, friction coefficient 0.70

Has ED made any promises/estimates/guesstimates if the new GE will in average actually increase FPS, keep them about the same or decrease somewhat (for the new eye candy)? New sim engines tend to increase eye candy but usually have zero or negative effect on FPS...

I'm just starting with Mist so I most likely got something wrong (I'm also new to Lua)... But just in case, is there a bug in mist.groupToRandomZone? function groupIsDead(groupName) local groupLife = 0; local i = 1; local group = Group.getByName(groupName); while group:getUnit(i) do groupLife = groupLife + group:getUnit(i):getLife(); i = i + 1; end; return (groupLife == 0); end; function init() mist.groupToRandomZone("MyGroup", {"TargetArea"}, AI.Task.VehicleFormation.LINE_ABREAST, 045, 80); end; DeathHandler = {} function DeathHandler:onEvent(event) if event.id == world.event.S_EVENT_DEAD then local unit = event.initiator; local groupName = unit:getGroup():getName(); if groupIsDead(groupName) then trigger.action.outText("Group " .. groupName .. " is dead. Respawning...", 10); mist.respawnGroup(groupName, 10); mist.groupToRandomZone(groupName, {"TargetArea"}, AI.Task.VehicleFormation.LINE_ABREAST, 045, 80); end end end world.addEventHandler(DeathHandler); init(); This code works the first time (so init(); works). But after group's death, it will respawn, starts moving and then crashes. It's not instant crash on respawn but takes a couple of seconds. Anything obvious wrong?

What's wrong with doing the light version first and selling it as FC addon, then starting from that, branching to full high fidelity DCS addon and selling that as well (with a little discount for those already having the light version)?

You have to fly this aircraft like having an uncooked well oiled egg stuck in your ass. Squeeze too much and your having an internal omelette, squeeze too little and somebody's gotta clean the floor - and the knickers... That's what I've learnt so far...

Hmm... Good to know. My MS Security Essentials didn't complain...

Not sure if this has been here already, but if not, found this: http://freechecklists.net/Resources/Bell/UH-1H/

-10+11

Out of curiosity and slightly on topic... Is there a way to get the current MGRS grid with a script as well? Getting LL is great for purposes requiring precision but often rough location would be enough. Something like the 9-grid system (or whatever that is called in english). For example, take grid location GG39. City of Hamiskuri would be in location GG394. You take the grid and then imagine your numpad keyboard over the grid and therefore split it into 9 smaller grids. Number 4 on numpad therefore is the left center of the GG39 grid. Very intuitive and fast way to get rough locations without typing lots of numbers into flight computers. If you need to, you may futher revise, for example, GG3949 meaning left center of GG39, top right of that left center part. That is relatively accurate already. So the question really is, can you dig up the MGRS grid and does it have enough LL information (top-left, right-bottom etc.) to allow splitting it into 9 subgrids and perhaps those 9 subgrids to further 9 subgrids each? To get the outcome: "I'm on grid GG394" or "I'm on grid GG3949"... Just an idea...

With 1.2.0, do you still have to own a payware module to be able to do multiplayer?