hollowman8904

I ran into the radar not picking up a contact again in multiplayer. Apparently my Tacview export isn't working right, so I don't have a replay to show you, but I did capture a video. The contact doesn't appear on my radar until I lock him using CCM mode. After I exit CCM, it loses the contact again shortly after. Hopefully this helps. I'll try to get a track next time I play.

Same here. It seems that all of a sudden the radar can't hold a lock. Half of the time, contacts don't show on the radar, even though I can visually see the contacts in front of me. The problem seems to have appeared within the last update or so.

Servers will generally advertise their TeamSpeak or DCS Simple Radio IP addresses in the server description if they use one.

It works fine for me. Make sure your INS is aligned. A quick way to check if you are aligned is to compare it to your emergency compass that pulls out above your INS num pad.

I am having this problem as well. Even after pressing unlock and having the original target way off axis with a new target dead-ahead, it still relocks the old target.

Gpu-z is a good lightweight program to check your gpu utilization. Sent from my iPhone using Tapatalk

Is there a way to cycle what weapon store is active? I guess what I'm looking for is an easy way to switch from the Super 530s, to Magics, and back to Super 530s again without taking my hands off of the HOTAS. I suppose I could map the "Store 1" and "Store 2" select buttons, but I'm trying to find a way to consolidate since spare HOTAS buttons are hard to come by :joystick: Thanks

When is it appropriate to use the different radar modes (high/interleaved/low)? The manual states the different ranges of each mode, but does not discuss why you would want to use anything but high.

They are turned off in options, but they are still rendering. The mirrors are not clickable, so I can't turn them off in game either.

Since the latest patch, I am unable to turn my mirrors off. Is anyone else experiencing this?

I agree. Mistakes happen, but it highlights the need for a system. The fact that deployments are happening right from a dev's laptop is a big red flag. Perhaps RAZBAM should investigate using a continuous integration platform with automated testing to ensure only good code is released in the future. Obviously, I have no idea how DCS is architected, but maybe ED needs to be the one spearheading this effort and providing a means of integration testing for 3rd party modules as well to ensure compatibility with new versions of the engine. That said, I think the module is amazing and my favorite so far. It's just makes me sad when progress goes the wrong direction and it takes a long time to see a fix (even if we are just waiting on ED to release it).

I believe it's relative to your flight path indicator, not the horizon.

Is there a switch/light/status indicator telling you if the magics are currently slaved to the radar?

Since the most recent update, I can no longer hear the magics as they are seeking. I do hear a loud tone when they lock, which k can adjust with the MISS volume knob. The knob doesn't seem to have any effect on the seek tone. Am I missing something?

Is there any feedback as to the state of the magic slave? I'm never sure if it is enabled.

Is there some documentation on what this is and why everyone is so hyped about it? :D

Whoops. Should be fixed now

Excellent. Thanks for all of the suggestions

When aligning the INS, how do you get the coordinates to enter for your current position? I tried looking at myself in the F10 view, but I only see my latitude.

I'm not sure if this is an issue with the module, or with the simulation itself, but I've noticed that sunlight washing out gauges is exaggerated. While it makes sense in the middle of the day to have sunlight fully overpower the gauges backlight, the same effect shouldn't happen at night. I recorded a video of me flying in a circle at sundown. You can see that when the sun is angled to shine light onto the gauges, the gauges are totally washed out. [ame] [/ame]

When I use rockets and select TAS, I don't get a pipper. RS works, though its not very accurate. Am I missing something, or is TAS not available for rockets? Thanks

Thanks that was indeed the issue. The instruments literally were frozen :D

Perhaps RAZBAM should look into testing their code. It seems like some feature gets broken with every release. Sent from my iPhone using Tapatalk

How do you select a weapon for jettisoning after it has been emptied (after you have already changed to another weapon)? Thanks

I noticed this bug after the most recent update (yesterday's patch). While flying, the speed and altitude will randomly stop updating and retain whatever value they had when it froze. This affects both the HUD and the analog instruments. After some random time, they will unfreeze and begin showing the correct value again. It seems to happen more often at higher altitudes, though in my video it happens before takeoff as well. Also as a bonus, the sound cuts out whenever I look perpendicular to the plane, or down at the control stick. I showed the startup in case the order of operations has anything to do with it.