Talonx1

+1 This patch took broken things that needed rolled back and instead just broke more things. But HEY ppl can eject and walk around on carrier decks now. Too bad planes dont work on them any more.

Literally the lamest and over used excuse. Stable is just as broken, its still on bigs from 5 months ago and everyone knows full well including ED that the majority of users play on OB including MP servers and that the title "beta" is nothing more than window dressing on what is the current proper build. Not to mention content that can be paid for but is only available on OB. Try again. No excuse for completely breaking content with a patch thats supposed to improve the title not destroy it. And to my knowledge its super carrier issues that were "known" and going to take a while to fix. That doesnt mean they fully intended to break current carriers and it was going to be a while to fix them. They worked fine 2 days ago.

A. So knowingly breaking carriers w a patch is an ok thing? B. That doesnt cover all of the current carrier issues.

How is there no mention amywhere on ED forums about carriers being broken on MP servers after this patch? Hoggit servers are borked and reportedly wouldnt load at all and servers that do load with carriers have aircraft bouncing all over the deck. Game breaking bug and everyone is awefully quiet about it on official forums while everyone talks about nothing but fps issues which dont even themselves make sense. With some claiming no improvement, some claiming small improvement and some even saying its worse. Just throwing code into the release and seeing what happens?

If thats so then its so. Personally I've been using the supplied software since my first thrustmaster mk1 and have never had an issue I wasnt able to resolve through a little effort. Most recently was in fact with target software when I first got it. Resolved it by disabling MS store which for some useleas reason effects joystick recognition.

All is explained in the other thread. You may think you have it programmed when youre on the ground but you do not. Not properly anyway. As I said initially its very easy to accomplish in target. I dont understand why so many people are adverse to using proper hotas programming. Spend potentially hundreds on sticks then waste their potential. See it all the time on Elite dangerous forums, ppl who refuse to actually program their hotas and then claim they dont have enough buttons. :joystick::doh:

Just saw theres another thread where a limited number of people that claim to have that switch sending 3 signals, one for each position, supposedly without any use of mods or programming. I find that suspicious however as in windows joystick control panel the switch only registers a signal when moved up or down. Otherwise it would send a hold signal for some dx button input while in the middle position. Unless theres some sort of manufacturing variation in some of the throttles it simply shouldnt be happening. My guess is that people have at some point installed something that makes it function this way whether they remember doing so or not.

Which switch? For the lower right corner 3 way toggle the switch only natively sends input in the up and down position. Only way to get 3 functions is to do one of the above. Same goes for all of the hogs 3 ways except perhaps the flaps switch. Not sure off my head but it may send 3 signals natively.

Not sure what exactly needs "fixed." Map with TM software and its plenty easy to map to the 3 way switch.

For now he can be controlled via macro in your hotas software or with voice attack or similar as the commands are "mostly" consistant in their location on the wheel. Glad to hear simpler keybinds are in the works though.

Any time I havent had a launch, i just drop back to idle and wait a sec and then back to full throttle and it typically launches. That said, I've noticed that as long as I make sure the engines are at full rpm before I hit launch I never have a fail. Not burner, just full mil. Every fail to launch I have is when I dont wait for the engine to spool up completely before hitting launch. Maybe something to do with the way the system works with the hirnet interfering with the tomcat launch system.

As of todays patch I'm having similar issues with the AP. I used to set hdg and alt switches to the up position and turn on the ap and it would hold my pitch and roll till I hit the NW switch and it would level off at my selected altitude. Then I could maneuver the aircraft with delayed input till the required stick pressure was met and the a/p light would come back on but it would hold whatever pitch and roll I lined up on when I released stick pressure. Now whenever I set the ap it seems to want to go back to that pitch no matter what I do and will max out my trim trying to force me back to where I was set as soon as I activated the ap no matter how much pressure I apply. I end up having to disable the ap and recenter the trim to regain control of the aircraft. I also always kept my speedbrake out in the pattern once I've entered the break as prescribed but now it's just not possible. With the brake out it's requiring constant full throttle just to keep from dropping like a rock an the trim settings required to maintain on speed aoa are completely different. Something with the FM update today has really made things wacky. That said with the speed brake in it felt super smooth and easy to bring in. :helpsmilie: This thread has been marked [no bug] but either something was way wrong before or its way wrong now. Seems unlikely that a corrupt install would be causing the same issue for multiple users so something else must be triggering it if it isnt happening for everyone.

Do fov changes have any effect in vr? Just curious.

F18 is much easier to fly thanks to fbw and hud however is more technically complex with all the mfd's and broader range of weapons. Personally I find the f14 more fun to fly. The flight model is just more fun to play with and imo the visuals and audio in the f14 are much better.

All I could hear in my head for that video was "you're teasin it man!" And "staay on taarget"

" Some are seeing significant improvement; others are seeing a reduction in VR performance. "

2 things. One, any chance we can get an option to disable the abbreviated jester command? For example, the menu defaults to a certain submenu depending on the situation ( aa, ag mode etc) and just pressing a number will send a command without even opening the menu. Using voice attack it just ends up sending commands to jester on accident and I half the time all I hear is "ok" or "roger" and dont even have any idea what he's done. Would much prefer to open the menu before he will respond. Second, since the ground track option has been added to the radar menu for jester the option for turning radar on and off moves between option 6 and 7. Again for ease of sending a macro through voice attack its easier to have it appear at the same location so it can be toggled with the same macro and if I actually want to create a voice command for ground track its location is going to move depending on radar state. Ok, one other thing... maybe have the order in which sources appear in the menu for radio tuning and tacan tuning ordered by type instead of range. (As i "think" its done now) so that a command of j - j - 5 - 5 - 4 - 1 for example would always end up selecting the closest carrier tacan as opposed to changing between carrier and tanker depending on the situation. If it already does this then never mind but I pretty sure off the top of my head it doesnt.

There's an improved readability cockpit mod on the user files section of the website. It helps a great deal with reading labels if you havent already found it.

Have also had no trouble trimming with stick input applied. Maybe check ap switch is off and that it isnt on with just alt and hdg hold switched off. If its on you cant trim properly. As for the fueling probe drag I noticed it right after it was introduced and while I've been able to fuel pretty well just ignoring it, I typically just apply a little rudder trim to get the slip indicator a little closer to center and have no problems at all. Just ran the included night mission where you take off at night, in a thunderstorm and you amd your wingman have to refuel at 2k feet before heading off on a long low alt engress for interception and it was great. :)

Have only had ai start with extended wings once, reloading fixed it. Have never had issues with cat launch other than a delay from time I salute till launch but havent even had that in a few weeks. If you have issues with hookup make sure front gear is compressed completely and that the aircraft is in the proper position.

I've read in some places they say to turn it off or it can cause stutters but I haven't had that problem. I always open oculus, open debug, set my settings then launch DCS from the debug tool and then leave it open. It's worked perfect every time.

I've noticed lots of weird melting/ghosting for a long time but had basically gotten used to it. Especially during loading screens it would geg all wacky. Recently though I stopped setting pixel density in game and now leave it at 1.0 in game and use the debug tool to set it to 1.3 amd disable asw. In the process I also started changing a setting for "adaptive gpu performace scale" to off. No idea why but it completely gets rid of all the ghosting melting for me in dcs even in the loading screens. I also always launch dcs via the "file/launch app" drop down in the debug tool as it seems the most consistant way to ensure my oculus options apply properly 100% of the time.

Awesome, will do thanks.

Anyone know if it might be possible to replace the painted on canopy reflections in the hornet with the glare/reflection shader from the tomcats cockpit? No offence to the hornet devs but that f14 glass just looks so much better that its painful to switch into the hornet after flying the cat for a while.

Would love a full size bomber like the b1. Even a b52 would be pretty cool. Tall about multi crew options :)