Jump to content

LorenLuke

Members
  • Posts

    368
  • Joined

  • Last visited

Everything posted by LorenLuke

  1. Yeah, it doesn't allow for keyboard binds in release at time of writing, but it can be bound to a non-keyboard joystick or gamepad device.
  2. If, assuming the grievances of both parties are valid, at least in part, and it ended up going to court wherein (again hypothetically) RB lost whatever IP theft was alleged, do you think the court would consider the money you proposed to be paid as damages and award it, or would that be lost to the aether ('Well, why did you pay them when they violated your IP? That's on you.') ? Even it it's foul, it's clear they think that some IP violation has gone on, and I can't say I don't see the business sense in withholding payment given this.
  3. Same button, but only when you're in thermal mode. There's HOTAS command to switch between television video and thermals.
  4. 150 rounds, shot in 3 round bursts, no reloading magazines required.
  5. The 'laser inhibit' only appears when you're more than about 170 degrees behind the helo. It's is done to keep people's eyes safe because the MMS is pointed backwards behind the helicopter, and may reflect all over the place by hitting the tail rotor, but more importantly, it tells you that the MMS is not at all pointed forward. While in the 'FORWARD' MMS mode, press the slave button a few times until the text says 'FWD' and the crosshairs are small, and it should slew to the fixed forward position. If that stops for whatever reason, just unslave it (MANUAL mode) and reslave it again, and it should work.
  6. Here's hoping Polychop have access to a deeper UI that can get that information and use it to move the camera to follow the drone's target.
  7. That assumes both parties are being reasonable. Have you ever tried to 'sort it out' with someone who would have it their way, and no other way? How do you sort that out with just giving in to their demands and giving up everything you want?
  8. It appears to be just picture, but if you use the drone as a JTAC, I believe the camera will follow the current 'requested' target.
  9. Check the highlighted section here again. '[A]ll FUTURE 3rd party agreements are now required to make the game files available'. StrEagle has been in development for over 10 years. This probably didn't and doesn't apply to this specific case.
  10. 'Jesus just fix it.' Yes, Razbam... please, fix the bugs.
  11. My major concerns more anything Multicrew/Multiplayer and just a lack of 'smoothness' between states. The RPM gauges and the like appear to freeze when in AI flight, which, if they had SOME sort of logical response curve to being moved by the AI pilot, I'd think that would be good, as well as having some sort of spool time when handing the controls back (because again, they just 'jump' to where's proper for your controls position as if you were flying it the whole time). The other issue is, as aformentioned, multicrew/multiplayer where I've seen the airbags deploy midair when exiting AI pilot mode (possibly some frame lag, or just too different a state between the real controls and AI) when they absolutely wouldn't have in any realistic scenario. I don't much care about the hovering being inhumanly perfect, though I wouldn't mind a little sway/drift from things like breezes and the like. Additionally, it feels like the 'turn left/right' slews way too slow, and is generally unaffected by the 'AI turn speed slow/medium/fast' commands. Whether that's a bug or intended, if possible I'd like it to be more responsive if you hold down the button on 'AI turn speed fast' to have the turn rate of more than what feels like only three degrees per second.
  12. Which is likely less now, given the deluge of F15E refunds.
  13. If those Razbam devs want to be paid, they should probably talk to the Razbam's payroll/CEO.
  14. https://forum.dcs.world/topic/350940-multicrew-display-bug/#comment-5454530
  15. Make sure you have Force Feedback turned off in the options menu.
  16. If using your 5th amendment right just makes you guilty, it's not much of a good right, is it? Responding with 'This is ridiculous, I'm not going to dignify that with a response' and then the other side saying 'OOOohh! AAAAaahh! Look, they didn't deny it! They're GUILTY!!!! ' is dumb. It's choosing to devote your time to things that would actually require your attention, not just constant accusations that are being made that you have to slap down every time they're made. The year of the Strike Eagle!
  17. You know what's absolutely wild to me as a concept? The refunds. Razbam refuses to support their module (at present) in wake of lack of payment, and starts this whole kerfuffle. People get upset with ED and/or Razbam, and demand money back on the F-15E. Obviously, I'm not privy to the contract, but if it's anything like the ones I've seen, I'm certain those lost sales aren't coming out of ED's wallet. I'm very confused on how they thought this would help them in any way. It's threatening the jailer for the key while you're locked in a cell.
  18. (I believe this works for target , it does work for waypoints) The alternative method is that you can go to the 'New Target' page (under Nav Setup), and enter the target number to edit the target point, then there should be 'prepoint' along the right. Make sure that's boxed and hit 'store', and that'll populate it to the prepoint menu (not sure what happens if the box is already full). Additionally, the last created point is automatically stored to the 'M' prepoint position in the PPT dropdown list.
  19. I'm just going to state here, that I think ED not pledging code support and maintenance of the modules is smart. Reminder that if they say 'Oh yeah, if this all goes south, we'll support them' in an official capacity removes any non-legal leverage over RB to not just 'peace out' of the whole thing and drop their own support to those modules the moment that statement is made. And I certainly wouldn't put it past Razbam to do exactly that at this point, if given that chance. @BIGNEWY @NineLine I know you have very often said 'we can't comment more until there's a resolution', but can you comment on, perhaps, a (non-exhaustive) list of outcomes for what you/ED would consider 'a resolution' to be? Two major ones that I can think of are: 1) Everything resolved to where Razbam goes back to work spring their modules, ED goes back to giving them full pay, and all is copacetic and happy and well and basically the terms of the original (or some new, mutually agreed) contract. 2) Presumably a legal conclusion is reached via court, both entities go their separate ways, and the state of these modules (either supported or not) remains a non-factor in whether or not the courts make their determination Are there ANY OTHER scenarios other than some settlement (1) or a legal conclusion in court (2) that you can think of, this moment, besides those two that fits your definition of 'resolution' to a level to where you can comment on anything going on here?
  20. The issue appears to be with the type of target. You have two scuds ready to fire with missiles up, and you're trying to track them. The cursor always seems to go to the centroid of the box, and since the missile is raised, the box is quite tall. Think of it as trying to balance a bagel on your finger: the only good spot is where there's a hole. So, for these types of targets, you'll need to do so manually. I'm able to maneuver the diamond around a target as I have my slew bound to two thumbstick axes. That said, it should still work for slewing through a target to one on the other side, so long as you don't let up on the button.
  21. Visually it doesn't seem to crumple/fall apart like others. For example you can come in tail first, bounce off of it, and it doesn't snap. That's the biggest (which is, admittedly, relatively small) thing for me on the damage model.
  22. It seems to be that happens after slaving in Pre-Point mode. I'm not sure if this is a bug or not, but this seems to cause the offset acquire and acquire on the move cursors to not move when attempting to slew. If you turn your MMS off and back on, it seems to clear whatever logic or variable is causing this behavior to be blocked. We'll see if this is fixed in the next patch, as I'm relatively certain it's a bug.
  23. I know I've had issue trying to get it to work, with cold-start aircraft, across a shared mission-editor setup AND manual set-up for presets, across UHF, VHF, and FM1/2 radios from no more than 30 feet away. Something's off, for sure.
  24. It can. I use the search bar and look for 'acknowledge'. Should have the 'ack' and 'recall' binds tied to it.
  25. This does appear to be the case, vis a vis prepoint. It seems though if you cycle the MMS off and back, the ACQ OM mode seems to work again. Though you're right, it seems the Point track/Offset Acquire and Acquire on the Move both break when you go to select prepoint.
×
×
  • Create New...