PitbullVicious

Do we know if the Magic 2 is boost-sustain or boost-glide?

Maybe you're both right :P Maybe I'm starting to imagine things (it's quite late here already), but looking at graphs from different missiles on TacView it looks like the R550 is "time compressed". Well, it is difficult to say anything conclusive at this point, and I think I need some sleep. Maybe I'll see things in different perspective tomorrow.

But that was the point of my question :) I'm just curious to know. I just succeeded to get a kill from about 9km. Mind you, from a very artificially advantageous point (high above in a dive). Wouldn't considerably larger cross section affect the energy loss? AoA during flight? Even if we otherwise consider the missiles to be similar in terms of aerodynamics?

What in general (if there is any standard to begin with) does maximum range in mean in terms of IR seeking missiles? The maximum range for the missile to fly straight, or the maximum lock range for the sensor? To me that translation reads like more of the latter.

Umm.. I'm a bit confused on what strong conclusions can you draw from the curves. I don't know how reliable Wikipedia's stats are, but according to them the R550 MII is over two times heavier, has 1.7 times the cross sectional area compared to the R60. It's about the same weight as the Aim-9m, and has about 1.5 times the cross section area. At least to me, supersonic drag is not a trivial thing, so could you elaborate on these conclusions a bit? Also, to me it seems that the graph only shows true airspeed and time. Doesn't the effective range depend also highly on the trajectory (which in turn depends for example the lift of the missile)? I'm not saying if the R550 is performing correctly. To be honest, I have no idea. I'm just wondering what kind of things can you read from those curves that imply that something in the physics modelling is wrong?

For what it's worth (maybe around 3 of your now obsolete francs :) ), I tested the 530 against a hot Tu-22M3 @ 40,000ft and managed to get a kill from around 25.8nm with the Tu-22M3 pumping chaffs and evading.

I'm using Japanese in my signature and it seems to cut off in middle of the sentence. I've tried to rewrite it and copy and paste it in the "Edit Signatures" with no luck. It shows up correctly in the edit field, but the preview is corrupted with some chars showing as question marks inside black squares. In the posts itself the sentence cuts before those corrupted chars. I tried to change the font, but that didn't seem to help. Here's the Japanese sentence: 善く戦う者は先ずかつべからざるを成して、もって敵の勝つべきを待つ。

I guessed you'd go for an average of 5ft, so I intentionally went for 4 of course ;) Thanks!

One... foot... I guess I had beginner's luck on my side. Really could've gone either way. Thanks to Bunyap for organizing and everybody participating. It was good fun and I learned a lot. - PitbullVicious

I had a little mishap (that's my story and I'm sticking to it) and had to bail out over the oval race track. I was surprised to see that the parachute was shown in 3rd person and there seems to have been quite significant improvements to the pilot model (or my memory is failing me).

Wehey! Should be ready then about the time I get home from work and get ready to have my evening flight ;) And as it happens I just finished downloading 2.0 last night.

This looks like a related bug: http://forums.eagle.ru/showthread.php?t=150299 So it seems that it is not Huey exclusive bug. A-10C didn't have that problem in 1.5.x, but I haven't tested it with other planes. Thanks! I haven't tested the A-10C in 2.0 yet, as I finally finished downloading only last night.

Here's also my submission (submitted to Bunyap earlier via email), in case anyone's interested or has comments. Both .acmi and .trk files included. And indeed, thanks to Bunyap for organizing this. - PitbullVicious Bunyap_competition_submission.zip

SiThSpAwN, A quick check in a quick mission seems to suggest that this has indeed been fixed. I saw some very minor flickering at the base of a bridge, but that might be a separate issue. I'll verify more thoroughly when I have time (although most likely someone else will do that before long). All in all, looking good, looking good :) Thanks!

Thanks. It seems that I better learn to read before trying to write to forums or indeed play computer games... :cry: Edit: Purchased BTW.. I guess I'll learn to read while using it... - PitbullVicious

SiThSpAwN, I think this might be the same problem as this: http://forums.eagle.ru/showthread.php?t=148420 On the 6th post of that thread there's a link to a video demonstrating this problem. -PitbullVicious

Hi Vyrtuoz, I'm seriously considering of buying the Pro Licence, but I'd like to verify one thing (didn't find an answer to this question here or in the FAQ): To what extend does the licence include updates? Do you have a roadmap for the version updates? I'd imagine that any updates before 2.0 are included with the licence, but how about 2.0 (which I understand you are currently working on)? Do you consider for example giving a discount to the licence owners for v2.0 when it comes out and when is it due to be released? Thanks! -PitbullVicious

OnlyforDCS, That worked indeed. Thank you!

I could also verify this: "Weirdly enough, using external views, I can confirm the elevator trim tab moving in the correct direction as it should. In cockpit the trim wheel also moves like it should in the proper direction." I.e. the plane 3D model seems to act according to the trim binds, but the FM actually acts as if pitch and roll trim have been exchanged. I'm also using a MS SWII FFB joystick (with the Warthog throttle), so maybe that is the root of the problem. I'll try with another stick. I think in at least MiG-15bis the trim works correctly with the FFB joystick. - PitbullVicious

This seems to be an old post, but I'm having similar issues with my MS SWII FFB stick in Open Beta 1.5 (these problems MIGHT have existed in earlier version also. I haven't flown the P-51D much until recently). I'm using the MS SW II joystick hat for aileron and elevator trim. However, setting the nose up and down trims in the setting to hat switch backward and forward respectively seems to affect the aileron trim (plane banking to right or left with the joystick offsetting from the centre in logical manner in respect to the aileron trim). Binding the hat left and right to hat switch left and right seems in turn affect the pitch trim. I have no recollection if the trims in the cockpit model move correctly or not, nor have I checked how the tabs actually move in the aeroplane model. I will verify these once I get home and update this thread. Of course the work around is simple, just binding the pitch trim to POV hat left / right and the aileron trim to POV hat frwd / bckwrd, but if somebody at ED / FC has time to look at this. - PitbullVicious

When flying in dark conditions with the landing or search light on, some object textures do not "light up" or even show up as extremely dark / black. I made a simple video demonstrating this problem (with the landing light, search light produces similar results). Note that in the end there are short clips with the A-10C landing light that seems to work more or less the way expected. Computer specs: GPU: 2xGTX680 2GB SLi (NVidia driver v358.50) OS: Microsoft Windows 7 Ultimate (v6.1.7601) Processor: i5-3570K @3.40GHz Mem: 32GB MOBO: Asus P8Z77-V PRO Sound Card: Asus Xonar DG MS Sidewinder 2 FFB x 2 MFG pedals Track IR 5 Graphics settings: All max, no DOF or lens effects

I don't know if this is a silly question or not, but I was wondering to what extend is controlling the force feedback of MS SW II possible via LUA scripts. I've found the trimmer, invertX and invertY values of course in the vanilla input LUAs, but I was wondering if different "modes" of the FFB could be controlled via LUA? My aim is to add full force to the X-axis of the joystick, while applying some "friction" to the Y-axis. I.e. the X-axis would always center, and the Y-axis would stay where set. Is this possible? I think that this. plus removing the twist spring would make a pretty decent DIY collective stick for the UH-1h.. Another option would be some kind of physical mod to the stick itself eliminating the X-axis movement, but if possible I'd not modify the stick physically.

Same problem as this one? http://forums.eagle.ru/showthread.php?t=148420

Same problem here. Plus I get some flickering during the pod cool down. Made a short video of it here (whot and pod cool down): System specs: GPU: 2xGTX680 2GB SLi (NVidia driver v358.50) OS: Microsoft Windows 7 Ultimate (v6.1.7601) Processor: i5-3570K @3.40GHz Mem: 32GB MOBO: Asus P8Z77-V PRO Sound Card: Asus Xonar DG Warthog HOTAS MFG pedals Track IR 5

Update: Billeinstein came up with a workaround solution for this: http://forums.eagle.ru/showpost.php?p=2508655&postcount=6 The problem seems to be Microsoft IME (at least both Japanese and Chinese) and switching to English before launching the DCS Open Beta assures that all modules are loaded correctly. I hope that ED has time to fix this properly in the near future, now that the problem has been pinpointed. - PitbullVicious