normanleto

Hey guys. After about year of pause I decided to get back to F-15E. Today during GBU training I discovered this funny thing: this little pipper f..ker sometimes blinks without a reason during a bomb run. Could not find any online info about that. All parameters of LGB drop are correct. After drop - it starts to blink. 20000 feet agl, 420 knots, no negative G load, PACS config correct, ARMT weapon selected (like GBU12B) and sometimes before, sometimes after drop it starts to blink. Not lasing related. Not timeImpct related. It stops flashing only after pickling another bomb. The pipper isn't outside a HUD frame (in other jets it causes the blinking) - even if it's centered on ASL, this behavior still occur. I am not sure if it indicates anything, but the randomness of the thing itches me Best, nl

so you just give some minimal dlc flaperons input to compensate for a-throttle overreaction and it hooks the line correctly? Like a one small input second before trap?

Do you know any details about current Shrikes bugs? Shrike is older gen missile than Maverick, even range-wise agm-45 is way worse from my experience. Too close for comfort.

Hello, guys. After couple of months flying of phantom, do you guys find Shrikes useful at all? I cant find any reason to risk using 4 shrikes instead 6 very accurate mavericks. Same goes with bullupps. I played with them to learn but using them in MP cold war servers is rather asking for death in most situations. Also a supply or limited availability is rarely enabled in MP servers, so Mavs are usually there in unlimited stock. Am I alone in this observation?

I am worried about so many bugs in this campaign it is hard to count. Most of missions start with AI exploding on contact with obstacles or trucks during initial taxi. Some trigger zones turn on in such an obviously wrong moments. I will not list them exactly, bc there are other posts about that particular bugs already there. What worries me is the general low quality of mission testing, especially after every map update. Syria got updated recently and all Syrian campaigns got really wonky (I also have the same problems in AH-64 apache and it's new, paid, syrian campaign). Is it really so hard to predict that adding too many changes to a map at once will break most of missions? Is there a way to cooperate between devs of particular maps and campaigns before launch of the update? I feel only HB and perhaps Reflected are the makers that can handle things at a really professional level, and their QC is at the best level possible in this persistent early access environment. I know we live in a constant early beta world in DCS but wasting hours on troubleshooting kills any immersion from Phantom (or apache) - even with as great product as only HB can deliver.

Thanks for such a great reply. I will dig in. I wonder if campaigns like "MAD" are going to support it. Would be good to know your wingman position without radar in the MAD campaign.

Guys, how is datalink usable in SP mission? I just set radios and TSD threat circles, but datalink? I was sure it is a MP feature only in apache?

Thanks for your input. It seems that after last update things got better with "back to TV mode" problem and I dont struggle when switching different weapons and the going back to mavericks or walleyes. I would consider it as a solved with update. I also tested your file, but after yesterdays update, so I am not sure what exactly solved the problem.

Thanks - I dont have problems using tv weapons or to lock them. Please read my initial post. I have problem getting back to a working tv mode after using any different dumb weapons beforehand during mission. So your quick test and tutorial links do not apply here, it has nothing to do with contrast lock and visibility for Walleyes or Mavs...

The timer is not the issue. I tried to get back to tv weapons after 15 minutes and there is still no way. I'll record the track tomorrow. You can always try to reproduce it before on your side. Perhaps it is something with afghanistan map and the spawning in editor. What is interesting, the plane spawns itself with weapon selector already on TVs with such armament config.

I did your suggestions before, I also recorded a short video of how it looks from my side. Even tried to do some WSO seat tests, but nothing could bring back the walleyes to life. Here is the video of a problem:

Guys... since two hours I struggle in mission editor trying to narrow down the following problem: I can't get back to Mavs or Walleyes video feed (or even their amber ARM state) after dropping dumb bombs or using rockets with other selector mode. When switching the selector back to TV mode, mavs or walleyes are unreachable no matter what. I am sure I know how to use TVs, because they work as advertised at the start of the mission if no other weapons are selected before them. Short video of the problem: It even happens after an unexpected AA fight during AG mission. Seems like some selection logic for TV weapons gets broken if you select/do something specific and then try to get back to your TV weapons attack config ofc I tried to reinitialize TV feed with jester menu, tried to turn the weapon and mode selectors around, cool off several mins to allow mavs or walleyes restore - but no joy. Is this a bug or feature?

Like every spawn point is an icon and the map can't handle displaying of so many jets' icons - both on tarmac and in air spawns. Good idea, but very odd execution. I wonder if they tested it on public servers with hundreds of slots.

Since new update I have a problem with freezes on the briefing and new spawn system window menu. It becomes unusable, very slow reaction, game hangs for 30 seconds when scrolling for plane type selection and briefing button. I also reported a separate topic with a mouse movement lag - lot of users have this as well. Something is very wrong with the new UI, I am all for the news but some hotfix is badly needed, guys.

Same here. Funny thing I've changed my steel series mouse for my simpler logitech one my wife is using. The problem is gone. However, in my steelseries Rival mouse, even lowering the polling rate to 125 did not solve the problem. So I am using my wife's mouse rn, waiting for solution. Best, nl

I confirm.

Exactly. We have to mod the CIU_Messages.lua to cut the unbearable SAS sound. Warning: after any new update, the CIU file is overwritten with a fresh one, with bad settings again. BIGNEWY, any news on this? We are patient but it is a simple issue to fix, even with a scotch tape for now...

Same here. Module is non-playable since yesterday, the first release was more complete than the current one. We just have to go back to our previous betas, F-16 in my case

Perhaps it should go to BIGNEWY to raise their knowledge? It brings a bad vibes for apache module, even if its beta. We will just all stop flying due to one idiotic warning. Ive asked before - modders, can we replace a sound file, for example?

I fly rather okay, but since about a week I have annoying sound of SAS SATURATION message too often to stand the game. It appears very often except perhaps straight flying. Even small adjustment of throttle causes it. Tried to turn off various channels in A/C utils page, but to no avail. I see a green bar of throttle input slowly creeping up or down the limits (on the controls preview). I have deadzones set to about 3 in each axis. Stick is saitek X56. Anyone else has this problem? It is very annoying during the hover attempts or during the combat. No way to turn the sound off. Perhaps there is a way to change a sound file to avoid hearing it every several seconds?

I have several hours already in Apache module, but I never got back to base with any kind of failure (except visuals) caused by an enemy. No engine failure. ZSU or tanks MG's seem to always tear off the tail and apache falls from the sky not killing any member, which is fine. You can stop the engines and contemplate the silence of the oranges plantation in Syria. Have you guys ever got some random failures on the way back?

Thanks, I was sure that some ghost update today inflicted a sudden drop in apache handling. Your A/C option put things back. Except COLL, please do not turn the last channel on (NOE), it makes flying somehow nasty.

As in the topic. Is there any page with clearly indicated possible damages? I did some testing myself and visual damage is already done pretty well, but how about systems damage? I had the same question regarding F-16 damage model, but on the other forum. Best,

Hey, did you find someone already?

Is there any page or instruction covering the current damage model of the f-16? I am not sure if it's done properly or just you-get-hit-you-go-boom at the early access stage? Best,