DragonSoulkin

I wasn't expecting the paint-kit to come out day one with the plane so that I'm not worried about. What I would like to see is dynamic bort numbers so those of us that fly in large groups don't have to have x-ammount of different liveries for every single modex and can just have one livery and change the number yourself like you can with almost every other module not made by HeatBlur.

Experienced this as well the moment a friend hopped in my back seat. Went from 60fps to 10fps...

Well if it doesn't break IC yet, it will. Like anything else that seemingly arbitrarily triggers Integrity Check Failure like changing the default kneeboards or a briefing menu image.

In my numerous attempts at creating an R_NAV_data_Sinai.lua I never could get anything out of it, as if the .lua wasn't there at all, so I was holding off on creating an R_NAV_data_Kola.lua as I didn't want to sit and waste my time for another thing that couldn't be done on the user end. So it's working then for Kola? Does it break Integrity Check?

So as it stands with the MiG-21bis in DCS, we have non-editable (without breaking integrity check) RSBN and ARK beacons on the following maps through the use of an R_NAV_data.lua. Caucasus Nevada Normandy (why?) PersianGulf Syria TheChannel (again why?) We are missing an R_NAV_data.lua for the following maps: Kola Sinai I have attempted to create such a .lua from scratch for the Sinai map, but was ultimately unsuccessful. I figured with successfully adding more beacons through the R_NAV_data_Caucasus.lua that I could just make one for Sinai and well, nothing happened but a big waste of time. Now with Kola released (yes, I know, EaRlY aCcEsS), that now makes 2 maps with absolutely no navaids besides a map, compass, and stopwatch, making navigation in the MiG-21bis comparable to WWII, but for whatever reason, those maps HAVE those navaids. I don't understand what goes into making these navaids, nor do I understand why after all this time that Sinai STILL doesn't have any, and now another map doesn't as well. Both of these maps have quite a bit that can be done historically with MiG-21, but as it stands we just gotta muddle through. So is there a workaround we can do in the interim, or are we just up a creek without a paddle till judgment day is at hand? Is anything being done to fix this lack of navigation systems for these maps? And lastly, why isn't there an RSBN beacon that can be placed like the TACAN beacons through the mission editor?

So it's worthwhile then to still have the liveries for it but no need for the extra kneeboard file?

So one of the things that's really bugging me about this rotorcraft is I've been unable to find the info or figure out which versions are which for the purpose of mission building, kneeboards, and skins. Could someone give me a breakdown please? I've got 5 variants in my kneeboards folder because I couldn't figure out which was which and how it was titled and ended up spitballing till something stuck and cannot for the life of me remember which ones it was.

Yes I am. I've been running Model viewer almost daily for well over a year and when I changed my resolution to fly in 4k, the liveries tool plug-in won't show anymore. I had to downscale my resolution back to 1080p to be able to get the liveries window to pop up. It's quite the PITA to have to switch resolutions back and forth if I want to fly in 4k and later do liveries.

I am currently having a problem with ModelViewer2:0 with the Liveries Tool Plug-In while using 4k resolution. The plug-in will not show even though the window itself changes to the background when attempting CTRL+L. When I reverted my resolution back to 1080p, it works just fine.

I was wondering the same thing. I tried making this a few weeks ago and got absolutely nothing. I'm also trying to add beacons to the Rnav lua for Caucasus but my direction and distance are waaaaaaay off and I'm not getting the morse code for any of the beacons I made except for one which is still 200+km off. Double checked coordinates and they're correct as far as I can tell.

Has any progress on this been made in the past year?

I don't know. I was also completely locked out of all "my" paid modules.

I've always been a firm believer in if I buy something outright, I own it and all its contents. You pay cash for a car, nobody can take that car outside of you doing specific illegal things with it. I buy a burger, I eat the burger. It's the same thing, but in the realm of purchasing digital things it seems the sellers hide behind long winded disclaimers masked behind legal jargon that the average person isn't going to read and/or understand. My first experience that opened my eyes on this was when the first Destiny released and I had purchased the disc copy. There was a lot of content that was "locked out" but still on the disc yet when players found ways to access this content before its "official release" they were punished. So I bought the disc, but wasn't allowed to access all the content I had purchased on said disc? It doesn't make any sense. Here on DCS it seems it's no different. We can pay hundreds for all these digital aircraft but god forbid you end up without internet for any extended period of time, or the servers go down, or this or that, bam you can't play with the digital planes you paid more than the cover price of an entire game for. It's absolute and completely total BS. So instead of actually buying a module, what you're paying for is the temporary permission to use a module that can be taken away at any time, without notice or reason, at no fault to you.

That's what I ended up doing and it did work, it's just weird to suddenly fail IC for something that's default.

So I'm having an oddball of an IC failure here. Screenshots are provided, so pretty much the IC failure is in ImagesGUI is what the game is telling me. I go into that folder and it's the default image for the M2000C. I double-checked my mods and none of them have anything that would go into or replace anything in the ImagesGUI folder, so I'm at a loss here as to what is going on.

In MT I can get the targetting pod to stabilize, the issue I'm having is getting it to zoom in/out and focus. It seems like it's constantly trying to refocus and the zoom I can see the box enlarge/shrink but the zoom itself only works if I'm moving the TDC slew around. Edit: Track File added. JF-17 TGP Zoom Issues.trk

Actually I've seen this once with the F18 on Syria. Unloaded the gun into an F14A and it just exploded the same way as in this case. I've only had it happen once though. Us F5 when trying to view a target in the replay (or live). It locks the view on the target from the selected plane's position.

I haven't tried the bin-mt MV. I did manage to get a little further this last time on using MV, managed to load an edm model but then blip, back to desktop without notice. Could ReShade have something to do with it? I tried turning off all my ReShade effects and I disabled all my mods through OvGME, did a cleanup & repair, so far not much progress but it was something.

I don't get an error or message, it just plain crashes. The only MV folder I have in the path specified is edModelViewerTrunk.

I can't even use ModelViewer, I have a post in the bug reports section but all my work has been done repeatedly re-launching DCS and going into Mission Editor. ModelViewer crashes immediately after I launch it and I don't have a log folder or edModelViewer2 folder and creating one hasn't stored any logs so I'm at an impass there. I'd love to get it to work so I could get the lua lines easier.

So I'm at my wits end here trying to get ModelViewer working. To do all my livery editing I've been launching and re-launching DCS and viewing my work in the mission editor and I would like to be able to use the model viewer, especially in regards to getting .lua info for my liveries, but it crashes very shortly after launch. Trying to research this problem I saw a few posts regarding Saved Games/edModelViewer2/Logs/model_viewer2.log but I do not have this "edModelViewer2" folder and creating it myself has brought no results, no logs are being stored.

Mosquito PR Mk.XVI 653rd BS, 25th BG, 8th AF USAF January 1945 https://www.digitalcombatsimulator.com/en/files/3329741/

Mosquito PR Mk.XVI 653rd BS, 25th BG, 8th AF USAF February 1945 https://www.digitalcombatsimulator.com/en/files/3329528/

https://www.digitalcombatsimulator.com/en/files/3329507/ Mosquito PR Mk.XVI 653rd BS, 25th BG, 8th AF USAF June 1944 With working dynamic board numbers.