VampireNZ

TMS left to cycle through the different modes TV, WHOT, and BHOT to see what is working best for the current situation. I generally find Black Hot to work best in highlighting vehicles etc. Just today was in the freefly instant mission with some Mavs and used this to locate an ammo and fuel truck hiding in some trees. Very visible in BHOT mode. Don't forget all your zoom options either. General zoom level for search, then EXP to get close for a good look. But generally a TPOD is THE worst thing to use to actually search for targets as such - we always equated it to looking trough a toilet roll to search an area - so not very efficient. But by leveraging the FLIR capabilities this gives you and advantage if you have a general idea of location. Oh and just quickly - golden rule of the TPOD - just TMS down-down-down-down lots to get right back to 'baseline', then hit CZ and you should be good to carry on. Standard moves after any TPOD usage etc. Hope that helps.

I think you will find it is 100% true, and if you look at the ordnance that is jettisoned - exactly the situation you would employ it. If you just want to drop your tanks for no other reason than they are empty, you use S-J. (FYI generally you don't go around punching off empty tanks just 'cause you can' either. Take them home and land with them). If you get jumped on the way to an A-G mission and are merging - you use Emerg Jett to get rid of everything except A-A weapons so you are not dogfighting (and dying) with bombs/tanks on. You don't enter a DF with someone with tanks fit then faff with the S-J page - period.

Maybe one day someone at ED will google a picture of an aircraft drop tank....and see the cap at the front that you can open, place a refuelling nozzel in, pull the trigger and the tank fills up with jet fuel. In know...I know - black magic.

Cheers Apache - generally when you are getting the sh!t bombed out of you, the last place you want to be is 'hanging out for a bit watching the fireworks' lol. Just the thought of ex-air force aircrew for you . I always taxied out left then right to the intersection and departed from there as requested. In any case, by the tenth time trying it I was sorta over it and it was just 'kick the tires, light the fires and GTFO' - you have seen my TacView files so can place where I was in the 'scheme' of things. So prob airborne a bit quicker than 'average'. My personal opinion is you don't really need a bunch of Mig-29's 'hanging around' anyway, they would escort the strikers in, encounter no air resistance then bug out 'during' the bombing due to bingo lol :) . But oty. loving the Campaign in any case - thanks for your work!

This really needs to be incorporated into the standard game - looks awesome! Thanks for this mod.

Thanks Apache. Yea I think maybe a trigger for when the Sabre exceeds say 50 knots or something during takeoff run. As it stands now it seems there are a whole bunch of aircraft (perhaps too many for a 'sneak' airfield attack - just a few strikers seems more legit) just loitering around the airfield when you get airborne, and don't 'despawn' till you exceed 800' or so. So if you try to run south low-level they follow/launch heaters at you. Also once they are engaged with you it seems they stay regardless - see my 2v1 against 2 Mig-29's (thought I had them! lol) Tacview vid. Yea I noticed the incorrect morse signal on the KB in about half of the missions or so up to this point. IIRC you have ... ---- or something. Aside from the utter frustration in that one mission (heater in the face 3 seconds after airborne will do that to you lol), really liking the Campaign so far! On the plus side - the multiple retries for that one have me up and running in record time now!

As per title - with Taxi/Landing light on there is a round pink spot the size of the light on the ground beside the nosewheel. Using VR if that makes a difference.

Still broken - Just tried this mission and got taken out twice four times by heaters launched at me as soon as I was airborne (and one gun) and heading south. How exactly are we supposed to fight multiple Mig-29's in a Sabre? I am stoked you like the aircraft so much, but I think the pedastal you have placed it on might be a little too high. Also, what happened to "the attacking aircraft are bugging out...engage the 3 from the south". Do I stay and dogfight Gen 4 fighter aircraft with heat seeker missiles, or go after the ones to the south? (scratch that - there isn't a choice - they chase you either way - high or low...whatever) I did notice the aircraft that shot missiles at me on previous attempts de-spawned on one of the tries....so perhaps supposed to happen every time (but its not)? Also, not digging the SU-25's which also just go fully ballistic with a full weapons load.....really?, GG DCS UFO physics. Also FYI your morse code for homebase NDB is incorrect in the kneeboard pages. Edit - Couple of Tacviews for ya also....fun times. Notepad++ edit campaign inbound.... Relic_1.zip.acmi Relic_2.zip.acmi Relic_3.zip.acmi

+1 for the realism immersions. Pretty standard to have last-minute freq changes before a RL op

Nice - thanks Bunyap! Something for me to read at work today before getting stuck into the missions this weekend. Edit: Wow very comprehensive procedures and briefings - very impressive.

Yea not sure what is going on , I don't think Steam reprojection with AMD 6000 cards is very good. In any case I mucked around with MSAA on then off then on again, and also reinstalled SteamVR and tried switching Motion Vector on and off a few times, then all of a sudden I was at 10ms all green sitting at 90 fps. Beats me. Want to run with Motion Vector on and sit at a steady 45 fps but not if it decides it wants to drop to 30 fps all the time for no reason - unplayable mess. Sooner keep it at Auto and take the shudders as it swaps between 90 and 45. Hopefully SteamVR improves its reprojection with AMD cards in the future.

I am having an issue with the G2 and 6800 XT where it drops from 45 fps and locks to 30 fps which results in really bad ghosting/stutters etc. Frametime is still fine in the low teens so no reason to drop to 30, my previous 1080ti would happily sit locked to 45 fps with frametimes ranging from low teens to 20's and wouldn't drop below that 45. What is making the 6800 XT drop below 45 to 30 when it doesn't neeed to, and how do I stop it? I have reprojection set to 'Motion Vector' in headset settings to ensure it is on, and to 'Global' in SteamVR, as if I set to 'Force Always-On' in per-application settings I still get FPS wandering around in the 50's etc, not locked to 45. Headset is set to 90 Hz in WMR and SteamVR. DCS pretty much unplayable with the G2 dropping to 30 fps all the time for no reason, so thinking of just going back to 1080ti and nVidia.

This! Until ED sort out the area of effect weapon damage from rockets and cannons etc, aircraft like Hind are pretty pointless in DCS doing what they are supposed to do. A 30mm round doesn't need to hit you to kill you, and seeing nil effect on nearby soft targets and troops 'walking it off' after a rocket salvo is just rubbish.

Yea TWS is pretty hit and miss at the moment. Just getting back into the Viper this week after a long break (am used to that 'other' sim, so the 'simplified' DCS Viper was annoying me). I tried a Viper free fly instant action mission on Syria and there are 4 Vipers flying wide formation up to the Nth, and approaching them from behind I could TWS cycle 3 of the 4, but it refused to cycle to the fourth aircraft for some reason. You also need to give it a fair bit of time to build the TWS picture, then yea just TMS right to swap all tgts to system, then you can 'mostly' cycle through them. But sometimes TWS just doesn't work properly at all - usually when you have multiple bandits inbound and you are faffing trying to get TWS to work properly and end up in a dogfight. End of the day RL radars aren't perfect either, and if it isn't working you need to make the decision to move to something else. What I miss most is the TTS and especially the Spotlight mode - but I guess they are coming in due course. CRUS ICP would be handy too...

NO.......I was quoting what you asked me to check, out of the graphics.lua. Figured since you were telling me to check it, you might recognise it...

--in stereo and hmd mode you can try to use single parser for both eyes , by default is false , comment to enable it or set to true stereo_mode_use_shared_parser = false I have tested this feature before, thanks thou.

I think the RL/DCS manual assumes a level of common sense in that most pilots would realise dropping bombs after hitting the ground is less than ideal, and therefore a little maths is required to set the INDEX altitude ABOVE the target altitude by the amount indicated by the MPC. So the super-handy MPC handily tells you the INDEX is 3,700' - you say thanks very much Mr. Helpful MPC, now I know I need to release my bombs 3,700' ABOVE the target (cause dive bombing from below the target is hard and for experts only....once), which in this case is 4,000' - so by amazing mathematical gymnastics requiring years of honing, I am able to deduce I need to set the resultant INDEX altitude on my nifty bombing altimeter instrument to 7,700'. It does not specifically call this the RELEASE altitude because it is just a reference, the pilot may elect to drop sooner or later depending on many different parameters such as wind or resultant bomb behaviour etc. He may have dropped exactly at the index alt last time and it fell short for example by a set amount, so next pass the pilot may drop a little differently. We used to do exactly that while bombing in the P-3. First pass may have been out when using 'standard' parameters, so next run you adjusted accordingly with variations to the known INDEX. Hope that helps a bit

Cheers, yea my specs used to be in my sig, but I guess that stuff has changed with the new forum. In any case the Q was more for ppl who know what is causing the issue/have also had the same problem and fixed it as there are lots of other ppl here with G2's- not so much guessing what it might be based on my system specs. Also I wasn't getting the issue with my Rift S so is G2 specific. Also yes I have V5 of the tree mod - seemed pretty obvious this might be causing it so tried with and without it and get the same issue. Also the tree mod is only for one map, I get the same thing with all trees on all maps.

I was wondering if this could have anything to do with the fact trees are rendering in at different distances in each eye in my G2, and some distant terrain also looks 'odd'? I dont have the "options.graphics.stereo_mode_use_shared_parser = true/false" line in my autoexec.cfg file at all.

Wondering if someone could help me please. Just got my Reverb G2 and generally things going really well, nice stable 45 most the time with crisp graphics etc. However - I have noticed that trees draw in at different distances, meaning that there are two different 'versions' of every tree leading to very disorienting looking trees in general. (So close one eye and trees are 'growing' into the sim at the tree draw distance, but then if you swap eyes there are no trees there yet till you get a bit closer). This then means all trees around me while flying don't quite 'look' right as if there are two different trees at each location. Anyone that has seen two different versions of an object in each eye overlaid before will know what I mean. I also see a similar effect with distant terrain/hills also - so they seem to 'ghost' and not quite look to be in the right place. I previously got a similar effect in my Rift S when I tried the parser line in autoexec.cfg file with shorelines etc - so the water would be in one place at the shore in one eye compared to the other eye - so both combined looked VERY strange. So quickly removed that line from the file. If anyone could help with this strange fault then I would be very appreciative - as this is really the only issue I am having with the G2 in DCS and it is a bit of a show stopper really.

Also seeing different render distances in each eye in my new G2 - very off-putting as you say. Is very noticeable with trees and some scenery/hills. It means they sort of appear to be ghosting and just appear 'wrong'. Any ideas what is causing this - how to solve?

+1

Just STT everything, then you can fly free of worry like in the Viper - that TWS doesn't work properly either ;) Firing at 6 different targets simulateously is cheating hax anyway isn't it? - DCS all about equality...STT for everyone!

Edit: Forget I spoke, brain fade combined with just getting back into the aircraft in the last few weeks.

For when you think AAR in a chopper is 'easy mode'...sling load as well.