M4ND4L0R3

Hahaha, Its fine. A lot of people shirk away from a presentation defining key stressed words and points, its hard to read for some people and easier to just stop reading. So i understand. English is not everyones native language, hell, even some native speakers struggle. All good.

Well. To add my 2c, which I am aware 99% people are not going to care. For the record : - Im done waiting for the F-15E, when it comes out, it comes out. The fact this post started in 2012 is beyond ridiculous hahahah. - As ironsights mentioned, I would also prefer a heavily tested and functioning module, rather than half assed or " weathered cockpit " ( shade at HB ) version of the aircraft ( I play in VR and literrally bending my neck down to read the buttons is still " A thing " ). HOWEVER: - The F-15E was heavily, HEAVILY featured in the " DCS 2022 " video.. last christmas pretty much. Infact if you count the scenes in the video it is almost 50% of the entire running time of the -> DCS <- 2022 video. Thats a lot of time to be " promoting " a single aircraft under the ED engine in the -> DCS <-video. - Now, its 3/12/2022, and we have had a few MFD videos on YT, and thats about it. Still no release or pre-release marketing grab. - Why did ED so heavily promote the F-15E in -> THIS <- years video, if it is not due or planned for release? ( christmas maybe? hurry up and wait ). If it was a RAZBAM release video, then fine who cares, its on RAZBAM for not hitting the project deadline for release. MY POINT IS: - It comes out when it comes out, but; - ED should NOT be promoting 3rd party products -> so heavily <-until there is a set release date ( even if ED know about it 6 months ahead of the customer, as it should be ), as long as its confirmed and dusted 100% going to be released on X date, we shouldnt see it promoted. This is called false advertising. - ED should absolutely push a release time date WITH the ED licence to 3rd party developers. A super dummed down, basic conversation would be... " We have X jet! ", " ok, whats a realistic time frame? " " Oh, 2-3 years? " " Ok, so make sure you release it by 3 years otherwise we will revoke your 3rd party licence to our product and reliquish any existing models and data under our engine as per our licence agreement ", " Ok great thanks! " - Its not hard. This is super, SUPER basic project management and licence management. If RAZBAM dont have the coders/designers/programers/engineers/what ever what ever, they should approach ED for assistance and then ED can dock RAZBAM for hours/time spent using ED staff to complete a project from proceedings of sale until ROI has been achieved. - Doing this also properly -> washes ED's hands <- of any project mis-management by RAZBAM, ensures that potentially ED itself would pick up the pieces of any failed 3rd party developers, and holds faith to ED's current customers to show that they are making an effort to ensure promises by 3rd party developers are made and -> delivered <- in a timely manner that doesnt spawn endless post's such as this thread. Anyway. Thats my 2c. What RAZBAM has released for us on YT looks great, but again I am not holding my breath. When/if it comes on pre-sale, I will get it for sure. Until then, Meh.

I think whilst the F/A-18 can do everything, having TWO two seater jets in DCS is just going to be amazing. If I wanna fly ATA I can hop in the Tomcat with my friend. If we wanna play multi-role we can hop in the F-15E. Just a dynamic we need more of in DCS.

Fair enough, its obviously something they havent really invested a lot of time in, at least as far as the #1 option of VR hands goes. I am going to try the rest of the options and see if I can find a method that works best, but still being unable to accurately grab both throttles consistantly is an amazing issue, let alone trying to use all of the stick options with one oculus controller, lol. meh, I guess.

Hi guys, Just testing for a buddy ( although I am also on VR and wondering myself ) Found some issues when using the " virtual hands " in DCS, for example trying to grab both throttles in the F-18 is super tedious at best, it doesnt really feel " smooth " when trying to use your left hand to interact with the rest of the cockpit, and then trying to find the throttle again. Toggle switches are also super painfull, you give the flaps switch a hit for example, and then without even moving your hand you get multiple movements from the toggle switch ( using the trigger to activate the finger point and moving it down/up seems to cause unusual reactions ) Does anyone fly with the 1st VR hand settings? or do you use #2,3,4 etc, or #6 where you set it up yourself somehow? I also play VTOL VR and its obvious to admit that its setup purely for VR, but I thought maybe DCS VR would have some smoother interactions than what I am experiencing. Typically I play just with the headset and the HOTAS/mouse, but my buddy was just wondering if he could get away with buying some rudder pedals and then use his Quest 2 setup to play. Thanks in advance for any advice, really appreciate it.

New DCS trailer " 2022 and beyond " HEAVILY features the F-15E in several, SEVERAL shots. When are we going to see it.... its been so long.... Watch for yourselves below:

Great! Thank you for the insight, you have made my decision much easier.

I definitely understand the thought process, this is basically what I did with the logitech profiler, except I still just had to swap the profile quickly in the profiler, as some aircraft are different obviously. It unfortunately doesnt answer my question about the mode select though. Does anyone know if the mode-select will -> hold the signal <-, or will it time out like the logitech hotas does.

First thanks for your reply, really appreciate it. Ok great, I did watch some video's on the software and outside of any of the complaints I saw I think the software is great for what it can do. Rather than just outline what a " bad way " is, would you perhaps be able to share some suggestions on the best way to get the mode select switch to work as a " mode select " with DCS? Before i used the logitech software to individually program each mode function and assign a hotkey in DCS to each function, but then all of a sudden with the F14 module from heatblur, this didnt work anymore. What are your suggestions to make the mode button actually give me more than one base map? Thanks for clarifying, I probably should have been more clear myself. I meant putting a throttle and a control panel together, not two control panels together, my mistake. But its good to know that wouldnt work anyway. So If I link the throttle and control panel #1 together as an example, the mode selector switch will then apply to the entire assembly? even if making the mode selector act as a held down button is a bad idea? Ive been doing a lot of research lately, really excited for this product but I still kind of need a direct answer to my questions, no one has really asked these kind of questions before on the forum. ( that I have found... I may of course missed some ) Thanks again for your reply.

I am also looking at VKB, but since VIRPIL seems to be the pricier option, I thought I would start here. Im coming from running an Logitech X56 with pedals. Had a few issues before ( thanks Iron mike for the help ), and it runs fine now, but I have finally swapped over to VR ( RIFT S ). With this in mind, im thinking about also upgrading my setup to something that " looks " to have a much easier " touch recognition " for when im feeling around with the headset on. Some question's: - Ive noticed the T-50CM3 throttle also has " mode select " buttons. Can anyone confirm that these will hold the " switch " signal with DCS? That was the problem with the X56. You would change the mode select button, but after 20-30 seconds the throttle would stop transmitting the mode select and you would default back to whatever your base map was. Otherwise, I guess I would use this like I do now for my ECM dial in the hornet, haha. - Virpil of course say that you can either use the control panels independently, or attach an auxilery cord that then merges the panel's together to become one big controller block. Does it work as they say it does, WITH DCS? - If the above two conditions work, can anyone verify that attaching a control panel and using the T-50CM3 mode select switches all work as they should? - One of the reasons I am also looking at VKB is that they have some very good stick ranges for those of us that like to really immerse with the plane ( F18/14 sticks, etc ), But I do actually float around from plane to plane quite frequently. I also dabble in Squadrons/x-wing alliance quite frequently, so having a set stick is not the worst, but I feel that the ALPHA-R might be able to fit more moulds than most. Thoughts? Again, I am also looking at VKB, but its not a question of money as it is functionality. VKB dont seem to have a good throttle on hand, unlike VIRPIL who have a very good example in the T-50CM3 ( strictly looking at what it offers ). But the VKB sticks are very tempting. I can obviously run two different brands, but I do prefer to just run a single brand rather than have a mess of brands. I havent found a suitable replacement for the logitech rudder pedals, but I dont think I will replace them as rudder pedals dont really have that many functions. Also would like to hear of any pressing bugs/incompatabilities from current owners. Thanks for taking the time to read/and or reply.

Wow... Now i want to bump this. I can land the hornet on the deck without issues following the AOA indicator, whether or not I hit the 1st line or the 4th line is another story, but in general i feel the AOA is correct. This definitely explains why I have been having so much headache trying to land the tomcat on the deck purely " following the ball ", I literrally follow the ball the whole way in and meet the back of the ship or manage to push enough power in the last 300m to " clip " the first set of lines if im lucky. How much higher should I be, by the way? just run it in faster or literrally run it in higher than normal.

Im gonna go completely off the pace and say that even though i have loved the idea of fighter jets since i was 3, and played every AC game there is ( cmon I was young etc ), I just have never enjoyed the asthetics of the aircraft. For me it just doesnt have the " presence " of the hornet, tomcat, or even the flanker. Its always been kind of like a " meh, ok, because i have to I will use it " plane for me.

Welcome, glad to see someone else also enjoys the A/G side of the hornet. On my normal PVE server, I usually just load up AGM-154's depending on target type ( cluster for light units/infantry, armoured for tanks/sams etc ). It takes a bit of time to set them up ( helps if you have a buddy calling the targets from the map for you, otherwise I just take photos on my phone and do it that way ), but for me personally there is nothing more fun than racking 8 different targets from maximum height/range and then already being on my landing approach before they've even hit the ground. Otherwise rockets/bombs with CCIP work great against moving targets. Im still learning TOO mode with the JSOW's, so im not too great with the FLIR or onboard camera. ( be great to have someone help teach me haha ) Enjoy.

Sorry, Do you mean you cant move the TDC cursor on the DDI? Did you: - Set aircraft to a/g mode - Set radar sensor to right hand DDI? If you didnt set the radar sensor to the correct DDI page then no, it wont move as your TDC priority is set elsewhere.

Right? Like im all for learning the backseat, I have another mate who wants to buy the module so im sure I will be riding shotgun while he gets the ropes, but actually knowing how to implement Jester would be great without deep diving on the forums. I tried again the other night using jester on manual TWS and SST modes on the first mission. Again, ( Flight mode AA, Missile seeker cooling activated, ACM on, Master on, Radar TWS MAN, Radar range 100nm, ), I didnt get any sort of call outs for locks, soft or hard. I also was looking at the DDI/TID infront of me and COULD see the range bar, but there was no target indicator/velocity indicator on the HUD. But I was already within 20nm by the time this started working, I ended up using boresight mode to shoot down most of the bombers. still not working too great on BVR, mr jester ( at least in my experience )