Koriel

I guess the answer would be "When it's ready". Jabber just did a video stating that the rear pit was't finished yet, at least some texture work was missing, and HB asked not to show the RIO's workplace yet.

^ Wow.... Nope haven't flown the plane, never even a fighter, I do have 15K+ hours though, and asking a non confrontational question...

@Jabbers_ I can't get over the fact that the shaking effect seems to be a bit overdone. I realize that a simulation can't convey real physical effects properly, and that sometimes graphical/sound effects are being used to try to capture that feeling. When you flew the F-14 did it feel "real"? On another note, yes the mirrors look very cool. And I realize that when you return to the boat you have to make sure your hair still looks good. Some (not as as vain pilots) might even use the mirrors for looking behind the jet iso for personal admiration. Can they be adjusted for those who wish to use them to look behind?

This, From what I gather they needed a more robust system to get all the multicrew working better then with the code ED is currently using. So HB developed their own, I would surmise that it's better. SO why wouldn't ED use that code as well? I can't find the source anymore.. I\ll look

The whole point was making is that HB had to overcome some deficiencies in the current ED netcode with regards to multi-crewed aircraft. If this code works, could ED implement said code as well on their own multicrewed planes? That's all..

That last part you've brought on yourselves. The announcement was awesome. (I bought it as soon as I realized it was available on your website.) That and the subsequent video's and interviews created a huge hype. Usually being able to pre-order a module means it's basically around the corner. And then having to announce that it could take up to an additional 3 months before we can have the module in our hands is a bit.. disappointing? You basically give yourselves over 5 months after opening up the pre-order to deliver the module I don't question your decision to "delay" the module. You haven't delayed it after all, you're still aiming for the target zone, you just have missed the bullseye.. ;-) Everyone has their weak spots and I think yours is that you love to tease and hype a wee bit too much and it (in my mind anyways) bites you in the rear-end. I am too old to get too upset about this. I would like to ask you to dim the teasing and such a bit for your next aircraft. (A-6 please please ??)

I've got a 34 inch monitor. I would appreciate it of I could have the Jester interface resized. I don't need it spread over my whole monitor.

So how would you do that in a multiplayer server? On another note, never really cared for the C-101, but with this update I might even take it out of the hanger on occasion. Good Job!

It's still a fun plane despite Eagles's lack of commitment in fixing some glaring bugs

Well.. ED has apparently some issues with multi-crew code with regards to side by side/Sharing the same cockpit. HB has written their own net code because they needed better code than what Eagle could provide. And I'm not just talking net code.

There are a few items that could very well be fixed quickly like the MP smoke, the engine start to name just a few. Even a statement or an acknowledgement of the items to be fixed would be welcome. The F/A-18 gets fixes or additions every 2 weeks.. Why not spend just a some time to fix the Yak?

That's all good and well, but looking at all the fixes every two weeks for the Hornet... The fixes required for the Yak won't take that much time, and then they can put a "released" stamp on this one and move on. Only 3 items on off the top of my head: Fix start-up. Visible damage modelling Multi-crew sync issues with smoke

I know that HB has coded quite a few original things for their own products. The ground radar, own network code for the Tomcat Pilot/Rio and of course Jester. HB is depended upon Eagle for the DCS code, development API's and such. I wonder if there is an exchange of code between Eagle and HB possible? I have heard that Eagle has issues with the multi crew code and I wonder if they could use the HB code. Just wondering, not being hampered by any knowledge. .;-)

The introduction of the Yak was a bit casual, a hotfix was released quite quickly. And after that it's been quiet. Has development of the Yak grounded to a halt? One of the most glaring shortcomings of the Yak is still the visible damage model. Seeing an intact model with some Spitfire parts strewn around it is a bit offsetting. Flying with parts missing, but still seeing an intact plane is immersion killing. So, ED.. when are you going to fix the Yak? I realize that you have a ton of work on your plate, but releasing an unfinished product and just continuing work on other modules is not the way to go.

Thanks for the update. I do commend you for your stand wrt the status upon release being more than other early access releases. Personally I favor a different stand, but it is what it is. Good luck!

I understand your frustration @Cobra847, and I know you understand ours. I think this whole discussion started with "The Announcement". HB created the hype. And now you reap what you have prematurely sown. I'll be looking for your dev update. And I hope for everyone involved that we have a good release.

Any word yet? I even tried it with pulling the landing gear cb, but the gear just won't come down.

Excellent !! Very easy to manually install and configure. Playing around with the excellent MOD I'd like to raise 2 "issues" Disclaimer, I know that it's most likely only Eagle-D that can do anything about it, but here goes: - The Track-ir enabled in outside view setting.. is there any way we can do this with the mouse? - Option to change viewpoints on the fly.. That would really make this mod awesome!

I think that they just have to make the decision to put it out there before xmas. We know the -14 won't be finished for a long time to come, but the module is very playable at the moment as we've seen in the livestream. To me it looked to be already way above some other initial releases by other developers. So take the decision and go for the early release! One thing that worries me is that we haven't really seen any carrier landings or the RIO station at the moment. That and the lack of instructional video's lead me to believe that a release is still a ways off.

@JagHond, If you go to the DCS website, log in, and check out the modules list. Under the price and pre-purchase button of the F-14 it gives me the message "You already have a license for this product" Could you check that one first please?

@Chaser, Been reading it a bit more. You failed to state exactly what the issue is. You only posted an error log. What exactly happens when you launch DCS? When did the issue start? After an update? What actions have YOU undertaken to solve the issue? Have you tried a repair? Going back to a previous version. You might want to try the DCS Updater https://forums.eagle.ru/showthread.php?t=160053 With this app you can easily update/repair/up or downgrade your DCS install.

Actually, multicrew still has issues. While it's a LOT better then when introduced with the L-39, there are still a lot of sync issues at times. I have flown rearseat in the Yak for example with a completely destroyed engine up front... ( Or was it the other way around? Can't remember). So the code can be improved to verify status between the multicrew partners. Same for the L-39. No wonder that Heatblur has developed their own solution.

I'll go for the first answer since I still have all 12 Mk-82's with me when I try the drop. Waiting for a fix and I'll use CCIP in the meantime.

I'll breathe some life into this thread as I believe it starts with my problem. In flight, using Chuck's latest description to drop Mk-82's everything works as advertised apart from the fact that as soon as I press the pickle button the 4 dashed lines appear again. Checked everything, Master arm on, 82's selected, a/g mode, it's all there, the line, the countdown, the drop line.. Any suggestion?

First of all, ED's customer service is not useless. I've had to use them for an issue or two in the past and they've always helped me. Even with an out of the box transfer of a license they've been going well beyond what a normal customer service would do. Second, looking at your log file I see driver error, mounting errors. etc. You might want to look into either deleting your shaders so they can be rebuild on next launch of DCS. You can find info on that on the forum here. Perhaps even deleting the complete dcs folder in saved games. After a complete reinstall of windows I just linked the dcs.exe from my game partition and it recreated the /saved games/dcs folder again. Try using the forum for your issues, most likely the answer is there. Always make a backup of stuff before doing anything rash though.