repsol

In scenarios some basic background noice could quite easily be added with the help of a trigger....could it not ?

I hope we will indeed see the BK90 included. IIRC it was withdrawn from inventory due to an international agreement to ban cluster weapons.

Nice...thoose rocket attacks are spot on ! :thumbup: Just the way i remeber seeing them during my time in the army back in the days. Winter conditions... and thoose lovely planes comming in low and fast delivering rocket salvos... Just like that !

Rodd... Excellent movie ! Describes the Viggen very well (to bad it is not translated though) 600 ! killed pilots...Thats even more then i would have thought Close to 2 pilots every months payed the ultimate price to preserve our neutrality... Respect to thoose guys !

I think it will be very different compared to the A10C, the F-18 (when released) and other more modern strike aircraft that usually operate from medium to high altitude. The attack Viggen did most of its work at treetop hight, flying at very high speed as far as i know (unless that changed during its last years of service due to improved avionics...) Should be good fun !

According to the document provided by Sporg that joystick is used to - control the radar... but probably also slewing the Mavericks...

colladiable trees all over the map :thumbup:

The "Viggen-way"...:) Operating from roadside bases and to a large degree relying on conscript soldiers to maintain them in the field... Sorry for the swedish narrative...hopefylly it will be viewable anyway https://www.youtube.com/watch?v=PoQtnugT6A4 I hope we will get the Viggen and a nice map to go along with it with usable bases like this... :pilotfly:

I did a testflight with this mission and it seems that some of the recent updates have messed a bit with it...It's not working proberly anymore...The target-jeep is not arriving at the intended location for some reason...It used to work just fine but right now it is not playable ! Sorry...

Hello phenom 419 It was quite a long time ago i made that mission so i will have to check it out to be sure but if memory serves me... the thing you will need to do once he stops is to use the COMMS menu F10 option to report that the target has stopped at that location. Once you do that you will be told to hold at your precent location and maintain observation of the target until a predator arrives and takes over the observation duty (will not take to long). When the predator arrives on station you will be told to return to base to rearm and refuel and then go back and bomb that building... Some other things will happen during the mission also that require your attention...pay attention to radiocalls... Hope this helps you out...

- startmenu...top selection (user name) - saved games - DCS - There you'll find 'Config' at the top - create a new file with notepad++ called "autoexec.cfg" and type in thoose two lines and save it to the config folder...Thats it

Hello Kuky... A BIG thank you for your suggestions ! Things are working again :thumbup: I'm back in the sky... blowing things up... and it feels great :pilotfly:

I changed the priority...It seems to have reduced the stuttering slightely but no where near good enough. I will try 1.25

Thanks, Lange 666 ! I will give this a try...

Forgive a stupid question...But HOW do you set the process priority of track ir to high ? I would like to try this and see if it helps...Othervise i will go back to 1.25 also... Thanks/ Repsol

I'm also experiencing heavy stuttering now using track ir ( CLOD and ROF is working fine )... This is very frustrating because after updating to the latest beta Nvidia driver the game is running amazingly well without track ir... Almost constant 60 FPS and pretty much no stuttering when the FPS drops below 60...I'm also able to run the game without Vsync enabled (no tearing at all) now...Not possible before for me. However...The terrible track ir performance in 1.26 makes the game more or less unplayable (have gotten used to track ir and find it hard to play without it)... ED, please try to fix this ! Regards/ Repsol

Hello again, Speed Thankyou for your assistance ! I have made a new short version of the mission...named (bug report version). I have edited the first post of this thread and attached both the origanal pictures and the short version of the mission as well as the new bug report version. In the bug report version i have removed the entire mission exept for the player A10, AI A10 and the first and second AI A10 targets... Hope this helps to find the problem Thanks

Hello... I have attached a 'scaled down' version of the mission... In this short version the problem will occur within a few minutes and will not require the player to do anything other then to take up an orbit pattern and watch the TAD screen. A full description of my problem may be wiewed in the mission briefing... I also tried to upload the full mission but the file is to big to upload here (5.16 MB). Any help will be apprisiated...Thanks

Hello, Speed This was my intention with this thread, 'bug report'. Maybe i expressed myself a bit negatively but i was quite frustrated when making this thread after spending many hours trying to fix the problem and thinking i had done so after several succesful testruns only to find the problem returning once again... That's part of the problem...The mission will work fine for a number of tests and then for no reason that i can understand the 'bug' appears and ruins the mission AI-planing. I did do a forum search...Using the keywords 'AI TARGETING' and simply 'TARGETING' but found no thread with a simular problem...I guess i could have done more searching but i don't really know what other keyword to use... The reason i only posted a few screenshots is that the problem does not occurs at the start of the mission but will require the 'tester' to fly the mission for 30+ minutes before the problem shows itself...I thought thoose screenshots might be enough to explane my problem... I will try to upload a mission were i have 'skipped ahead' to a few minutes before the 'bug' happens...and also the full mission... Regards/ Repsol...

I gave this a try... - With the NOTHING task the AI A10 did not attack at all - With GROUND ATTACK the problem remained the same as with the grayed out CAS task (the AI seeing som non-existent target, offmap)

Hello again...No it was the CAS task in the ADVANCED WAYPOINT that i had removed... Should i put this option to...NOTHING or perhaps GROUND ATTACK ?

Hello Jona33 I have done that...does not help I will look at it again just to make sure those CAS tasks are gone..

Hello... I'm working on a mission in the editor and i have come across a big problem... For some strange reason the AI A10 choose to 'turn its attention' to a non existent target hundreds of miles away instead of attacking its asigned target (perform task-attack unit) This does not happen every time...Sometimes the AI A10 do actually attack the asigned target and everything works as intended...but the next time i test the mission the AI choose to focus on this 'non exsistant' target that is not even on the map (making it its SPI...se pictures). This is ruining the AI plans and the mission will not work :( AI targetingproblem SHORT.miz AI targetingproblem (bug report version).miz

Hello, Habu 23 Thanks, looking forward to V3 :pilotfly: Yes...the thermal signature for all units seems to have been a bit reduced in one of the latest updates i think...but if i'm not mistaking the FLIR camera displays will be changed in the upcomming 1.2.3 patch.