Jump to content

Luke Hume

SI Staff
  • Posts

    2,791
  • Joined

  • Last visited

Everything posted by Luke Hume

  1. Thanks for taking the time to raise this here. This is something which has already been flagged as a request within the community, so has already been documented and is part of our internal database of features for consideration. Like all features raised to us, it could end up rejected, or could after extensive design and development become a part of a future FM.
  2. Thanks for taking the time to raise this here. This is something which has already been flagged as a request within the community, so has already been documented and is part of our internal database of features for consideration. Like all features raised to us, it could end up rejected, or could after extensive design and development become a part of a future FM.
  3. Thanks for taking the time to raise this here. This is something which has already been flagged as a request within the community, so has already been documented and is part of our internal database of features for consideration. Like all features raised to us, it could end up rejected, or could after extensive design and development become a part of a future FM.
  4. Thanks for taking the time to raise this here. This has been documented and is part of our internal database of features for consideration. Like all features raised to us, it could end up rejected, or could after extensive design and development become a part of a future FM.
  5. Thanks for taking the time to raise this here. This is something which has already been flagged as a request within the community, so has already been documented and is part of our internal database of features for consideration. Like all features raised to us, it could end up rejected, or could after extensive design and development become a part of a future FM.
  6. Thanks for taking the time to raise this here. This is something which has already been flagged as a request within the community, so has already been documented and is part of our internal database of features for consideration. There are a number of licensing issues involved with this idea. Like all features raised to us, it could end up rejected, or could after extensive design and development become a part of a future FM.
  7. Thanks for taking the time to raise this here. This is something which has already been flagged as a request within the community, so has already been documented and is part of our internal database of features for consideration. Like all features raised to us, it could end up rejected, or could after extensive design and development become a part of a future FM.
  8. Thanks for taking the time to raise this here. Due to licensing restrictions, this is unlikely to be something we are able to explore.
  9. Thanks for taking the time to raise this here. This is something which has already been flagged as a request within the community, so has already been documented and is part of our internal database of features for consideration. Like all features raised to us, it could end up rejected, or could after extensive design and development become a part of a future FM.
  10. Thanks for taking the time to raise this here. This is something which has already been flagged as a request within the community, so has already been documented and is part of our internal database of features for consideration. Like all features raised to us, it could end up rejected, or could after extensive design and development become a part of a future FM.
  11. Hi there, we are always looking to improve the animation in our game. Due to some PC-specific specs, this isn't always possible, but we always strive to improve. Thanks for raising, anyway!
  12. Thanks for taking the time to raise this here. Due to the severe amount of memory that would be required, this is unlikely to be implemented. Thanks for taking the time to raise this here, but has been documented and is part of our internal database of features for consideration. Like all features raised to us, it could end up rejected, or could after extensive design and development become a part of a future FM.
  13. Thanks for taking the time to raise this here. This is something which has already been flagged as a request within the community, so has already been documented and is part of our internal database of features for consideration. Like all features raised to us, it could end up rejected, or could after extensive design and development become a part of a future FM.
  14. Thanks for taking the time to raise this here. This is something which has already been flagged as a request within the community, so has already been documented and is part of our internal database of features for consideration. Like all features raised to us, it could end up rejected, or could after extensive design and development become a part of a future FM.
  15. Thanks for taking the time to raise this here. This is something which has already been flagged as a request within the community, so has already been documented and is part of our internal database of features for consideration. Like all features raised to us, it could end up rejected, or could after extensive design and development become a part of a future FM.
  16. Thanks for taking the time to raise this here. This is something which has already been flagged as a request within the community, so has already been documented and is part of our internal database of features for consideration. Like all features raised to us, it could end up rejected, or could after extensive design and development become a part of a future FM.
  17. Thanks for taking the time to raise this here. This is something which has already been flagged as a request within the community, so has already been documented and is part of our internal database of features for consideration. Like all features raised to us, it could end up rejected, or could after extensive design and development become a part of a future FM.
  18. Thanks for taking the time to raise this here. This is something which has already been flagged as a request within the community, so has already been documented and is part of our internal database of features for consideration. Like all features raised to us, it could end up rejected, or could after extensive design and development become a part of a future FM.
  19. Thanks for taking the time to raise this here. This is something which has already been flagged as a request within the community, so has already been documented and is part of our internal database of features for consideration. Like all features raised to us, it could end up rejected, or could after extensive design and development become a part of a future FM.
  20. Thanks for taking the time to raise this here. This is something which has already been flagged as a request within the community, so has already been documented and is part of our internal database of features for consideration. Like all features raised to us, it could end up rejected, or could after extensive design and development become a part of a future FM.
  21. Thanks for taking the time to raise this here. This is not something we'd be likely to implement in the near future, but never say never!
  22. Thanks for taking the time to raise this here. This is something which has already been flagged as a request within the community, so has already been documented and is part of our internal database of features for consideration. Like all features raised to us, it could end up rejected, or could after extensive design and development become a part of a future FM.
×
×
  • Create New...