Azraeil

Ironic.

Ok cool. Seems like we are on the same page. The reason there is no 'signal' (gauge boson) is because the information exchange occurred before the particles separated spatially. Until their wavefunction is collapsed (by interaction or 'measurement') they evolve as ONE system. As you say there is no information exchange so no causal violations. I think where people get confused is equating wavefunction collapse to information exchange, one can occur instantaneously whereas the other cannot.

Probably a language barrier thing here, but could you explain your meaning of 'physical signal observed' and how that relates to the preserving the laws of physics in this context? I don't quite follow.

You aren't conceptualizing the experiment correctly. Rather than considering the particles as separate entities you need to consider both particles as part of one inseparable quantum system (hence the term entangled state). When you measure the spin of one particle you're actually measuring the state of the entire quantum system, which just so happens to be spread over a large area of space. At no point in time can you force a specific outcome without wavefunction collapse, and thus results you will measure are completely random and whilst in perfect agreement with an observer on the other side of the wavefunction, can not be used to communicate with said observer.

We cover these concepts in undergraduate, however it has been a while lol that I have specifically dealt with this issue! One thing I might add that I have learned is that it is not trivial to conceptualize mathematical/physical theroem, hence why we have various interpretations of quantum mechanics (Copenhagen interpretation being the current frontrunner).

One way I like to conceptualize the positron-electron quantum state is as a single wavefunction which happens to occupy a large volume of space. Before you propogated this wavefunction you would need to have life hax in order to know the result and thus use it as a meaningful communication mechanism and I am pretty sure life hax don't exist yet.

As a PhD student in astronomy this entire thread amused me highly. fyi - old problem http://en.wikipedia.org/wiki/EPR_paradox

Dat ambiguity...

http://www.simhq.com/_air15/air_540a.html Some new screenies and a discussion of features we knew about already.

Woah missed a whole page of posts there. Yeh, I knew you would bring up SADL stuff and I must admit, having flown the F15 in fc2 for the first time I really did miss the TAD. And yes, I actually agree with you.

I didn't want to be quite as forward as that. Maybe the testers know something we don't ;)

Evidence?

I can see how one would draw a logical conclusion that 1.2.2 and FC3 may be related in feature set and thus share a similar release date (although this is pure speculation). To say however that it just IS coming out this month is beyond speculation and just saying things for the sake of saying them. Unless you know something I don't?

Haha nice one guys. Seems like the general consensus after a bit of reading is that 1.2.2 is the priority and rounding out features such as the resource manager etc etc.... I doubt we will get any further specifics from Wags though so I suppose it's back to (in)patient waiting.

Many many fails. Probably most epic was the time I was coming in formation landing as lead. I forgot to put my gears down and landed on my belly. My wingman at the time (Redfish) was laughing so hard that he also forgot to put his gears downs. We both landed in perfect form on the runway aside from any lackthereof gears.

Seeing a frame-rate improvement in the instant action with the latest build :) Bring on FC3 and take my dang money!

One core does most of the work with sound offloaded to the second core AFAIK. I expect that as DCS becomes inherently multithreaded we will see significant fps boosts around airdromes and the like. I think that's what EDGE/nevada seeks to do but don't quote me on that.

Now there's an idea for a persistent/dynamic campaign. Imagine if you regularly exceeded safe operating parameters causing structural wear which required your aircraft be grounded for a few days during the campaign!?

Anyone experiencing frame rate issues with the P51 guns with the latest build? Just hosted a dogfight server and had some frame-rate drops whenever they were firing. Or has this always been a problem?

Its funny I was in that server the other day when you were on the opposing team. The only confusing thing about that mission is that battle lines were reversed. I.e. blue ground vehicles were closer to the red home plate and vice versa. The mission was basically a race to see which side could finish its objectives first. The TOR's you were referring to were a bunch hiding just outside your homeplate as an anti base rape measure. I must say these have worked quite effectively in the past (I saw an SU25 get shot trying to be sneaky). As you where on the blue team, your objectives were composed of Russian vehicles and hence each armour group may have had a TOR defending it, these are well away from the anti base rape sams. Rather than just saying this 'mission makes no sense' try reading the briefing or jumping into the 104th's ts to ask some questions as I did, they were all very helpful btw. Actually I think op moonshine is a fantastic template for red vs blue scenario's when fc3 comes out.

To avoid igla just do a barrel roll like so. ;)

Ditto. I have connected a dozen or so times over the last 5 hours and have not crashed yet. I hope this issue can be resolved for other players as it was encouraging to see as many servers up as there were.

Just had a fly today with build 6120. Excellent stability (relative to what we have had in the past ;)) in the server with upwards of 10 people, frame rate improvements (for some not all), plenty of servers on the server list and have yet to crash at the master server list.

To be fair, this problem has existed since the standalone. I have mentioned this before, but certain areas seems to hardcap the framerate and no amount of gpu power or visual setting tweaking will budge the framerate. This problem is most common around airdromes, especially those with the fortified hangars. It would be really nice if we could get an explanation of the cause to this from the devs, but I have read from ed testers on this forum that this is likely due to the processor capping out and not being able to instruct the gpu fast enough. As far as I can tell only one core is doing the brunt of the work (maybe sound on the second core?). EDIT: Just checked the server list and didn't crash out, and there are servers up everywhere :D, to bad I am from AU and have bad interwebs and 300+ ping.