CrashO

Noticed it too. Figured it was the laser. However. For some reason though, it seems the inverse from the laser. If I center the camera, Spot is in the middle. If I slew the camera left, spot moves right.. if I slew the camera right, spot moves left.

I see a lot of lag in other server too. But blueflag usually tops it. Like this, a few hours ago here on BF (with a buddy, on a decent connection).

Turn on autopilot. Then try using your trim left/right and look at the selector

You know a life is lost as soon as you takeoff, and returned only on landing right? So disconnecting does nothing to save it. What does happen a lot on BF, is the game crashes when you die. Not with all people, but a lot of my friends have this problem, and I have had it to for some weeks (problems stopped a month ago for unknown reason). You get hit by a missile, and before seeing the actual "boom", your screen freezes up and the game just crashes.

For simpleradio, the buttons in the Mirage don't have to be bound.. if you do, all it'l do is open up the radio menu (same as \ key) everytime you want to talk on SRS.

You have SU-33's with ET and ER missiles (while blue is stuck with aim-7), and unlimited lives, spawning from Carriers that respawn every 3 hours, even if we destroy them. Making it impossible for blue to get north of Sochi. And you have had a 4:1 radio for the first half of everyday (when blue is either at work or sleeping), for the last 2 weeks. (leading to capturing stuff in the morning and blue capturing back in the evening. And still your playing the "its so unfaaaair" card. poor poor reds. :doh:

One minor difference here. If I have a A-10C mission all build up and worked out. And someone who doesn't own (or want to fly) the A-10C wants to join in. I can just add a Huey for search-and-recovery and he can play (and add an extra element to the mission). The helicopter fanatic does not have to buy the A-10C he does not (want to) fly in order to play along. With the assets, using a single asset, forces all of the "would be" players on the server, to purchase it. Leading to everyone needing to buy everything if they want to be able to move around a lot of the servers. Again, I am not opposed to buying assets, but feel they should work in similar fashion to the current aircraft DLC. And not block people from joining a mission that has a asset element in use. I can play on OpenConflict when I just own a F-15C, and use just that module, without having to buy 12 different modules to join first.

It is isn't. You are still assuming everyone would buy it because they want to have some ww2 roleplay. There is a lot of stuff in that pack, that can be used in a bunch of not strictly ww2 situations. And mission designers (particularly on the other 2 theaters) can't use those without have all of their players get the pack. But since we are in a general asset topic. I will use the "advanced" carriers that are under development (and whom I am guessing will be some sort of DLC asset pack in the future). If you take a busy multirole server like BlueFlag, that sees alot of different players visiting, is already has carriers with SU-33's. Once the F-14 hits (and future carrier assets), it'l make perfect sense to stick one of those in there 200nm from the coast, for people wanting to be Maverick. And most F-14 pilots wanting to use those will buy them for sure, so will Harrier pilots. But.. having one of those puppy's in there, will mean the people who now only fly troop transports in their huey, of roam around in their A-10's. will have to buy the carrier asset, in order to continue playing their CAS or transport roles in the server. It's totally different from the way DCS World worked up until now. (buy what you want to use). How doesn't this fragment things?

All there is to it. :)

There isn't a (default) keybind. Is is on the hotas of the Mirage, you are supposed to bind it to something.

I think you are missing the point most people have. It's not the price. I'll gladly fork out $60 for the map+assets. Same as I have done with all other modules up till now (even though I haven't gotten more then 2 hours flight on any of the ww2 stuff). Just to support this niche sim so I can have fun in the jets. The point most people have regarding the assets, is that using the assets in the other maps, stops people from joining the server. The beauty of DCS world is/was that the threshold to join is low. If I want to fly a mission in the mountains of Georgia with a Huey + A-10. I can do that. I have to buy the A-10, buddy buys the Huey, because he never flies fixed wing. After playing the mission a few times, another buddy comes around who only owns the F-15. So I stick a f-15 in there and that buddy is circling around in CAP now. Everyone happy. Now I decide to stick a flack canon in there I gotten with my mappack. Buddies can't join the server anymore because of 1 canon in the map. Sure, as the mission designer I can remove it, but it'l mean checking every single time with all of my buddies, who has what asset pack, what assets pack are the same so we can use, what not. etc. etc. Is going to become a big pain very fast. Instead of just "What are we flying tonight lads? Caucasus!, aight" I get why ED needs a return on investment, and support it. But.. loosing the flexibility DCS world has gotten his name for (anyone can fly any of the modules in one massive shared world) shouldn't be lost because of it. In my opinion, the way to go would be something similar to how plane DLC works in the game.. Free: Have the assets sitting in a server as a client (not hoster) without having any influence on them Paid: -Controlling the assets (with or without CA) -Use them in the mission editor -Host missions with them The 90% of people who never play online, will still have to buy it. So do mission designers and hosters. What is left is some small percentage, many of whom wouldn't buy WW2 assets in the first place, while still trowing the "online community" a bone in letting them fly together.

Why? The multiplayer part of DCS is (still) small compared to the offline userbase. Offline players still need to buy it. So do mission designers and hosters. And people who want to control the units. And people who like to support ED. What is left is a percentages of players pretty small, a lot of whom probably wouldn't buy it anyway because they don't focus on WW2 or for different reasons. What you get back in return is the same as is currently going on with all the others modules. Loads of people buying and using different planes in 1 big shared environment with large flexibly about what they spend there money on, yet still offering the ability to fly together.

Sort of the same way Plane DLC is handled at the moment. If I join a server and someone is flying a plane I haven't bought, I can still watch him fly it (and join the server). I just cant fly it myself. Imo, thats how it is supposed to be. Now, ofcourse with AI "assets" it is slightly different. I can see how map DLC is mandatory, but the units shouldn't prevent people from joining in. What would be fair (in my opinion, but obviously, I don't know if the DCS engine has the technical ability to implement it this way) is: Assets need to be purchased in order to: Add them to missions Edit them in missions Host missions with them "control" them in missions (with or without CA) should be "free" for: watching them fly around in missions you are not hosting yourself This way it doesn't fragment things, but to make actual use of them you will still have to buy them.

How would that work? They are both used on two different helicopters. The version that fires HOT missiles is the SA-342M The one that fires Mistrals is a subversion of the SA-342L wich itself is a militarized version of the civilian SA-342J. Different engines, different camera systems, different airframes, different controls panels.

Might be a stupid question, but are you editing the correct version? (this path is the stable branch and you are not launching the beta or anything? ). The file looks normal to me. (although I haven't checked every dot, but in general it looks right).

Server just died 2 times in a row again (within 15 minutes from start). Coincidentally, a lot of people where using Viggens... *edit* and a third time, thats one way to lose 3 lives in an hour.. Mass disconnect this time. From 40+ people to 5. Pretty much everyone except the observers got connectionloss.

How I (and most others at blue) generally use it, is SR for OPS and the buddyspike TS for general banter. So usually i'm connected to both. When I am generally coordinating stuff with the squad (what are we hitting, when are we hitting, who's flying what? I use TS3. And for general banter. And on SR (264) we just do BRA callouts and strategic stuff. (asking new pilots intensions, rayguns, setting up squads (and once thats done, have that squad switch over to a private SR freq for chat about that specific flight) The GCI freq (264,- for blue) is usually just business. Although the brevity is quite informal, being a lot of the guys don't know the strict and correct way to make call-outs. The only thing that bugs me is the people doing radio checks on 264 instead of 251. I hate being in a fight and having someone with his mic boost set to over 9000 doing a radiocheck every 10 seconds on the GCI freq. So as a practical example (for people who never used SR). When I am flying a (blue) Huey with troops, with the intention of a base capture. I am tuned in to 3 frequencies (at the same time) on SR. 264,000AM for GCI 1xx,000AM for comms with my squad and/or cap 30,000FM for comms with other helicopters and A-10 doing the striking. While also being on TS3 for cracking jokes and bitching about RED spawning in their SU33's again :D

DCS-SimpleRadio Standalone

You should advertise SR day in Russian. Seeing blue doesn't need a special day but just has simple radio day, every day. :D

It was a pretty nice furball against those overpowered ET launchers with the flightmodel of a skateboard. Raptor had it on video. :thumbup:

какой причина говорить по-русски на английском форуме. Razbam не владеющих русским языком, razbam испанский и английский

Check if the fuel cutoff switch is down. The default state of it changed a few months ago. So old tutorials don't teach it, and it might have worked a while longer on 2.0 because a lack of updates there. k6EWUselqjg *edit* Second thing to check, confirm your throttle is all the way down before starting. If not, press engine shutdown to reset it (small red button on the right side of your throttle).

Still think your doing something wrong while saving. Might be the editor, might be something your doing. No way to tell for me. Try this (JSGME ready) one out of the box and let me know how that works :)

Entire "procedure"... If it destroys your bindings you must be running some other stuff that interferes. One thing that might cause issues is if you have binded the (old) nightvision to another key. And now that device no longer excists. Try resetting the lines back how they where, start game. Set the binding for the Goggles back to "default" and then make the change to the code. If you messed up the syntax in the lua file however, DCS might decide to ignore it during parsing, causing all the bindings in it not to load. That might be what happened to you. Check if you did it like the GIF

Affirm, passes the IC.