RafaPolit

@NineLine Maybe this will "summon" you to the thread so you can put this on the devs laps? Thanks. Rafa.

Image is "ghosting" on externally exported MFDs with the MT preview version: As you can see, the exported MFDs start "ghosting" without refreshing the panel contents. Every pixel gets "stuck" and not refershed.

I have tried this mission now for about 15 times (no kidding) and can say I have only "really" flown ONCE! It is a masterpiece!!!! Thanks a lot! But here are my issues: - 14 of the 15 times, after startup, I go into the catapult (whichever catapult) and the process will go out perfectly up to the last man which gives you the right hand side-to-side motions to go. I go into full non-afterburner power, salute (as I have always done and worked always perfectly), but no one changes position, no one kneels, I just stay there hooked to the catapult and no way of launching. What am I doing wrong? - I too had the tanker problem. Here's what happened to me. I went in to tank first, had a couple of disconnections so it took me "a bit", but not really a "very bad plugger". The thing is, I had a disconnection at the very end, Jester tells me we are full, but the Tanker's "menu items" are gone. I can no longer claim "abort refuel", and, of course, wingman always calls "negative", because there are no more tankers in flight according to the menus (although I am literally flying next to the tanker) . - I'm trying to re-fly it, but I cannot get the catapult to launch me, no matter what! Any advice? (Oh, and I would indeed make the changed suggestion to first send your wingman in to refuel and then try it yourself. Chances are your fuel is higher and it's OK if you move forward with less than a full tank, but if fuel capacity is an issue, then maybe instruct to take "half" and leave the rest to your wingman?) PS. You can see EXACTLY the issue about the tanker I described on this Youtube video: On minute 1h28m30 secs, the menu item to access the tanker dissappears. EDIT: So, I have the answer to my catapult problem! I feel a little stupid, but during night you don't salute to catapult, you need to toggle the master lights switch on-off. I had no idea. Sorry. It has nothing to do with the mission.

I have always thought that about the grass thing as well, but I understand the problem: in order to have low grass actually look like grass, you need millions of polygons to achieve that. For taller grass, it's much less. Even in the huge studios this is an issue: have you seen the hair on the 3d characters of every pixar / disney movie? Each hair is about the width of 100 regular hairs, and they try to keep it as long as the character would accept it. Clothing is another area where this affects things: most fabric is thick as leather! So, while I agree with your general comment, I understand the problematic behind it. Not sure what a fix would look like.

And an increase from $9.99 to $14.99 is 50% more. Check your MAR-LX1A calculator... it's failing you.

I cannot speak for everyone, but I can speak for myself: it's not the amount that bothers me, it's the fact that they announced a value and then they change it upwards (obviously never downwards). So, if you are purchasing a house and the price goes from $100.000 to $150.000 after they listed the house, would you get upset? It is the same margin of difference here. Literally, 50% more from what was offered. Yes, it's not $50.000 difference, it's $5, still, it's 50% more of what was offered to the owners of both maps. So, for me it's not the actual value, it's the concept and margin that upsets me. If it doesn't upset you, great. It does upset me.

Those are the things that, after all the praise and kudos one has given, brings us back to upsetness and critique. Think twice before deciding on pricing, and once you have committed to writing, stick with it. You failed and you wanted $5 more from every user, too bad, stick with your already-published pricing! Let's hope this is an oversight and they still plan on having that, because if not it will be the "steam F-15 pre-sale" debacle all over again.

Thanks for the answer. I'll have a look. I was hoping it was more of a "what I pick" solution rather than "what the HMD decides to show". Because my solution to the tanker or keeping an eye on a low enemy helicopter will not work with this approach. Thanks again, I'll report back once I have had a chance to test it.

Good afternoon friends. I am wondering how to mimic a functionality on the F-16 that I don't know how to do on the F/A-18. Maybe what I am missing is the terminology for it, for I hope you guys can help. In the F-16, I can SOI the HSI and TMS Forward on my Wingman and that would display his position on my HMD, even if he is beyond visual range. I will see it like an octagon to differentiate if from the other types of "lock". This works not only for wingmen, but also for enemies. The great advantage of this is that I can rely on AWACs info to keep tags on situational location of a specific thing I want to track. I use this for wingman, for tankers, for enemies I want to keep a "secondary eye" on. So far, I have failed miserably at reproducing this behavior in the Hornet. On the SA I can hover over a contact and see their angels, but I cannot "lock" them to render a "circle" or "octagon" or "square" in the Helmet display. Thanks for any insight or any alternatives to achieve a similar thing, best regards, Rafa.

@BIGNEWY I just reported that the pre-order is not allowing to pay with miles, nor is it adding to my existing miles if I pay without them. It has been noted that ED has mentioned that pre-orders actually should add to miles. Can this be fixed? Thanks.

I have to give KUDOS to the process of listening to the user base and reacting to that. We, as developers, are usually faced with this dilemma: stick to the original plan (which is the only wat to meet deadlines and budgets) or adapt to the user requirements. More often than not, this is a juggling process where you need to balance things a bit. The level of user-based-improvements on these posts really do show a profound interest in giving the users the best experience, and not just get out the map as soon as possible to capitalize on the eagerness of people buying. Thanks for this. It is refreshing and the effort is well noted, albeit these type of forums tend to bring out more complaints than praise. I know I have given some complaints about certain decisions, but the effort behind this is noted and appreciated. Rafa.

Good afternoon, The F-15 pre-order is not allowing to use miles to pay for it, nor is it reporting as adding my purchase to my existing miles. I was told on the Razbam forums that you have actually commented on this and that pre-orders SHOULD provide miles, so please fix this before I commit my purchase. Thanks.

For me the pre-order discount is a big part of the equation.

I think that pre-orders are a good way to inject cash flow into a project before the project is ready for release. Being a developer, it's a very complex scenario to require funding for several developers and systems and hardware and have to pay for that from your pocket for 2 or 3 years until the product is mature enough to be sustainable. Crowd-funding, pre-release sales, grants, external investments... all these mechanisms help mitigate that. Some come with strings attached, others require you to present a project to the community and hope they trust in your ability to deliver, and, therefore, be able to pay up front without getting anything usable for several months. It's a leap of faith from the users, and there is no security you won't simply lose that money. But, on the other hand, the developers don't need to make a profit to investors. So, it's a good option for me. Since it's asking a lot of faith from the users, it comes with a very good discounted price, which is also a good incentive to just risk it (from the buyers perspective). So I think pre-orders are win-win situations, as long as they don't actually make more damage than they do good. Obviously, if you can produce the funds until the system is ready, by all means avoid pre-sales and just market when ready, you have to deal with a lot less frustration and anxiety from the customer base.

No, because then they wouldn’t have already announced a date (ED I mean). They had already “approved” the process, that means they thought it was already there. Still, this brings up a matter of transparency: if they would put out a more transparent communication, we wouldn’t be speculating about it.

I believe there are several key factors at play here. Obviously no one will die due to a missed pre-release date. Obviously no one took vacations out to buy the module, since it’s not coming out immediately. This is all true. I am a software developer and I have probably missed more deadlines than the ones I have met, just because of the amount of unforeseen variables that come into play. This is 100% true, but it, obviously, changes with the amount of, precisely, variables in the process. So, if you have to develop a fully functional plane, with complex flight models and damage models and realistically simulated radars, etc., release date can miss by several months, for sure. We would all understand that. On the other hand, If you have to add a button to a webpage, then a three minute variable timeframe is already too long. What’s really involved in a pre-release? A price, a text describing the module (of which every single module reads similarly and there’s already a “format”), and a video (which they have mostly already produced, several times). There may be a few other variables, and if ED didn’t already have a platform for selling things, I would agree this is orders of magnitude more complex. It’s not the case. That’s why everyone “kind of” understood the pushback from the 3rd to the 15th. But, another delay on what already seems enough time to produce these very specific assets and which involve a lot less complexities than actual module development, does ring like a “how could you have miss-timed a preorder, where mostly everything you need is already in place”. There could be other unforeseen factors, but at this point in the maturity of the software, there shouldn’t. So this rises legitimate concerns on the company as to their ability to deliver what is promised. Given that we have many other modules (or even games!) to chose from, this is not trivial. I agree that they “wouldn’t have delayed unless absolutely necessary” as has been pointed out here, but the fact that they had to do it, twice, on a reasonably “simple” process, is of concern to some of us.

With what? The Thrustmaster Cougar MFDs? No, not only is one "not included", there is no "specifically made for them" display, so that's the reason of this thread, to show different implementations of different options available.

I wanted to extend my huge thanks to this post! Really changed my experience. It even works for night missions, I created a couple of profiles with different values for white point and gamma and I shift through them quickly depending on the scenario. This is a game changer if you have external MFDs. Big thanks again! Rafa.

This looks incredible!!! I understand winter is "different" and more difficult, but this is exactly the type of response to "critique" or "suggestions" that puts a smile on people's faces and makes us be more "happy" with our purchases. This, for me, changes this map from a: "very niche scenario", to a "wow, you can do anything but winter", and for that Caucasus is perfectly fine. I really love the seasons and the effort put into this. Thanks!!!

I wanted to share a big thanks to this thread, the community and especially to @Gierasimov! The suggestion to go with the VSDISPLAY 7" 7 inch 800×600 4:3 CLAA070MA0ACW LCD was ABSOLUTELY FANTASTIC! I'm going to share a little bit of my process: I was planning on building metal frames to hold the screens and then the MFDs on top, all to house larger screens that actually made little sense and I was not happy about wasting a lot of screen size. Your suggestions really put my mind at ease that the CLAA070MA0ACW could do the job... I couldn't be happier! Not only are they almost a perfect fit, I was able to install them without any alterations to the MFDs, no alterations to the LCDs, and I was able to still use the MFD stands, so the amount of work you saved me is really undescribable. In case my approach is useful to others, here's what I did and what was required: - 4 x 3cm M3 screws (the length will depend on the fixtures you find, M3 is a good thread but just pick something that fits on the original holes) - 4 small washers and nuts for those screws - Some thin metal plates, ideally with a hole that can allow the M3 screw a little wiggle room so you don't need to measure everything down to a thousand of a milimiter - Larger washers to secure the bottom part of the LCD - 5mm nuts to serve as "spacers" between the metal plate and the MFD - 1mm double sided tape (this can be any thickness, but you need to account for the 4mm of the bezel for the LCD plus the thickness of the tape when choosing the separator nut) How I did it is: - Start by securing the bottom part of the LCD with the bolt a larger washer and then the washer and nut like in the picture. This is ideal, because the LCD bezel is at its PERFECT height when resting on a bolt going through the bottom-most holes, which is a god-send! No need for crazy perfect measurements, it just aligns. - With this two bolts securing a little bit the LCD, center it horizontally so that you have symmetric "air" on the sides of the MFD to the SCREEN AREA (crucial here, don't center it to the outer size, but the inner screen area) - Once it's roughly centered (the beauty of this method is that you don't need to be milimetrically precise with anything!), secure the metal plate to the bezel with double-sided tape, using the bolt as reference (here's where it's handy if the hole in the plate is slightly larger) You are DONE! Now simply: - Put the 5mm spacer in the bolt, secure the back element from the Cougar MFDs, and place a nut and bolt (please note that, in this picture, the plastic frame is upside down, that is not the way to mount it, mount it normally with the opening to the top part as in the next image) I used the MDFs frame to further secure the PCBs that come with the LCD: And with that, I have my functioning MFDs with screens, for less than the WinWing screens. Not a LOT less, these are: - $90 for the MFDs + $160 for the LCDs (with HDMI breakout PCB and remote control!) + $10 of nuts and bolts = $260 - WinWing solution will offset you $349.6 and you don't have to do a thing, so it's note like a night and day difference Still, I love the result, couldn't be happier!!! And I couldn't be more grateful to @Gierasimov for sharing his "discovery" of these marvelous screens! The fact that I can use the Thrustmaster stands is a huge advantage for versatility and upcoming options. Thanks so much! Rafa.

I have to agree with the general hype about this map. The new images look great, and the new airports will certainly make for a much wider possibilities. I don't think anyone would go to the Big Ben to check the time of day, but that attention to detail certainly shows in many places and that is encouraging. I have been open about my frustration about the lack of seasons in this map, but its size and the addition of larger cities could very well make up for it. Looks really great. Thanks for sharing.

I've had this happen to me as well. I have not been able to pinpoint a specific culprit, though I have a couple of things that I blame for: - The iron may get a little colder when exchanging heat with a large component or one that can sink a lot of heat - I may try to "fuse" the solder when the component's leg is not warm enough - The iron's tip get's coated by the flux or rosin and it gets charcoaled and I no longer have the tip correctly covered in solder I blame a combination of (or all) those three things. When that happens, I wipe the iron clean with a cloth or wipe, I re-tip the tip with solder, wait for it to heat up back nicely, and then resume soldering. I would describe them as "mini spikes" or "uneven surface" rather than whiskers, but I know exactly what you mean.

Hello. I really appreciate this effort, I had a similar issue and was surprised how little documentation there is to use Witchcraft with modern OSs and NodeJS versions. However, your solution seems to have taken the "long way home". If I may suggest, the changes required are much fewer! You simply need to: - Remove the included NodeJS version with the newest one (at the time of posting its 18.13LTS) - Implement Socketio correctly with just this two lines: var server = app.listen(port, "0.0.0.0") var io = require('socket.io')(server); instead of var io = require('socket.io').listen(app.listen(port, "0.0.0.0")); That's really it. No other modification required, and this doesn't force a global installation of npm packages and other unnecessary stuff. If you try it and double check it to see it works, I'd be happy to support your Fork of the original asset. If not, I'll probably create my own with this much simpler instructions. Best regards, Rafa. ps. My solution does not address the automatic opening of a browser pointing to localhost:3000 , but that's really the only thing missing.

Good afternoon friends. I was wondering if there is a flow that would allow me to run everything I need in my main DCS machine and access some kind of profile / monitor / export / view from a remote browser preserving touch functionality. This is the scenario: I would configure DCS with Helios? Iris? To export all the views I need... then I access the DCS machine via IP with a web browser that can see AND INTERACT (this is crucial) with, for example, the F-16 ICP screen. So, I want to export the view of the ICP (and perhaps DED) and access it via a remote web browser. Why haven't I found a solution to my needs? Mainly because my remote PC is running Ubuntu on a RPi3. I have found solutions for Android Tablets, it would also work for remote windows machines that could run Helios on them, but my machine needs to access a somewhat different flow. Any ideas where to start looking? Thanks a lot! Best regards, Rafa.

Thanks! This is very helpful! For me, Winwing looked great, but logistics to send to my country are a nightmare, and Amazon US is better with an importing service, so I have the Thurstmaster MFDs incoming. Also, call me a snob, but I fly the F-16 more than the Hornet and I wanted the MFDs to be more like the F-16! Thanks for the info.