Patch 1.13 Requested Features/Fixes List (*Merged)

[bestiajo]

MULTIPLAYER REFUELING

 

After reading all threads in that forum i have seen people focused in new plane models, terrain, clouds, etc.. We are talking about a patch to fix problems in present game, seriously i think ED forgot to patch what i think is the most important bug of the game instead any others, what im talking about is MULTIPLAYER REFUELING!!! where client cant see the refueling baskets or dont have visual contact, this is a big bug to fix to be more playable and to expand online game capacities and features.

We have to think that there are a lot of online missions and this is a very important feature in the mission.

So, from here I want to say to ED to solve or fix this problem.

I hope this will be fixed in 1.3 patch. ;)

 

Sorry about my english, maybe there are mistakes.

[G3]

a interesting read this thread,

it has visualized what i have struggled to understand in the past.

exploits, thanks for the vids, fingers crossed for the patch.:music_whistling:

[A.S]

Having spent the last half an hour going through the thread and reading most of the "suggestions". It disappoints me the attitutde of many who have posted their. I just cant help thinking that when the senior members of ED read these replies they dont feel compelled to bend over backwards for this community. It sort of makes more sense why the first aircraft in DCS will be Attack Helicopters and NOT fighter Jets.

 

What is so surprising about a clean F15 out maneuvering an Aim120 in a barrell roll if you get it just right. If you are doing 400-450 knots, know the missile is coming which is doing 1500 knots plus, you should be able to out turn it. Missiles are fast but they cant turn very tightly.

 

Notching: ok so you cant lock the guy but you can see him, and set yourself up for the advantage at the right time. Also see what happens if you let off a couple of AIM 120's in the situation pointed just a little in front of the target.

 

Orthagonal roll: Same as Barrell Roll If you can see the missile coming there will allways be a way to out maneuvre it. As you can see in the video, they dont miss by very much.

 

Im not pretending that LockOn is perfect, I never have and we can be sure it never will be. Lockon is a "survey Sim" not a study Sim.

 

True true, i have to agree on that too, but few things are just too OFF and we have to point to it.... how else improvements could take place if not interactive with the pilots...... Doesn´t matter if Sukhoi or ED is building a Plane, they all get inputs from the pilots....... and this all isn´t that bad in my opinion, it more like a comminicative way of searching better ways.

[tflash]

What might be helpful is a kind of "executive summary" or "readers digest" of this 380+ thread.

 

In fact, this cannot be done in the forum format, we might need a wiki page, does one of the community servers have one?

[Geier]

What might be helpful is a kind of "executive summary" or "readers digest" of this 380+ thread.

 

In fact, this cannot be done in the forum format, we might need a wiki page, does one of the community servers have one?

 

Don't forget S-kid's thread about F15 fixes are nedeed firstly

 

http://forums.eagle.ru/showthread.php?t=5658

 

deas to date (07/12/2004 - need to be re-ordered):

1. To fix the code and separate the HSI nav system from the combat modes on all aircraft (not just F-15), so that the HSI continues to show the NAV information about the next waypoint even when the radar or other systems are being used against a target.

2. To implement a finite angular and range resolution for all radars, so that closely spaced targets at a distance appear on the display as a single target.

3. To use time-limited "legacy" tracks, so that targets leaving the TWS scan zone, or returning from STT to TWS, not all tracks are immediately lost.

4. To review the operation of the TWS mode, and ensure that it is not going into STT incorrectly when a target is designated (needs further discussion, especially regarding ECM targets).

5. To ensure RWR is working correctly (needs further investigation, especially regarding accurate symbology).

6. To allow the AIM-120 Rmax zone to expand if the F-15C pitches upwards at the moment of launch, to represent pilot-assisted "lofted" launch trajectory.

7. To implement the "Sort" ("Expand"?) submode, which zooms in the radar display to help "break-out" closely spaced targets.

8. To replace the existing "burn-through" model with a "kinematic ranging" AOJ submode, for estimating the range to an ECM target.

9. To introduce a fighter datalink display on the MPCD (needs further investigation, which F-15Cs actually have such feature).

10. To introduce an air-to-ground radar mode.

11. To let chaff be more effective when rearwards-facing ECM is used.

12. To introduce the "passive Sniff" mode.

13. To let the pilot manually "interrogate" IFF.

14. To review the close-combat auto-acquisition modes (include SuperSearch and ensure correct lock-on range).

15. To introduce the Python and other Israeli weapons.

16. To add color to MPCD display.

17. To introduce night vision goggles (NVGs).

18. To let a single ECM aircraft cover other targets near the same bearing

19. To expand TWS mode with (N)DTWS and HD(ND)TWS

20. To include low-altitude, Med-PRF clutter on the radar display

21. To include Vector and Range Gated High (RGH) search modes

22. To include the "miniraster" function while locking a target

23. To make the arrestor hook functional

24. To ensure the "automatic trimmer" is working correctly

25. Default Master Arm switch to off during ramp start.

26. Add ADI and VI master modes

27. Research the Israeli helmet-mounted sight

28. Collimated HUD display that moves with pilot head, as in Il-2

29. Correctly scaled HUD wrt other instruments

30. "Data fusion" model for use with datalink - AWACS has limited detection range

31. Check for any radar gimbal limits in roll during scan and TWS mode, as on Su-27

32. Check to ensure gunsight radar lock is not being lost at close ranges or in vertical flight without reason

33. Check to see if lock is lost in co-speed tailchases in real life

 

Thanks for your interest,

 

-SK

 

Lock On v1.1 "Flaming Cliffs" beta tester

[Pilotasso]

Those fixes would more than do it for me. At least untill a new and better SIM is donne.

[yar]

Those fixes would more than do it for me. At least untill a new and better SIM is donne.

And those fixes will never get into game ... you can be shure...

 

and if there would fixes, none of them would fix the western jets, only the russian products ...

 

 

i can wager something, ED wont fix anything :(

 

 

 

-bm-

[Rhino104]

BE ABLE TO REWIND REPLAY TRACKS!!

[Weta43]

and if there would fixes, none of them would fix the western jets, only the russian products ...

 

 

i can wager something, ED wont fix anything

 

This post should win First prize in the uninformed comment contest

[UWBuRn]

Those fixes would more than do it for me. At least untill a new and better SIM is donne.

 

What a reasonable request in the 1.13 contest... almost requesting a F-15 DCS module with that list. :music_whistling:

 

I taught was clear that the patch is definitely not about new (at least, so relevant ones) features. :smilewink:

[Pilotasso]

you are right but you dont seem to understant why so many features are in that list. I cant tell you nor can anyone else tell you why exactly they are there except that maybe its important for the ongoing negotiations. ;) ;) ;)

[plane00]

Lift line in canopy & moving smoothly toward center view for no-trackir users

 

same as above, trivia wish

[yar]

one point, which should be fixed is the missile speed.

for example the real aim-120's speed is Mach 4, in lock on the max. speed is 3037 kmh, which is less than Mach 2!!!. All versions of the amraam (A/B/C) fly up to mach 4 and not mach 2-.

this would increase the range to 75km (aim-120A/B) and ~ 100 km for the C (C-5 has 105km)

 

Same for the R-77: real speed: mach 4 (Lock on speed: 3321kmh) with a range of 90km.

 

 

 

I dont know what happend to ED: there are 3 different speed's for those missile: Real speed (more than 2 times faster), in game speed, and the speed in the Encyclopedia ...

 

-----------

(ive done all lock on speed tests from with speed 500kmh and 2000m over NN)

[GGTharos]

Have you considered that mach speed is different at different altitudes, -and- that due to air resistance, a missile launched at low altitude will be slower? Not that you're wrong in general, but your numbers are a bit off.

 

AMRAAM is aircraft mach + 4. R-77 will be a little slower, thanks to those potato mashers.

[yar]

Have you considered that mach speed is different at different altitudes

yes, i know that... :smilewink:

 

you can fly with mach 2, this wont affect the missile speed. If you start 10.000m over NN, turn 90 degrees down (vertical) and fire a amraam 10.000m vertical into the ground, it wont reach more than 32xx kmh ;)

 

 

 

Please tell, how i can get a aim-120 or r77 to fly with mach 4 :P

[GGTharos]

Sorry, I meant the real missile's speed is such. I am well aware of the issues with missiles in LOMAC. ;)

I know how you can get it to fly at mach 4 ... ask ED to change the max mach limit :D

[Shaman]

This thread is getting terrible. It's gone really off topic. There's no real list in here. I wouldn't even bother to read this if I was a developer,- waste of time really. There should be an objective comprehensive list in the first post of requested fixes for 1.13 to things that have been discussed and everyone in community agreed that they should be actually fixed/changed (no one opposed).

[GGTharos]

The developers already have a list I'm sure.

This is stuff that's just being rehashed as if ED hasn't heard nor taken note of it. They have, a long time ago. It's logged in some bug database or another, I'm sure of that.

What WILL get fixed for the patch is not too well known.

[yar]

but i think a list from the community could help a little bit...

[GGTharos]

Not, it wouldn't. The list has already been gathered from teh community's wishes. The community has so far been rehashing the same ole. Nothing new.

[yar]

you are betatester, so im shure you must know it.

 

i know its a stupid idea, but if we get no patch (and to 99% we wont get one), we could try to make a unofficial one / ask ED to let some people to this.

(only for the most important fixes, like the missile, the shadow etc.)

[DarkWanderer]

...stealing the source codes?..

[3Sqn_Fudd]

This thread is getting terrible. It's gone really off topic. There's no real list in here. ...........

 

Ill probably run through and make a list, it wont be hard.

 

I'll include every idea regardless of how obtuse it is...

[vadIL]

...stealing the source codes?..

 

Dont be so shoked about it!!

 

If ED wont release any patches that mean its the END of Lockon!

I guess there are some people that can do some "home made" stuff..

Anyway I hope so..

I dont want to see the end of lockon...

[yar]

Ill probably run through and make a list, it wont be hard.

 

I'll include every idea regardless of how obtuse it is...

 

thx fudd! if i can help you, this things should be fixed

 

• Missiles (speed, range, seeker etc.)
  
• cloud shadows (this could make you crazy -.-)
  
• 'jumping' water
  
• a REAL IFF for the F-15. If you lock a friend in RL, there is a big cross over the ASE circle
  
• ( the cockpitbug in the F-15, its not importantat but should be fixed )
  
• ( the awacs -> i dont want a contactinfo which is more than 200nm away, if i request a declare!!!)
  
• maybe the israel python missile (but i think without HMTD, because that is to much to do)
  
• the speed of the aircraft should affect the missile speed
  
• maybe im the only one, who wants this, but it would be nice if you could fire only one flare
  
• i dont know if its possible, but do something against this **** warping!
  

 

k, additional some things of this list:

 

Ideas to date (07/12/2004 - need to be re-ordered):

1. To fix the code and separate the HSI nav system from the combat modes on all aircraft (not just F-15), so that the HSI continues to show the NAV information about the next waypoint even when the radar or other systems are being used against a target.

2. To implement a finite angular and range resolution for all radars, so that closely spaced targets at a distance appear on the display as a single target.

3. To use time-limited "legacy" tracks, so that targets leaving the TWS scan zone, or returning from STT to TWS, not all tracks are immediately lost.

4. To review the operation of the TWS mode, and ensure that it is not going into STT incorrectly when a target is designated (needs further discussion, especially regarding ECM targets).

5. To ensure RWR is working correctly (needs further investigation, especially regarding accurate symbology).

6. To allow the AIM-120 Rmax zone to expand if the F-15C pitches upwards at the moment of launch, to represent pilot-assisted "lofted" launch trajectory.

7. To implement the "Sort" ("Expand"?) submode, which zooms in the radar display to help "break-out" closely spaced targets.

8. To replace the existing "burn-through" model with a "kinematic ranging" AOJ submode, for estimating the range to an ECM target.

9. To introduce a fighter datalink display on the MPCD (needs further investigation, which F-15Cs actually have such feature).

10. To introduce an air-to-ground radar mode.

11. To let chaff be more effective when rearwards-facing ECM is used.

12. To introduce the "passive Sniff" mode.

13. To let the pilot manually "interrogate" IFF.

14. To review the close-combat auto-acquisition modes (include SuperSearch and ensure correct lock-on range).

15. To introduce the Python and other Israeli weapons.

16. To add color to MPCD display.

17. To introduce night vision goggles (NVGs).

18. To let a single ECM aircraft cover other targets near the same bearing

19. To expand TWS mode with (N)DTWS and HD(ND)TWS

20. To include low-altitude, Med-PRF clutter on the radar display

21. To include Vector and Range Gated High (RGH) search modes

22. To include the "miniraster" function while locking a target

23. To make the arrestor hook functional

24. To ensure the "automatic trimmer" is working correctly

25. Default Master Arm switch to off during ramp start.

26. Add ADI and VI master modes

27. Research the Israeli helmet-mounted sight

28. Collimated HUD display that moves with pilot head, as in Il-2

29. Correctly scaled HUD wrt other instruments

30. "Data fusion" model for use with datalink - AWACS has limited detection range

31. Check for any radar gimbal limits in roll during scan and TWS mode, as on Su-27

32. Check to ensure gunsight radar lock is not being lost at close ranges or in vertical flight without reason

33. Check to see if lock is lost in co-speed tailchases in real life

( http://forums.eagle.ru/showthread.php?t=5658 )