Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


jimj

Member
  • Content Count

    2
  • Donations

    $0.00 
  • Joined

  • Last visited

Community Reputation

0 Neutral

About jimj

Profile Information

  • OS
    Windows 10 x64
  • Country
  1. UCyborg: They shouldn't keep popping up if you don't close them. Duh? UCyborg: ...not spying on us. Paranoid are we? My inference was that a debug version was released to collect data on potential issues. If not, what's the point in releasing a debug version. I assume all the opoups are part of the debug nature of the release. There is one opoup that remains open continuously. The others stay closed when I close them. If the 'experimental' version of the dll isn't to collect data, I don't see the point of releasing a dysfunctional dll, which is what the debug feature does to an otherwise functional program. Until such time as the owner addresses the issue, if ever the issue is addressed, this is speculative.
  2. I downloaded and used the 'experimental' dll. Two things became obvious. 1. There would always be a CMD 'DOS box' window open, though minimized. 2. There would be occasional cmd "DOS box" popup windows that needed to be closed. I assume data was being collected and forwarded to the owner. I hope that helps. The frequent popup screens are the reason I reverted to the non-functional release. Other than that, I would have kept using the experimental dll.
×
×
  • Create New...