Dugong

What are you basing the the more accurate than ever before on? I tested the new RWR behaviour against M2000, F15, F5, A4E & Mig21 and found the following; -Detects ALL aircraft radars at 80km -Flashes/Tone noticeable increase in rate at 35km for ALL radars -Powerfull radar (M2000/F15) has all four lights when locked @ ~30km & no sort of launch indication. -Older radars (A4/f5/mig21) have no indication of lock outside of 4km -Older radars have all four lights at 4km exactly and less. To me this doesn't seem particularly realistic, especially the identical detection ranges of massively different power radar systems. It just seems we have 2 different rwr scripts for old/new radar. I havent testred ground radar yet to see if its the same sort of behaviour.

On my machine it seems the text on the A10C HUD is much less crisp than every other module (and for some reason much harder see in bright conditions), even than the KA50 which is an older module. Is there any way, or any mod to make the text sharper?

Nowhere i don't think, they seem to have stopped bothering to do them.

Are you on the beta or the main branch? It really strange, i tried setting a C130 up in the editor flying straight and level with no manouvering and the R3R still does the same thing, a dive straight towards earth! I can launch at max range or 1-2km and it still does the same thing every time.

Anyone else had this? They get to within a few hundred feet of the target and then execute a 90 degree dive towards earth. Doesn't matter what launch distance.

Radar symbols are still inverted as well.

Indeed it's back to the hangar for the 21 again! No launch tone for R3r, can't launch R3R as part of a mixed pair, countermeasures not working, gun solution for ground target falling well short, weapon selector still absolute rather than preference, Jammer mostly inop. :(

Nope, we probably need real life bombing charts but i haven't been able to find any online, and the LN manual is no help. Mind you i'm not sure if the ASP has got full proper functionality implemented yet as patch notes for the 21 are bad to non-existent, which doesn't make bug finding very easy.

Hey Cobra, can we have a guide on how to use the SPS jammer pod please. I've fiddled with it for ages, even found some details (in italian) online but can't get the in-game version to do anything apart from dispense flares manually.

Has anyone else not been to exceed Mach 1.1 with the hotfix installed, or is it just me being retarded?

Cobra, has any of this been patched to 1.5 open beta yet? As far as i can discern, all the things listed in the first post from 3 months ago are still broken.

No, it doesn't seem to work properly at the moment. I've been trying to test it and figure out how/if it works and as far as i can tell it only seems to have very basically simulated jamming like the flaming cliffs aircraft.

but it isn't, im still getting problems more than half the time!

Everything was performing really well with 1.5.2, but now with the 1.5.3 patch im getting good fps (50fps+) but enormous lag spikes/stutters in MP only. In single player it seems fine, maybe a bit worse than 1.5.2, however MP is pretty much unplayable as it stands.

Were there any MIG21 bug fixes in the recent 1.5.3 patch? All the issues in post 1 are still broken for me:(

Similar issue here using the http updater. The download stopped after 400mb with a time out error and now i can't update at all. The launcher just launches 1.51 without checking for updates.

Any update on this, is it being looked at or worked on? It seems as if there are still no force feedback features implemented.

What is going on, i've got 1.5 beta and the standard 1.2xx and ive just had to waste another 2 activation keys on top of the 2 last week! It's saying i have changed hardware but haven't updated computer in years, this is getting to be a bit of a mickey take. At this rate im not going to be able to fly the mig if they keep on releasing patches.

It seems there is a problem with the lock tone and indication light (no62). I've tested with R60/R60m and if you are in IR mode and lock the target with radar, the IR lock tone will sound & indicator 62 will light (suggesting you have IR seeker lock, even though you dont). If i then unlock the radar the tone and light will remain on, but of course i have no IR lock so launching just sends the missle of in a straight line. In realistic IR missile mode this means you have no indication whatsoever that you have a IR missile lock if you have previously locked the target with the radar. It seems in IR mode, the tone and light 62 are indicating radar lock and not missile lock. However if you don't use the radar at all, the tone and indicator light seem to work fine.

Ah okay thanks Harle, didn't realize that the previous CCIP was a cheat. Did we ever get to a conclusion on how the ASP actually functions in real life for the various modes? From testing Air to Ground, It would seem for rockets, in AUTO mode the asp behaves in a CCIP manner in both gyro and msl modes, and it doesn't seem to matter if radar is on/off/fixed beam (the intercept angle knob still doesn't move as it says it should in the manual). For guns though, i can't really tell if its working at all. It doesn't seem to calculate aim point at all in the horizontal axis, and the vertical aiming point doesn't seem much better. I find it much easier to aim the gun with the fix net at the moment. Thankfully though the AA modes seem to be working as intended.

Yup the AA gun radar ranging does seem to work fine now. It does seem to stop working when you get too close to the enemy aircraft, not sure if it's supposed to be like that or not. But, it seems like the asp pipper now does nothing in air to ground mode with either guns or bombs. Rockets seem to work fine, but with bombs the pipper just locks itself to a point on the lower right of the glass and doesn't move at all. With guns the pipper seems to point to the wrong side of the asp glass, as if the aiming calculation is accidentally inverted in the horizontal plain.

Same thrust bind issue for me, but i don't have the slider bound to anything at all. Joystick is an X52 pro.

Okay so i copied headtracker.dll from my steam install into the open beta install. Now the SU25T works, but some of the axis' have inverted, but none of my paid modules work! Do i need to copy all the individual aircraft profiles from steam to open beta as well?

As per title, v2.2 freetrack works perfectly fine in the non-beta mainbranch, but absolutely cannot get it working in 1.5, any tips? Many Thanks

Hello, hopefully a simple question for you guys. I have my current install and modules through steam. Can i download the standalone beta and have that active at the same time as the steam version, or does the act of activating the keys on standalone deactivate or otherwise render the steam keys invalid? Many Thanks