Fisherman82

I tried MOOSE now but was unable to get it to work. I tried loading MOOSE in the mission with do script file and then I tried to get a SH60 hover along side the carrier and a recovery tanker take off from uncontrolled state on the carrier using scripts but I was unable to get it to work. I hope ED adds this to the core soon Skickat från min D5503 via Tapatalk

But I dont use MIST or MOOSE in my missions because of the need to update them with new versions of it. In the best scenario, in the worst scenario a DCS update makes MIST or MOOSE incompatible and the missions I worked on many many many hours unplayable. So I use only whats in the ME, and this must be coming. It would just be nice if they would confirm it. But thanks anyway! Skickat från min D5503 via Tapatalk

It would be nice to hear if they are planning the ability to have a helicopter escort a ship and a tanker to orbit with a circular orbit with a ship (carrier) as reference for the orbit Skickat från min D5503 via Tapatalk

Is this a different mod than the Community Superbug Mod that was canceled recently? Is this one still on because its only AI or is this also affected by recent changes by ED?

I saw "Offset waypoints" planned for 2021 and thought that we would not get the finished nav system until then. Hopfully Im wrong because I have been waiting for it since the Hornet was released in order to interact with JTACs in a reasonable way. As I understand it "Mark points" planned for 2020 are more about marking the position where your aircraft is at. But I might be wrong about that as well. Skickat från min D5503 via Tapatalk

Hello, When Im starting a mission on the SC with the Horning as a player using "Takeoff from parking hot" in the mission editor I am unable to get a catapult assigned to taxi to when I request launch on the communication menu. I have both radios tuned to the SCs frequency. Am I missing something or should I report a bug with a track-file?

I get that ED does not guarantee that mods will work after updates, they have other stuff to focus on and that is perfectly ok with me. I know that you should remove all mods and all that if you encounter problems and thats also fine, I get that. However, if you try to open a mission you have created with a mod now you get to know what mods you need to have for it, that is also fine. But if you do not have the mod you are not able to even open the mission in the editor and that is not so good. If you loose a mod or it becomes unsupported after a update of DCS you might not be able to fly or even edit your missions and thats not so fun if you spent a lot of hours creating them. Its fine if there is a block for running the mission if you dont have the mod, but there should not be a block for opening it in the editor so you can remove them. I cant see a reason for why someone should be blocked from editing a mission just because they dont have a mod. Instead objects in the mission that the user dont have in their installation should be loaded as "Unknown object" perhaps as a red 3D-cube in 3D. Dont even have to be 3D at all, it could just be shown in the editor somehow and missing in the world. This is not a request for ED to support mods but just (in my world at least) a small change in how the mission editor works. If ED someday would decide to remove some of the very old objects in DCS it would apply for that situation also. Before I updated to 2.5.6 I had to edit all my missions to create mod free version in case i would not be able to access them after the update. I would have liked to be able to do it only if there would be a problem to some of them and not as a precaution on all of them. If you get locked out of your own mission the last hope is to edit the mission-file in Notepad and change the units that blocks you from opening the mission to something else, that is very time consuming with great risk for errors for me at least and I would really like to be able to do it in the editor instead.

I picked up the L-39 in the stay at home sale and is flying it around the russian airbases in Caucasus looking at the scenery and sometimes bombing some helpless truck. In the L-39 there is one switch for navigation lights with settings for off, steady and flicker. There is no separate for beacon. Western aircraft like the Hornet i think i figured out how they use them IRL. In peacetime that is obviously. Beacon always on when the engine is running and nav lights and formation lights depending on the situation that is. But how do Russian aircraft us them, during a normal training flight in peacetime that is at home in Russia. I have tried looking on Youtube but havent been able to make it out. In DCS the AI seem to taxi with steady lights and flashing seems to not be mandatory when the engine is running. But the AI in DCS is perhaps not the best source for IRL procedures so thats is why Im asking. I could get it if you would use flicker all the time the engine was running, but then when would you need steady? Forgive me if this question is too nerdy but I always think of this when flying the L-39 even if I cant even see the lights from the pilot seat..

Yes but Im on the stable so perhaps its fixed in the OB then Skickat från min D5503 via Tapatalk

Here is the mission with no mods, the track, DCS.log and my pc specs. Hopefully someone will see it So now you dont have to move i since hopefully its a proper bug report now. If I have not missed any formality. Bug static on AA-radar.miz Bug static on AA-radar.trk dcs log.zip

Has anyone else noticed that AIs ground targets show up on the air to air radar as hostile aircraft if the datalink is on? I suspect it occurs when the AI passes its waypoint before the target and gets its enroute task to attack it. Im on the stable version. Edit: Can some moderator move this thread one step up because it is not a bug report? I put it in the wrong section. Skickat från min D5503 via Tapatalk

The wierd thing about this is that this worked ok a while back, I did refueling training missions with my AI wingman just fine, we where hooked on the same time at our respective basket. However recently it takes him as you say forever, so refueling AI wingmen is not really possible now if you want to go refuel together, you will have to leave him and hopefully he will rejoin a half hour later if he survives the refueling. There has been a unfortunate step backwards regarding AI refuellng apparently.

So before and after we fly a night mission we must go into options in DCS and change the brightness, and also not take long flights that go from day to night.

If I remember, your task was to communicate with the forum on RAZBAMs behalf, I thought I saw that in some old post. Surely as a representative, you must be able to relay this feedback to the team?

Are there more things not implemented in the Early Access version that will never be implemented in the final version? I mean who would have thought that this kind of thing would be degraded to a slider in the special options when they bought the early access version. Sure, the description probably did not say we where supposed to be able to adjust it, but it probably did not say we where supposed to extend the landing gear either. Basically this means that they feel that in the definition of a full fidelity module, working adjusting of brightness for displays is not included so if they like they can just skip implementing it during the Early Access period. There must be some kind of basic requirements for what the finished product should include in order to be sold as a full fidelity module in the ED store. Could RAZBAM provide a list of similar features that have been canceled for implementation in the final version since the module was released as Early Access?

I dont mean to criticize your post but I just have to say that to me VAICOM is like going VR, its no going back. I can not belive that everyone is not using it. In the beginning I had big problems eventhough I had a good Sennheiser headset with a very good mic I got bad recognition. I guess there my desperate postings about this is somwhere in the giant VAICOM thread. It turned out to be related to me needed to use a extension cable from my Zonax sound card. Bought a cheap usb sound card just to run the mic and now I have no problems. So for me it just runs now, it tells me when there is a update automaticly and I update. Never any problems setting up PTT or anything like that I have the TXes mapped to keypad 1-5 and then I just map the ones I need to my Warthog. Worth every dollar and even a weeks effort to set it up if thats needed because in the long run it is totaly worth it. I hope everyone is aware that it exists. Skickat från min D5503 via Tapatalk

Hello, some models use external tracking with lighthouse system, and some use inside out tracking where the headset uses cameras to recognize the surroundings together with accelerometers in the headset to work out where you are looking. The inside out trackning is newer and most likely will be what will be used going forward in future headsets because its simpler and you dont have to put up lighthouses with cables to them also. I bought a Rift S a couple in the beginning of March as my first VR-headset, it uses inside out tracking from 5 cameras on the headset together with the accelerometers. I bought that because it had a good balance between performance, price, ease of use from what I heard from other DCS pilots on the forum and so on. But actually when I bought it I was worried about the tracking, because I have a cockpit setup where Im basically sitting sideways inside a closet, so on my left shoulder I have the open room for surrounding and on my right side there is just a black wall 10 centimeters next to my shoulder. I was thinking that the right wall may be a big problem for the tracking and before I got it I planned to put up IR-LEDs inside the closet to get references for the cameras on the headset because I thought It would be needed. Then the Rift S arrived and I set it up to try it, I was preparing myself to have to send it back in case the tracking did not work in my setup. However, I got pretty blown away. It worked very very good, I mean when Im looking to the right Im looking straight into a black wall just some centimeters away but it still tracks perfectly 99% of the time. On some very rare occasion it looses tracking, and that is when Im looking to my right into the wall, but I think that is not related to lighting conditions or the wall only because as I say it works 99% of the time, I have tried to figure out what is causing it and I think its more related to something else in the computer, like DCS stuttering just when I turn my head or some software running in the taskbar or antivirus or something. But its so rare so its not really a issue. I have been trying to figure out how the tracking works more in detail but if you google it you only get info how the tracking of the handcontrollers work, not the tracking of the headset itself. When Im looking at the wall im pretty sure it uses the input from the accelerometers mostly because I cant see how it sees anything then. If you would be sitting at a desk so that you would have room on both sides, the light on in the roof and shutters closed on the window if its daytime I cant think that you would have tracking problems with the Rift S. If you do it would be related to something else in the computer. Im very pleased with my Rift S, although there are headsets with greater resolution Im pretty happy with running the Rift S with 1.2 Supersampling and 2x MSAA in DCS on my GTX1080. If I could crank up the Supersampling to 1.5 or 1.6 the clarity of the view would be even better so Im hoping for that in the future when I someday get a better graphics card. To do that now I have to turn MSAA of and then the world looks really bad. I had to buy a Starforce USB 3.0 expansion card that gets power straight from the PSU though because when connected to the motherboard I had major problems with "the headset is not connected". I think this is a common problem with VR headsets, they need to have a good powersource for the USB cable. If you have not tried VR, the difference between DCS on a screen and in VR can not really be overrated. Its just no comparison. Perhaps this was a long answer but thats because Im in a boring Skype-meeting and Im happy with the Rift S.

I have never gotten Repeat brief to work What is it supposed to do? Repeat the nineline for JTAC or all transmissions? Skickat från min D5503 via Tapatalk

And a absolute must in VR. A Kneeboard page where the latest 9-line given by a JTAC would be auto generated would be fantasic. It would also be good with a page where info from ATC is generated, I guess that would be good with the new Supercarrier module where I guess there will be pretty much info to remember otherwise. Skickat från min D5503 via Tapatalk

I injected the whole checklist I found on the internet. The one for for the Harrier i deleted some pages of stuff that wont be used in DCS, thats 229 pages now and that works. For the Hornet and Viper I did not do that and got more pages, I have done some cleaning now of stuff that wont be used but I have not tried again. But it would be interesting to know why it works on the monitor but not in VR with 300 pages, there must be some memory that runs out or something Skickat från min D5503 via Tapatalk

After more investigating, and a DCS cleanup followed by a DCS repair again I have found the cause of the problem, however no solution. The reason for my problem is that I had many pages of checklist in my Saved Games\Kneeboard folder for the Viper and Hornet. More than my other aircraft. This causes the kneeboard maps not to generate in VR in my Rift S. When I removed all but one page it worked. So somewhere between 1 and 300 pages there is a limit, unknown where, only way to know is to put on and of the Rift S and start and shut down DCS 300 times to try where it is. Unless ED could give a hint for where the limit for number of Saved Games\Kneeboard goes for the maps to generate in VR.

Can some moderator rename and perhaps move this thread? Since the tread is about kneeboard maps with flight plan not beeing shown in the Oculus Rift S for ED Hornet and Viper modules only and it works for Razbam and Heatblur aircraft aswell as on monitor?

In my single player missions I use a trigger that sets a flag to a value from 1 to 60 every minute. This can then be used to controll all kinds of ramdom activities. Like starting a AI-flight from a base for example. This works pretty good for missions that dont take more than a hour. If a mission takes more than that one may consider to increase the max value from 60 to something else. It can also be used for this, if you use switched condiotions to turn each EWR on and off. Make EWR1 turn on when the random flag is 1-20, EWR2 on when it is 21-40, EWR3 when it is 41-60. And EWR1 off when the flag is higher than 20, EWR2 off when the flag is lower than 21 and higher than 40, EWR3 off when the flag is lower than 41. If you have the random flag to set it self every minute then a EWR may at minimum just stay on for one minute. If you like to limit this you can change how often the flag is set or you can perhaps include time since flag conditions in the triggers I described. This should work if you change beween green state and red state in alarm state (if I remember right its called alarm state). If you use activate and deactivate the group I dont think you can reactivate them again when they have been deactivated.

After some more testing, I did the following findings: Caucassus is not ok either, it worked only because I used Viggen there and Hornet in the others. So after testing all my aircraft I see its not terrain related but aircraft related. It works for all aircraft exept EDs Hornet and Viper. Do they use some different way of showing the kneeboard maps in VR compared to the other aircraft? Skickat från min D5503 via Tapatalk

Ok, thats the opposite of me then, I only have custom files in my saved games kneeboard folder. And those work well, but the autogenerated maps with the flightpath never loads in VR, only on the monitor. Skickat från min D5503 via Tapatalk