CptTangerine

Hi I wanted to give Smerch hunt a go in VR (I haven't really revisited the A10 since I got VR) and I am having a few problems. The main problem is with inputting coordinates given during the mission. The first problem is remembering them - I used to write them down when I was playing with TrackIR but that's pretty much impossible with the Vive on my head, and the second problem is being able to see the keypad to type them in. Has anyone come up with a decent solution to this? Cheers! CptT

The problem with that is that it will only work in the cockpit (unless I have this all wrong). It's when the camera jumps to outside views that I have the deafening issue. Normally, it's not that much of an issue, it's just that I use RedKite's mission a lot, like *a lot* and it's an annoyance. I was hoping that there would be a quick setting to define the distance. Alternatively, is there a way of setting up the mission so that the order of objects is rearranged so that instead of shoving me face-first into a SU-25 it starts off with a GAZ truck, or something else quiet?

If I turn down World sound volume, will that not reduce the noise of external explosions from the cockpit and other sounds? All I really want is to change the default camera distance from aircraft (like when you press F2). It's a bit of an insult to injury, getting killed in-game and then having your eardrums destroyed. Likewise, where the game uses an external view as a sort of cut-scene, it's deafening. I'm almost worried about the damage to my headphones.

Hi I was wondering if there is any way to set the default distance you spawn from an aircraft when you die or when transitioning from the aircraft selection menu to the cockpit of the plane you have selected. I am currently using the excellent RedKite tutorial mission which is a veritable airborne activity-blanket for the Harrier. Unfortunately when selecting the scenario to play, as soon as you hit Fly there's a 2 - 3-second burst where your head is basically shoved into the air-intake of an SU-25. It's pretty deafening. I always keep my headset away from my ears during this transition, but I was wondering if there was a way of setting it so that the camera is much, much further away from the SU-25 so that I am just not deafened at all. I have tweaked the tutorial a lot to suit my own requirements and I would really love to tweak this as well. Any suggestions gratefully received. CptT

Yep. I reckon that was it. Thanks for the help!

That sounds reasonable, cheers! I will give it a go.

Hi This is more of a head-scratcher than a genuine problem. I know the best solution - follow the start-up procedure properly - but nevertheless, I'm curious as to why this happens. If I start up the Harrier and forget to flick the Engine Start switch and just keep on turning things on (MFDs, INS etc.) when I go to start the engine, it won't. I have the APU on, the APU generator, all the fuel flow switches, but flicking the engine start does nothing. At first, I thought that I had used too much voltage from the battery but that doesn't seem to be it as there is often plenty of voltage left when I am trying to start up. I have tried shutting down the things I started up but this still doesn't solve the problem. Does anyone have a way of recovering from this? Is this something that has been modelled from real life or is it just that the sim can't handle a departure from the prescribed start-up sequence? I'm really just curious as it would feel more realistic than abandoning the plane and getting a new one. Cheers! CptT

I played the Spit for the first time in ages today and only just noticed the reflection bug. I was really hoping that this was a recent bug. I only fired up this forum to report it. Seems it's a longstanding problem then.

I have got it working. Thanks for all your help! It seems that what works for me is locking up the target on the DMT TV then uncaging the Mav, putting the Mav as the SOI, then zooming and then, when I'm within 7Km pressing and holding the DMT action switch until I'm at about 6Km and releasing it. I'm not sure if it's because it's zoomed in but it doesn't unlock the target point and it does lock. I'm very relieved that this isn't a bug. Cheers! CptT

So, really, it's a case of pointing the Mav seeker head at the target with the TV, switching to IRMV mode, and then just waiting for it (hoping for it) to lock?

So, I should be holding the TDC action button down the whole time until I get the Mav IR screen up slaved to the daylight TV? Is this why there is a toggle option for the button?

Brilliant thanks! I'll give that a go when I get some gaming time.

As a matter of interest, the TV is coming up on the right hand MPCD and the Mav IR screen is coming up on the left. When I select the Maverick as the SOI the TV image doesn't go away. Is this normal?

Thanks for that. Do you think that the fact that I'm not zooming in on the display is causing the DMT to unlock when I press the the TDC action switch? I haven't got time to test it tonight.

Thanks. It will be annoying if it is a bug. I'm pressing the TDC down not the SSS (although I have tried both).

Hi I have been practising using the Mavericks with the DMT. I lock the target by putting the marker on the target and pressing the DMT action button (it isn't set to the toggle mode) and then slew the DMT until it is over the target. I then push the sensor select switch fore to select IRMV. The mav doesn't lock so I press the DMT action button again (as has been described in some of the video tutorials) to try to persuade it to lock. Instead of locking the DMT locks onto wherever I am pointing as a new target area and the mav's focus follows it. Am I missing something or has the setup changed recently? I am getting pretty close to the target and the mav isn't locking. I just get to a certain distance and the cross-hairs disappear rather than focusing in on the target. I have had this working in the recent past so I'm not sure why it isn't working now. I am doing a cold start on the Tarawa with Red Kite's tutorial scenario so it is possible that I am not switching on a system that I should be switching on at startup. Any suggestions gratefully received. Cheers! CptT

Yeah. I binned the Beta as soon as the Harrier module started to work well. All up and running now, cheers! CptT

Hi I checked BIOS and the legacy support is enabled. I did a pretty big upgrade to get my PC VR-ready - I changed from an AMD processor to an Intel one (with associated mobo), I also upgraded RAM, graphics card, and put in an SSD. Most of my USB ports are USB 2.0 and the one that I use for it now is USB 2.0. I have a MadCatz mouse (so, basically Saitek) and trying to get that and the joystick working at all at the same time was a very frustrating and lengthy process. In the end, the only way I could make it so that the joystick worked and the mouse didn't keep locking up at random after a few minutes use was to part install the X-52 drivers and part use the generic HID drivers. I tried, I think, every other combination at the time. I was just curious if there was some other element that I had missed. I have no intention of uninstalling the drivers and starting the whole tedious process again (the thought of that much stress makes me feel physically queasy) but I was hoping that someone might point out an issue that would explain the stick, the mouse, and the fact that my TPCast also seems to need to be plugged in on startup to work. I said, during the two days it took me to get the TPCast working, that if it required me to stand on one leg, blindfold, singing the national anthem backwards to make it work, that's what I would do. The actual process is somewhat less dramatic than that but it would be nice if there was a simple explanation that would make the whole thing run as I feel that it should. Cheers! CptT

Cool. Thanks for letting me know. It would have been nice if it had mentioned it, but I can wait for a day or two. CptT

Hi Is anyone else having problems with The Big Show campaign? I bought it the day it came out but it is not showing up in my module manager in game. I cannot see anywhere that this requires the beta version of 2.5.x. Cheers! CptT

Ah. Sorry, I'm using Win 7. Is this likely to be the same?

I don't really have room to leave it plugged in all the time, besides it messes with my VR controllers when I'm playing games that require them.

Hi I have an issue with my X-52 Pro stick that I suspect is indicative of other problems in the PC setup. The stick will only work if I plug it in from a shut-down PC. From this state, it works perfectly and I am very happy with it. If I try plugging it in with the PC running then it will essentially lock up the PC. It was the devil's own job trying to get the stick to work at all when I first upgraded my PC (it worked fine beforehand). Recently I had my TPCast unit replaced under warranty and that was a nightmare to get working (it worked straightaway before) and I have now found that the only way to get it working is to shut down the PC, turn the TPCast unit and router etc. on then fire up the PC. These solutions work, but it makes me wonder if there is an issue with my USB set-up (IRQ problems or similar). It seems that if the USB device is there when the PC starts then it takes them into account but has a panic if they are plugged in hot. Has anyone encountered a similar thing, or have any idea what might be causing this? If there is a deeper problem, solving may save me grief in the future. Cheers! CptT

As far as I'm aware I have. No menu comes up at all, it's not just that nobody replies to my radio calls.

Hi I have just come back to the Spit after a time away. The colours all seem to be washed out. There was an issue a while ago where the colours would wash out if the supersampling on the VR was turned up above 1.4. I have turned this down to 1.4 and it is still very light. Has anyone else had this problem? Any ideas for a solution? Cheers! CptT