Jump to content

Recommended Posts

Posted

Yep ... it was a very good source. ;)

[sIGPIC][/sIGPIC]

Reminder: SAM = Speed Bump :D

I used to play flight sims like you, but then I took a slammer to the knee - Yoda

  • Replies 1k
  • Created
  • Last Reply

Top Posters In This Topic

Posted

If ED has to read through 100+ posts just to realize that some guys want a completely new sim as a "patch", I guess there will be no 1.13 at all. We should focus on what is broken in 1.12a and should be fixed, not on what could all be very interesting.

[sIGPIC][/sIGPIC]

Posted
So, bright one...what part of this list isnt kosher with the rest of the communities needs (aside from I want this I want that because its being implemented into BS) ?

? Its your list, not the definitive list like your trying to make out, you've selected what you want from the communities wishes, bright one.:P

You say fix AMRAAM what about R-77 that misses bad too, or are you only interested in one a/c? What about ER?

"[51☭] FROSTIE" #55 'Red 5'. Lord Flashheart

51st PVO "Bisons" - 100 KIAP Regiment

Fastest MiG pilot in the world - TCR'10

https://100kiap.org

Posted
I just realised I should mention one more thing (after someone mentioned this bug in this thread before me):

 

In russian aircraft when you turn on the radar and sellect TWS mode... the first time you scroll the TDS box over a contact it will automatically lock it (IFF doesn't matter). This will happen every time but only the first time you scroll the TDS over a contact on the radar. This has to be a bug that I think should be fixed also.

This has never happend to me :huh:

 

2075291193_EDSig.png.650cd56f2b9a043311112721c4215a47.png

64th Aggressor Squadron
Discord: 64th Aggressor Squadron
TS: 135.181.115.54
Posted

Guys, there already has been a 'must fix' list for a long time - it was put together on the beta forums. This has been mentioned before. This list includes FM adjustment, missile issues, ECM and G modelling. As stated, as many things as possible will be fixed that are on that list.

[sIGPIC][/sIGPIC]

Reminder: SAM = Speed Bump :D

I used to play flight sims like you, but then I took a slammer to the knee - Yoda

Posted

I know it'll be bad question but how long we must wait for the new patch?

[sIGPIC][/sIGPIC]

Intel Core i7-6700K, @5GHz | Asus Maximus Hero VIII | 2 x eVGA GTX 970 SLI | Kingston Predator 16GB DDR4-3000Mhz | 2 x Samsung 850 PRO 240GB RAID-0 | AOC G2460PG G-SYNC LCD | OCULUS RIFT CV1 VR | THRUSTMASTER HOTAS WARTHOG | CH PRO PEDALS

Posted

Like Wags said, probably after Black Shark.

[sIGPIC][/sIGPIC]

Reminder: SAM = Speed Bump :D

I used to play flight sims like you, but then I took a slammer to the knee - Yoda

Posted
This has never happend to me :huh:

 

happens to me all the time. Try quick mission for the su-27... turn on the radar, set to TWS mode then scroll the targeting box over one of the three aircraft... once you get it over the radar strobe line, it will firstly automatically show range, then just a split of a second later it will autolock. Once I unlock then repeat the same, it will no longer do it, meaning I actually need to press lock to lock the target. Very anoying if you do that with friendly aircraft.

Windows 11 Home | Asus TUF Gaming B850-Plus WiFi MB | AMD Ryzen 7 9800X3D + LC AIO 360 | MSI RTX 5090 LC 360 | 64GB PC5-48000 DDR5 | 1TB M2 SSD x2 | NZXT C1000 Gold ATX 3.1 1000W | HOTAS Cougar+MFG Crosswind ... and waiting on Pimax Crystal Super VR headset & DCS MiG-29A release

Posted
happens to me all the time. Try quick mission for the su-27... turn on the radar, set to TWS mode then scroll the targeting box over one of the three aircraft... once you get it over the radar strobe line, it will firstly automatically show range, then just a split of a second later it will autolock. Once I unlock then repeat the same, it will no longer do it, meaning I actually need to press lock to lock the target. Very anoying if you do that with friendly aircraft.

 

Two problems may cause this:

First, when you switch in SNP (TWS) mode, in 75% range of the selected weapon the target is automaticaly locked on, the radar not just "tracking" it. So make sure while testing this bug, that you're way out the ranges of your weapon.

 

Second, if you brake lock, the radar returns to OVZ mode. (normal, with the 3 submodes; dunno what is it in english HUD)

 

I never had problems with that.

  • Like 1

[sIGPIC]http://www.forum.lockon.ru/signaturepics/sigpic5279_1.gif[/sIGPIC]

I could shot down a Kitchen :smartass:

Posted
...First, when you switch in SNP (TWS) mode, in 75% range of the selected weapon the target is automaticaly locked on, the radar not just "tracking" it. So make sure while testing this bug, that you're way out the ranges of your weapon...

 

yup, you're right, it will auto lock only when you are about 70-80% of the max-range of the selected weapon... but it does it only the first time you scrol the TDS over a radar contact. I don't know which one should be correct way.. should it auto lock every time you are in TWS and in range on the weapon, or never? I doubt doing it just the first time is the correct way...:huh:

Windows 11 Home | Asus TUF Gaming B850-Plus WiFi MB | AMD Ryzen 7 9800X3D + LC AIO 360 | MSI RTX 5090 LC 360 | 64GB PC5-48000 DDR5 | 1TB M2 SSD x2 | NZXT C1000 Gold ATX 3.1 1000W | HOTAS Cougar+MFG Crosswind ... and waiting on Pimax Crystal Super VR headset & DCS MiG-29A release

Posted
This has never happend to me :huh:

 

I think Kuky is specifically referring to a SOFT lock. That is- the target is bugged but the target is not being alerted about the extra attention he's getting.

 

Problem is- it will do this to ANY target even if it is friendly. The automatic switching to STT @ 80% of RMAX exasperates the problem because again- it will paint and LOCK the one prioritized- friendly or not.

 

His contention is this could not possibly be modeled correctly. If it is- the engineering team should be laughed off the planet.

Posted

no Konkussion... I mean, the target will be locked. I am not talking about F-15 TWS mode but rather Su-27/33 and MiG-29. Every time, only first time after I turn on the radar and sellect TWS (russian SNP) the moment I place the targetting cursor over the target, if I am within the weapon range it will auto lock, but it won't do it afterwards... this can't be right?

Windows 11 Home | Asus TUF Gaming B850-Plus WiFi MB | AMD Ryzen 7 9800X3D + LC AIO 360 | MSI RTX 5090 LC 360 | 64GB PC5-48000 DDR5 | 1TB M2 SSD x2 | NZXT C1000 Gold ATX 3.1 1000W | HOTAS Cougar+MFG Crosswind ... and waiting on Pimax Crystal Super VR headset & DCS MiG-29A release

Posted
I know it'll be bad question but how long we must wait for the new patch?

 

yup, your right because we will never see a 1.13 patch. Read between lines Ed no resources. Other more important projects. Don't mean to be a bubble breaker because I am wishing as hard as everyone that there will be a Patch. In RL I am afraid we are out of luck.:cry:

Posted
no Konkussion... I mean, the target will be locked. I am not talking about F-15 TWS mode but rather Su-27/33 and MiG-29. Every time, only first time after I turn on the radar and sellect TWS (russian SNP) the moment I place the targetting cursor over the target, if I am within the weapon range it will auto lock, but it won't do it afterwards... this can't be right?

When you switch to TWS mode the cursor snaps onto the nearest contact, then, at 85% range auto locks. (this is meant to happen)

 

If you unlock the target you will be switched into normal BVR mode, so you need to switch back into TWS (not sure if this should happen)

"[51☭] FROSTIE" #55 'Red 5'. Lord Flashheart

51st PVO "Bisons" - 100 KIAP Regiment

Fastest MiG pilot in the world - TCR'10

https://100kiap.org

Posted

Yep. That's what I sad, so I guess Kuky does not make this mistake. About how it SHOULD work, I'll ask the pilots.

 

Anyway, IFF in these planes is not that magical like in LO, if you move TDS over a target, there is an interrogator button in the stick, ZAPROS I think. In newer systems, with data-link, I've got no idea.

[sIGPIC]http://www.forum.lockon.ru/signaturepics/sigpic5279_1.gif[/sIGPIC]

I could shot down a Kitchen :smartass:

Posted
When you switch to TWS mode the cursor snaps onto the nearest contact, then, at 85% range auto locks. (this is meant to happen)

 

If you unlock the target you will be switched into normal BVR mode, so you need to switch back into TWS (not sure if this should happen)

Yes, thats right! A way around this, if you wanna keep a TWS track on the target within 80% of Rmax, is to select your shortest ranged weapon, say R-73s (since 80% of Rmax would be very close), til you want to launch. Then switch back to your weapon of choice and fire....Its stupid but works so and so.....

 

2075291193_EDSig.png.650cd56f2b9a043311112721c4215a47.png

64th Aggressor Squadron
Discord: 64th Aggressor Squadron
TS: 135.181.115.54
Posted

I agree with GG ?!?!?

 

Guys, there already has been a 'must fix' list for a long time - it was put together on the beta forums. This has been mentioned before. This list includes FM adjustment, missile issues, ECM and G modelling. As stated, as many things as possible will be fixed that are on that list.

 

I'd like to see the Beta Mashers "Punch List" addressed. They are going to be the best documented and understood possible changes. There for most likely to be properly and less painfully implemented.

 

Don't forget, this would be a good bye pat on the ass. They're done with us here.

 

But the 4 GG mentioned, are pretty reasonable in addressing the core "issues" that people have been pissin and moanin about for awhile. And would leave LO:FC in a much better post development position.

 

Attracting more late comers over the next few years to buy into the DCS modules. Which will come, understandably as a 2nd priority to any Mil Tech Contract.

Hair on the wall... Blood in the street... The

crush of bone ' neath my feet.

Posted

Maybe before we forget: it would of course be nice to have wide screen support right from within the options interface, instead of having to open graphics.cfg with notepad!

[sIGPIC][/sIGPIC]

Posted
Maybe before we forget: it would of course be nice to have wide screen support right from within the options interface, instead of having to open graphics.cfg with notepad!

 

Nice but not really important I think. This is an issue you CAN change by yourself. All the other stuff is a "no-go" for us, so...

[sIGPIC][/sIGPIC]

Asus ROG STRIX Z390-F Gaming, Intel Core i7 9700k , 32gb Corsair DDR4-3200

Asus RTX 2070 super, Samsung 970 EVO Plus M2, Win10 64bit, Acer XZ321QU (WQHD)

TM HOTAS Warthog, SAITEK Rudder Pedals, TIR 5

Posted

The wide screen support issue is important anyway. And these are the kind of fixes devolopers first pay attention to.

My rig specs:

Intel Core i7 4770 @3.4Ghz // Corsair 16GB DDR3 // MoBo Asus Z87K // HDD 1TB 7200RPM // eVGA Nvidia GTX 760GT 2GB DDR5 // LG 3D 47" 1920x1080 // Thrustmaster Warthog HOTAS // Saitek Combat Pro Pedals // Thrustmaster MFD Cougar pack // PS3 Eye + FTNOIR

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...