BigBorner

Yeah. There is also sometimes this bug where Amy is suddenly going through allll the available voice warnings like it’s a test routine. Had that while taxiing and in flight. But it’s doing it once and then everything is back to normal. Maybe she becomes self aware and wants some conversation.

Hm, I was a bit more far away then you initially but went pretty close. But i used a better angle (~45 degrees) to the target. You can see it a bit in my Screenshots. There is another bug report somewhere that shows differences between maps, on some maps Airfields are mostly invisible on radar. Maybe it has something to do with that. Ima post the link if I find it again. Edit: I really don’t know anymore how to design my test to catch all those variables. And now I remembered that I recently had issues with the eagle and scuds, too. But on a MP server. I knew exactly where the scuds where through Terrain correlation between F10 map and Radar map but I could not see them. But I think we can all agree that something is broken and it’s not just user error @JG54_NF2 You used PG? Which airfield is that? Ima recreate your test there and see what happens.

Looking at this here together with your other bug report, I guess that those weapons with videofeed are code wise a sort of extension of the plane itself and thus it might be hard or impossible to change. But yeah, some official words about this would be nice.

There should not be any warning when you’re going above 20k feet. Can you make a track and post it in the bug section?

That might explain it. I was using Autostart. I thought once its done im good to go.

Nooo. They’re being flown up to their office by lesser Jets like F-16

I don’t know. Looking that it’s even possible to change between Blackhot and whitehot with the appropriate HOTAS binds while not in IR - maybe something is a little bit wrong with the pod, too.

This was on Persian gulf if I remember correct. Yeah maybe. But - that be positive and negative testing on several maps, with at least 2 airframes on… idk how many ground units exist. 100 maybe? so, 3 maps x 2 modules x 90 units = 540 test cases minimum. I think I did plenty enough work I would usually get paid for for free to show that there is something afoot that needs work by professionals. Those are aware now.

I have retested a little bit. (Current Open Beta, Singleplayer, Multicore) I get no returns from: BTR80 BTR82A Scud Ive attached tracks for all of those and one as comparison with Fuchs as targets. They do give returns. I did the same Tests using the Strike Eagle, and got Returns from all of those Units. Scud as example: I only get a return from the Tank i placed on the right side as control thats how it looks in the eagle (Yeah, i like staring at pixels) Thats how radar returns can look like if they are there on the jeff. Here the Fuchs. BTR82A_JF_NoReturn.trk BTR80_JF_NoReturn.trk Fuchs_JF_Return.trk Scud_JF_NoReturn.trk

There is something wrong with the voice warnings. I don’t know how many times I experienced it suddenly running wild during taxi, or in flight, and go through every possible voice warning. No, I don’t have a double bind to any test buttons and while I have both hands on stick and throttle I can’t accidentally press anything in the cockpit. Unfortunately I play MP only, so tracks are unusable for Bug reports and as it is so random (as in it happens while not pressing or doing anything else then flying straight) it don’t know how to reproduce.

But i corrected myself in a later reply here. You can do that only with 2 per program.

CBU is a dumb weapon. The plane only knows it’s there, but not what it is. That’s why you see a “1” on the station it’s mounted to. You need to go to the armament page and tell the plane what is strapped to it.

Yes, we noticed that. Every time we use the targeting pod or try to bomb runways with runway bombs. Or if SPI is runnning wild because AG radar decides to set one on its own and you need to unlock it first to do anything with SPI. Sometimes even with radar switched off. With all due respect, the only important visit needed here is you as DEKA representative. It’s your responsibility to put the bug reports on the right tracks. We don’t have access to EDs JIRA, and we are testing a product from DEKA. So Deka gets the report. Hope you get well soon and don’t have any hassles with it afterwards. All the best!

Hm. Now that you say it, that remembers me of a sortie I had last week. Was flying in (somewhat loose) formation with a Viper. Viper was crying because were locked (by I think SA-2) and got launch warning. While my RWR was - clean. Some distant nails maybe. Shrugged it off as „well, maybe not close enough together“.

Which did not exist in the initial mission setup, so I would assume also used INS only and probably introduced also its own drift. Idk if this is modelled for the bombs though

Whilst i do agree, it is honestly still Dekas Job to communicate that issues to ED. Where is the issue to just move, for example, the bug report for the runway bombs to the ED weapons but section and create some visibility and pressure if they don’t get any help from ED side as stated. All of us here are beta testers that even paid to be that - only to discover bugs that should have been catched on even the simplest regression testing flow which obviously did not happen. Neither on ED nor on Deka side. You can’t explain everything with hardware combination on user side. I would get shouted at by my project or integration manager if I’d work that way. And they would be right.

The pod still has the bug that daylight camera is the same basically as IR. You can even switch between BHOT and WHOT when not in IR mode. Is there work planned on the pod or will it stay like that? You need a new track showcasing the error?

Yeah, that’s for me the biggest headache so far and attributed most misses to it. Can’t say anything on the technical limitations on coordinate precision from a radar designation in dcs - but I was hoping I was the only error factor there

So were not really supposed to use it for that? Or what’s the consequence of that information?

By having the WSO create the Target Designation and Pilot uploading them to the weapons via SmartPacs?

I’m just repeating what Razbams SME is saying about it. I mean, 65ft isn’t a big difference (he also says that MSL will be used as reference in SP) - maybe it only becomes really relevant in case differences are bigger.

Hm. Notso repeats over and over again that it is very important that you have the radar slaved to a target point in the vicinity of the to-be-mapped area to get correct terrain elevation for mapping and targeting. That’s something that is not happening in this video. Maybe add this to the workflow if someone intends to follow that video. And WSO can zoom in even more then the pilot by HA Trigger + TDC depress.

Hm. But all I had loaded in terms of AG weaponry were this 2 JDAMS on the CFTs. Wanted to test a double magic on a comms bunker. Tried again immediately after, when I transmitted coordinates to the right CFT first, the left was working fine too.

This also happens if they are mounted to the CFTs. Had a penetrator JDAM disappear from left CFT today after transmitting coordinates

That’s how it is intended to. Turned out, pod does not have AA functionality IRL, so they removed it a few updates ago.