Jump to content

[OLD BUG REPORTS] Cleaning and Organization of old posts


RAZBAM_ELMO
 Share

Recommended Posts

This is actually important because it highlights how radio is supposed to work. I was looking for some info on that but everyone seemed to actually completely ignore the issue and assume that the rocker on the throttle acts as radio PTT. That's how SRS and I think VAICOM treat it, even though it's been mentioned in many places that rocker is used for radio SELECTION. Well, this debacle seems to accidentally explain what is going on - the rocker indeed only selects the radio, and button number 8 on stick is PTT. At least that's how I understand it and it would mean that the closest HOTAS mapping would be to map whatever stick button was used for STT/TWS switch to Communications instead (or SRS PTT), and map STT/TWS to TDC press instead. Can any of the devs weigh in on this?

Link to comment
Share on other sites

  • Replies 1.4k
  • Created
  • Last Reply

Top Posters In This Topic

Not sure how long this has been happening, but I recently got into the Mirage after about a year, and discovered I could not lock a target. The target shows up on the screen and blinks preventing me from locking them. I lock for a second and then it breaks lock. When I get closer, I can lock them with special modes , but not until I get in range. Not sure what is going on, never had that before.

Link to comment
Share on other sites

It's more realistic radar behaviour introduced with the latest update.

 

Absolutly beverly contract disappear after each swipe. There is no buffer or memory, it's redrawing it.

Was shocked at first but it is...

 

... each bar is a separate swipe. So if a contact is detected buy first bar but not the other he will appear only when the first bar is swiped again.

 

https://forums.eagle.ru/showthread.php?p=4114151#post4114151

i9 9900K @4.7GHz, 32GB DDR4, RTX2070 Super 8GB, 1TB NVMe, 6+4TB HD, 1+1TB SSD, MSFFB2 joystick, X52 Pro Throttle, TIR5, Win 10 Pro x64, 1920X1080

Link to comment
Share on other sites

I had a hard time reproducing organically with AI so I went online and was able to reproduce. The wing break occurs during the second engagement as I cross the F-16's wake turbulence.

JustDogFight_Caucasus_v2.4ga-20191124-204307.trk

[sIGPIC][/sIGPIC]



64th "Scorpions" Aggressor Squadron

Discord: 64th Aggressor Squadron

TS: 195.201.110.22

Link to comment
Share on other sites

I have reported this in our system, I am sure RAZBAM will take a look also.

 

thanks

smallCATPILOT.PNG.04bbece1b27ff1b2c193b174ec410fc0.PNG

Forum rules - DCS Crashing? Try this first - Cleanup and Repair - Discord BIGNEWY#8703 - Youtube - Patch Status

Windows 11, NVIDIA MSI RTX 3090, Intel® i9-10900K 3.70GHz, 5.30GHz Turbo, Corsair Hydro Series H150i Pro, 32GB DDR @3200, ASUS ROG Strix Z490-F Gaming, HP Reverb G2

Link to comment
Share on other sites

Yea, would be nice if this could be fixed as soon as possible, as this bug is ultra-annoying for people who like bfm.

Can't count the times I've been behind an enemy in favourable position , working on a gun solution, only to have the aircraft disintegrate below me because I flew through his wake.

 

Thank you.

 

Kind regards,

 

Snappy

Link to comment
Share on other sites

So I was playing and realized that I couldn't find bogeys when pointing radar cone exactly at their range/altitude when there is altitude difference. It's specially noticeable when operating in one bar scan. So I made a test mission where i fly at 20000 feet, and bogey is flying hot at me at 3000 feet:

 

 

So something is off. Horizontal scan ccm is the same thing, if there is significant dive/climb angle, when I elevate/lower movable dashed line and put it on the bogey, it doesn't lock, but if i put it above/below the bogey enough: it locks.

Also it seems that I can only detect bogeys at some distances like say 25 miles, but when he gets closer, he disappears i can't pick him up again on regular basis. Although that might be related to previous bug.

 

Also some other behaviors I noticed:

Before when you moved antenna up and down number of bars would always be locked near antenna symbol, but now it moves separately as demonstrated here:

 

 

Bug or feature? If bug, maybe related to elevation problem.

 

Another behavior: In one bar scan, when you move elevation, antenna movement displayed by antenna position symbol is not smooth:

 

 

Bug or feature?

LOOK MA, NO HOOK

Link to comment
Share on other sites

Hi all,

 

 

Today I decided I would finally start learning the Mirage, so I fired up the first training mission (cold start). When I got to the radios part, it says I should set the V/UHF radio to Pal, but this seems to have changed with the new radio from the cockpit update. Since I can't do that action, the tutorial never moves along.

 

 

I can obviously make up for it with YouTube video tutorials or something, but it's a pretty crappy experience for newcomers. It also makes me afraid that I will be running into similar bugs further on, or even during the campaign :(

Link to comment
Share on other sites

still broken after the update

 

What? really? Haven't tested yet since update, but it said in the update notes it was fixed.

Motherboard: ASUS ROG STRIX Z390-F GAMING
CPU: Intel Core i7-9700K 3,6GHz/4,9GHz Turbo
GPU: KFA2 NVIDIA RTX 2080 EX
RAM: 2 x Corsair Vengeance LPX Black DDR4 3000MHz 8GB
VR SET: HP Reverb G2

Link to comment
Share on other sites

The RWR fix was due to my error, had a model version screw up when fixing a different bug and it reset the RWR connector to the model that was causing the error. I didn't realize this until after it was released.

 

I am truly sorry about this. I have already made sure that the fix is in the repository to be pushed out on the next update.

[sIGPIC][/sIGPIC]

We take the Metal and bring it to Mesh

Link to comment
Share on other sites

Np Tim, thanks for letting us know. Not possible to edit a file or something on our part to fix it until then?

Motherboard: ASUS ROG STRIX Z390-F GAMING
CPU: Intel Core i7-9700K 3,6GHz/4,9GHz Turbo
GPU: KFA2 NVIDIA RTX 2080 EX
RAM: 2 x Corsair Vengeance LPX Black DDR4 3000MHz 8GB
VR SET: HP Reverb G2

Link to comment
Share on other sites

The RWR fix was due to my error, had a model version screw up when fixing a different bug and it reset the RWR connector to the model that was causing the error. I didn't realize this until after it was released.

 

I am truly sorry about this. I have already made sure that the fix is in the repository to be pushed out on the next update.

 

Thanks for the reply and for your mea culpa, shit happens.

Same question : is a file or hotfix possible ?

Link to comment
Share on other sites

I just found a similar thread with repies from BalticDragon in the Training Missions subforum. He seems to be on it already. Sorry for the noise.

 

Yes, but from what he says, it will be some time before this and others are fixed.

Intel i7 12700K · MSI Gaming X Trio RTX 3090 · ASUS ROG STRIX Z690-A Wi-Fi · Acer 4K 32" XB321HK · Samsung 970 500Gb M.2 NVMe · 2 x Samsung 850 Evo 1Tb · 2Tb HDD · 32Gb Corsair Vengance 3000MHz DDR4 · Windows 11 · Thrustmaster TPR Pedals · TrackIR5 · Thrustmaster F/A-18 Hornet Grip · Virpil WarBRD Base · Virpil Throttle MT-50 CM3 · Virpil Alpha Grip · Virpil Control Panel 2 · Thrustmaster F-16 MFDs · HTC Vive Pro 2 · Total Controls Multifunction Button Box

Link to comment
Share on other sites

 Share

  • Recently Browsing   0 members

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