RvE LRM 2.0 preview

[Kuky]

Meaning scan/nails not detected until around 55 km.

STT spikes around 70-80 km with sound and 130 km visual only

 

And why did you implement this Yoda? You want TWS nails not to be detected from F-15 so you can fire TWS 120's from high altitude? I don't like this at all... I think you've gone to the wrong side with this mod now.

[GGTharos]

Actually it would represent the degraded sensitivity and foggy SA just a little closer to real life probably.

 

People use the RWRs as some sort of primary sensor for hunting other aircraft and as far as I know, you have a radar because those are just not suitable for such things ;)

[Kuky]

yeah but not to get any warning at all from someone who's within firing range is bit too much. That can't be realism.

[GGTharos]

I've heard it can be but ... I've heard :P

[Kuky]

You know you might argue that for really old aircraft/systems something like this is the case... but not with Su-27 for sure or the MiG-29S... or the F-15. If the RWR works like that in modern aircraft that would be just stupid to have an RWR then.

[GGTharos]

I can definitely argue it for any aircraft carrying a Beryoza. The RWR is there to warn you; right now certain RWRs give you a far better ability to get a picture than they should in LO.

[RvEYoda]

And why did you implement this Yoda? You want TWS nails not to be detected from F-15 so you can fire TWS 120's from high altitude? I don't like this at all... I think you've gone to the wrong side with this mod now.

 

 

Kuky did you miss the part of this not being part of LRM?

This mod probably gives more edge to those with ERs than 120s.

 

And even if it would have been part of LRM it can be

selectively disabled by server admins (like any other LRM feature),

as stated quite a few times before. It is NOT part of LRM.

 

Why the mod?

Because a single search sweep from 100 nm should not every time, instantly

trigger rwrs with perfect bearing, range, everything, unless you brought

em from the 2050s ;). Not even if you put an optimized radar array at that point

(recieving end, also one at emitting) would you get this kind of perfect informtion

on everything by one *ping*. Consider now the antennas with a much worse

reliability in terms of angular coverage/distinct lobes etc, how they must be made

not optimized for small frequency bands, but an incredibly wide range to deal

with all sorts of emitter types (unlike your radar's recieving end), etc.

You just won't get the kind of detailed information, and it would take a bit of

work on any signal to identify it's type.

 

People are using unreal 100% super reliable RWRs as their primary

BVR sensor, completely ignoring radar, and that from downright dumb ranges.

 

I would also like to remind you that other, more advanced sims already have this feature.

Meaning if you put less radar avg (over time) energy/second on a target,

his rwr has less chance of picking you up (combined with more reasons).

This is also of course highly distance dependant. (in fact in there,

the ranges would be even less(!))

 

Lockon's basic model is just that - basic. All aircraft get the same rwr range/sensitivity

numbers or too close to make out differences between (only diff being detection angles).

And I would also have like to make this aircraft dependant if I got intel on that stuff.

However I dont have any,so I'll just stick with lockon's idea and keep all ac equal.

Edited April 18, 2009 by =RvE=Yoda

[Kuky]

Ah well, what can I say, I am for realism and if RWR's do work like this then I'll just have to accept it... I have to admit that I am bit sceptic on it though but then again who am I to argue if it's correct or not as I don't have first hand info or experience in such real life hardware.

[RvEYoda]

Basically, this should provide client flight behaviour much closer

to what is reality. It's still a lua script/hack though, I wish we could make

it MUCH more advanced and transparent, but, as has been said,

this is for everyone to chose theirselves if they want on their server.

[Udat]

I, like kuky am interested in realism, and while perfect bearing and distance from a quick scan 150km away really probably isn't realistic at all, I feel that 55 km might be a bit on the low side. I'm not an expert at all, but the part where you build a mental picture of the nearer parts of the battlefield based on the combination of radar and rwr is to me maybe the heart of air-to-air in lockon.

 

Hmmm, if it isn't very much work for you to make 55km nails RWR detections, maybe it's be cool to have the option to select 3 or 4 different rwr "strengths" that the server admins can choose from?

Edited April 18, 2009 by Udat

[Kuky]

I just flew in RvE test server and the RWR mod didn't seem to bad... when ever the enemy aircraft was in any vicinity you should know about I got the nails on RWR so looks like I was bit harsh on Yoda implementing this.

Edited April 18, 2009 by Kuky

[RvEYoda]

Set it to whatever number you like :).

 

It's just two numbers there available for edit

[RvEYoda]

I just flew in RvE test server and the RWR mod didn't seem to bad... when ever the enemy aircraft was in any vicinity you should know about I got the nails on RWR so looks like I was bit harsh on Yoda implementing this.

 

 

Remember, 55 and 70 km are for reliable detection ...

you can still pick it up farther away if you are lucky ;).

(which you are quite often)

 

My personal opinion is that it was nice to have some

silence in the cockpit, not always having an rwr screaming

"oh noes, bandit 150 nm 12 oclock"

[Udat]

Hmm, if you can pick it up farther away it suddenly sounds a lot better! And yes, the constant chirping in the us planes can be a pain in the ass. Sounds damn cool now suddenly :)

 

Edit: did you test it with long-range sam sites?

Edited April 19, 2009 by Udat

[Udat]

I won't presume to talk for yoda, but if you are referring to parts of the mod getting too far from original lockon, he have stated time and again that all parts of the mod will be optional, so that servers can pick just the parts that they want to use ;)

[RvEYoda]

If it was possible to edit things more advanced, I would make WAY

more deep stuff. Unfortunately all we can do is add scripts that

affect "ourselves"

[herig2]

I hope this is were I can post LRM 2.0 Test Server remarks. I been flying on it for the last week. Its been good, Good FPS and very stable. The mission is great for my A-10. However today 4-22-09, at 2:52 PM EST. When I log on, I'm setting in the cockpit, and a Warning window pops up ( Mission Pauses-Interrupt- ). As I sit there the HUD cycles though its colors. When I hit cancel the window reappears. I had a ping of 135, change the skin to USA Flipper and my # to 17.

[RvEYoda]

I hope this is were I can post LRM 2.0 Test Server remarks. I been flying on it for the last week. Its been good, Good FPS and very stable. The mission is great for my A-10. However today 4-22-09, at 2:52 PM EST. When I log on, I'm setting in the cockpit, and a Warning window pops up ( Mission Pauses-Interrupt- ). As I sit there the HUD cycles though its colors. When I hit cancel the window reappears. I had a ping of 135, change the skin to USA Flipper and my # to 17.

 

 

Thank you, bug has been corrected!

 

This bug appeared when solving the localization issues with

russian lockon.

 

both issues should now be solved.

If you still get this problem its because this payload you have selected

is not allowed in RvE Maple Flag event that will run on saturday.

 

The server right now in HL is not a demonstration of LRM 2.0,

it's a test to find these bugs and fix them before the weekend release :)

Edited April 23, 2009 by =RvE=Yoda

[Feuerfalke]

Finally LoMAC get's some multiplayer gameplay added - reinstalling. :pilotfly:

 

 

 

Thanks for your hard work!

 

@ED: Hire this man! :D

[RvEYoda]

Ok finally got down to business and did some work

against the ECM flashing. Getting slightly annoying about

enemies thinking BVR is a game of who can press

E the fastest.

 

sure on and off ECM can be effective irl.....however...

the game's representation removes more realism tha

it adds, so I made some fun stuff against it.

 

Ok so what does it do?

Right now it only works for F-15 because I havent had time

to write the russian version of the functions yet.

 

But, what it basically does is :

if lost lock : Log /Temp/ECM_log.txt *lost lock on *username* at *time**

 

if it then picks up the guy as ECM : it RELOCKS the bastard

Log /Temp/ECM_log.txt *auto-lock on ECM *username* at *time**

 

So it makes the result of ECM flash a little less pronounced

and also it gives everyone the ability to see who is doing the flashing,

report it to the server admin and BAN that IP.

 

. out

 

About the russian aircraft anti flash :

if anyone feels like writing a lua function that puts the target cursor

in mig29, su27 and su33 on top of a given ingame object or object ID,

I could just shove that code in there and we'd have this for all planes.

Edited April 23, 2009 by =RvE=Yoda

[RvEYoda]

Release will be very early sunday morning,

Right after RvE Maple Flag is finished.

 

Release posts for LRM2Beta1+AMRACT have been prepared!

[RvEYoda]

Release is delayed due to CTD problems at today's Maple Flag

[104th_Crunch]

Take your time to squash those bugs good.

[STRIKER]

Speaking of Maple Flag....doesnt anyone have a track that they can share/link. Thanks

[PoleCat]

Fast work addressing those issues Yoda!

Thank you for the continued efforts.

 

Out